Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757166Ab2HGCGF (ORCPT ); Mon, 6 Aug 2012 22:06:05 -0400 Received: from db3ehsobe004.messaging.microsoft.com ([213.199.154.142]:51313 "EHLO db3outboundpool.messaging.microsoft.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753755Ab2HGCGC (ORCPT ); Mon, 6 Aug 2012 22:06:02 -0400 X-Forefront-Antispam-Report: CIP:157.56.234.117;KIP:(null);UIP:(null);IPV:NLI;H:SN2PRD0510HT003.namprd05.prod.outlook.com;RD:none;EFVD:NLI X-SpamScore: -3 X-BigFish: PS-3(z5109h5105hz98dI9371Ic89bh1432Izz1202hzz8275ch8275dhz2fh2a8h668h839h93fhd25hf0ah107ah) From: Dongjin Kim To: Olof Johansson CC: Thomas Abraham , Dongjin Kim , 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?7ZqM7IugOiDtmozsi6A6IFtQQVRDSF0gT0RST0lELVg6IGhrZGs0NDEyOiBB?= =?utf-8?Q?dd_new_hardware_based_on_Exynos4412?= Thread-Topic: =?utf-8?B?7ZqM7IugOiBbUEFUQ0hdIE9EUk9JRC1YOiBoa2RrNDQxMjogQWRkIG5ldyBo?= =?utf-8?Q?ardware_based_on_Exynos4412?= Thread-Index: AQHNc92ANlJ7ZpF870uQj1SyfcsbLJdNDJaAgAAH5miAAAeygIAAd4uI Date: Tue, 7 Aug 2012 02:05:56 +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: [210.113.108.23] 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 q7726BI8009295 Content-Length: 1939 Lines: 42 Hello, I am trying to understand what I have to do for device tree. In order to create dts file for ODROID-X hardware, it seems I may need dts file of EXYNOS4412 SoC. But maybe exynos4412.dtsi is not merged yet or not exist, like exynos4210.dtsi or exynos5250.dtsi. Obviously it seems not easy to create such a file without SoC datasheet, and I do not have it. So do I wait for the file to be merged by Samsung or better to create initial dts file cloned from exynos4210.dtsi and modify to have verified nodes with the source/header files? What's your suggestion? Regards, Dongjin. ________________________________________ 보낸 사람: Olof Johansson [olof@lixom.net] 보낸 날짜: 2012년 8월 7일 화요일 오전 3:33 받는 사람: Dongjin Kim 참조: Thomas Abraham; 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 Hi, On Mon, Aug 6, 2012 at 11:16 AM, Dongjin Kim wrote: > 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. Basic rule (that has some flexibility for legacy platforms) is that the net movement of board support should move from board files to device-tree based. Introduction of a brand new board like this is a prime example of something that should be using device tree from day 1. -Olof ????{.n?+???????+%?????ݶ??w??{.n?+????{??G?????{ay?ʇڙ?,j??f???h?????????z_??(?階?ݢj"???m??????G????????????&???~???iO???z??v?^?m???? ????????I?