Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932368Ab2HFSQ0 (ORCPT ); Mon, 6 Aug 2012 14:16:26 -0400 Received: from co1ehsobe004.messaging.microsoft.com ([216.32.180.187]:48383 "EHLO co1outboundpool.messaging.microsoft.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932114Ab2HFSQY (ORCPT ); Mon, 6 Aug 2012 14:16:24 -0400 X-Forefront-Antispam-Report: CIP:157.56.234.117;KIP:(null);UIP:(null);IPV:NLI;H:SN2PRD0510HT001.namprd05.prod.outlook.com;RD:none;EFVD:NLI X-SpamScore: 3 X-BigFish: PS3(z5109h5105h32acnz98dIc89bh1432I4015Izz1202hzz8275ch8275bh8275dhz2fh2a8h668h839h93fhd25hf0ah107ah) From: Dongjin Kim To: Thomas Abraham , Dongjin Kim CC: Kukjin Kim , Russell King , Tony Lindgren , Jon Medhurst , Shawn Guo , =?utf-8?B?VXdlIEtsZWluZS1Lw7ZuaWc=?= , "linux-arm-kernel@lists.infradead.org" , "linux-samsung-soc@vger.kernel.org" , "linux-kernel@vger.kernel.org" Subject: =?utf-8?B?7ZqM7IugOiBbUEFUQ0hdIE9EUk9JRC1YOiBoa2RrNDQxMjogQWRkIG5ldyBo?= =?utf-8?Q?ardware_based_on_Exynos4412?= Thread-Topic: [PATCH] ODROID-X: hkdk4412: Add new hardware based on Exynos4412 Thread-Index: AQHNc92ANlJ7ZpF870uQj1SyfcsbLJdNDJaAgAAH5mg= Date: Mon, 6 Aug 2012 18:16:18 +0000 Message-ID: References: <1344262254-14648-1-git-send-email-dongjin.kim@agreeyamobility.net>, In-Reply-To: Accept-Language: ko-KR, en-US Content-Language: ko-KR X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [125.177.223.167] Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 X-OriginatorOrg: agreeyamobility.net Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by mail.home.local id q76IGWYu007079 Content-Length: 1821 Lines: 39 Hello Tomas, I am agree with you to look at using device tree and I have some plan for it. But as of now I am focusing to bring up the hardware itself with mainline kernel and merge into it. I also need some time to look at the requirement of device tree, because I am not familiar with it yet. Any advice will be welcomed. Thanks, Dongjin. ________________________________________ 보낸 사람: Thomas Abraham [thomas.abraham@linaro.org] 보낸 날짜: 2012년 8월 7일 화요일 오전 2:37 받는 사람: Dongjin Kim 참조: Dongjin Kim; Kukjin Kim; Russell King; Tony Lindgren; Jon Medhurst; Shawn Guo; Uwe Kleine-König; linux-arm-kernel@lists.infradead.org; linux-samsung-soc@vger.kernel.org; linux-kernel@vger.kernel.org 제목: Re: [PATCH] ODROID-X: hkdk4412: Add new hardware based on Exynos4412 On 6 August 2012 19:40, Dongjin Kim wrote: > The HKDK4412 is the CPU module developed by Hardkernel which is based on > Exynos 4412. mach_hkdk4412.c is to run on ODROID-X hardware and Machine ID > (4289) is registered. > > Change-Id: I3af02808c03b9acea916c310390a4904ad92d761 > Signed-off-by: Dongjin Kim > --- > arch/arm/mach-exynos/Kconfig | 23 + > arch/arm/mach-exynos/Makefile | 1 + > arch/arm/mach-exynos/mach-hkdk4412.c | 979 ++++++++++++++++++++++++++++++++++ > arch/arm/tools/mach-types | 1 + > 4 files changed, 1004 insertions(+) > create mode 100644 arch/arm/mach-exynos/mach-hkdk4412.c How about looking at using device tree option for this board. That might require additional effort but would be helpful in the long run. Thanks, Thomas. ????{.n?+???????+%?????ݶ??w??{.n?+????{??G?????{ay?ʇڙ?,j??f???h?????????z_??(?階?ݢj"???m??????G????????????&???~???iO???z??v?^?m???? ????????I?