[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <A6A3B7488C419F488E5B13FFD03C08AD2F43688D@SN2PRD0510MB370.namprd05.prod.outlook.com>
Date: Tue, 7 Aug 2012 02:05:56 +0000
From: Dongjin Kim <Dongjin.Kim@...eeyamobility.net>
To: Olof Johansson <olof@...om.net>
CC: Thomas Abraham <thomas.abraham@...aro.org>,
Dongjin Kim <tobetter@...il.com>,
Kukjin Kim <kgene.kim@...sung.com>,
Russell King <linux@....linux.org.uk>,
Tony Lindgren <tony@...mide.com>,
Jon Medhurst <tixy@...t.co.uk>,
Shawn Guo <shawn.guo@...aro.org>,
Uwe Kleine-König
<u.kleine-koenig@...gutronix.de>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-samsung-soc@...r.kernel.org"
<linux-samsung-soc@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: 회신: 회신: [PATCH] ODROID-X: hkdk4412: Add new hardware based on Exynos4412
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@...om.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@...ts.infradead.org; linux-samsung-soc@...r.kernel.org; linux-kernel@...r.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
<Dongjin.Kim@...eeyamobility.net> 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
Powered by blists - more mailing lists