From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v7] dreamplug: initial board support.
Date: Sun, 18 Sep 2011 19:58:14 +0200 [thread overview]
Message-ID: <4E763136.4010709@aribaud.net> (raw)
In-Reply-To: <F766E4F80769BD478052FB6533FA745D1A11467302@SC-VEXCH4.marvell.com>
(Please do not use my @free.fr address to copy me on U-boot matters...)
Le 14/09/2011 08:39, Prafulla Wadaskar a ?crit :
>
>
>> -----Original Message-----
>> From: Jason [mailto:u-boot at lakedaemon.net]
>> Sent: Tuesday, September 13, 2011 7:47 PM
>> To: Wolfgang Denk
>> Cc: Prafulla Wadaskar; Albert Aribaud; u-boot at lists.denx.de
>> Subject: Re: [U-Boot] [PATCH v7] dreamplug: initial board support.
>>
>> Albert,
>>
>> On Tue, Sep 13, 2011 at 03:00:59PM +0200, Wolfgang Denk wrote:
>>> Dear Prafulla,
>>>
>>> In message<F766E4F80769BD478052FB6533FA745D1A114670B3@SC-
>> VEXCH4.marvell.com> you wrote:
>>>>
>>>> Let's have Wolfgang's opinion on this, since this not aligned with
>> current
>>>> u-boot development strategy.
>>>>
>>>> May be we can create a separate header file for tracking
>> (unsupported/tobe
>>>> supported) arm machine-types.
>>>
>>> Actually this is for Albert to comment. He is the ARM custodian and
>>> has to live with the results.
>>
>> Wolfgang, Marek Vasut, and I discussed this here [1]. To summarize, by
>> declaring non-mainlined mach_types in the respective board config, an
>> error will be thrown at compile time after mach-types.h is updated to
>> include the mach_type.
>>
>> The other idea is to have a separate file, say mach-types-local.h where
>> all non-mainlined mach-types would be defined.
>
> I will vote for this second approach so that it becomes independent change and anyone can update it in future.
>
> Let's get Albert's opinion on this.
My opinion on the whole mach-type question is "if a board needs a
mach-type it's because it will run Linux, so its mach-type should
eventually be in the Linux mach-type list". As I understand it, the only
case when is not there is because U-Boot support is submitted before
Linux mainline support. Thus I second the idea of defining it in the
board config header file, possibly even testing for it first and if it
already exists, throwing a #error to remind the board maintainer to
remove the now useless define from the config file.
> Regards..
> Prafulla . .
Amicalement,
--
Albert.
next prev parent reply other threads:[~2011-09-18 17:58 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-13 15:54 [U-Boot] [PATCH 0/1 v4] RFC: Dreamplug support u-boot at lakedaemon.net
2011-06-13 15:54 ` [U-Boot] [PATCH 1/1 v4] RFC: dreamplug: Initial support u-boot at lakedaemon.net
2011-06-13 15:59 ` Prafulla Wadaskar
2011-06-13 16:07 ` Jason
2011-06-13 16:46 ` Wolfgang Denk
2011-06-13 16:51 ` Jason
2011-07-21 19:36 ` Clint Adams
2011-07-21 20:26 ` Jason
2011-07-21 20:56 ` Clint Adams
2011-07-21 21:17 ` Jason
2011-07-26 21:19 ` [U-Boot] RFC [PATCH 0/5 v5] add dreamplug support Jason Cooper
2011-09-11 22:10 ` [U-Boot] [PATCH v6] dreamplug: initial board support u-boot at lakedaemon.net
2011-09-12 7:37 ` Igor Grinberg
2011-09-12 11:36 ` Jason
2011-09-12 11:45 ` [U-Boot] [PATCH v7] " Jason Cooper
2011-09-13 7:32 ` Igor Grinberg
2011-09-13 13:53 ` Jason
2011-09-13 11:56 ` Prafulla Wadaskar
2011-09-13 13:00 ` Wolfgang Denk
2011-09-13 14:17 ` Jason
2011-09-14 6:39 ` Prafulla Wadaskar
2011-09-18 17:58 ` Albert ARIBAUD [this message]
2011-09-18 18:27 ` Albert ARIBAUD
2011-09-18 18:39 ` Jason
2011-09-18 20:28 ` Wolfgang Denk
2011-09-18 20:58 ` Jason
2011-09-18 19:06 ` [U-Boot] [PATCH v8] " Jason Cooper
2011-10-03 4:37 ` Prafulla Wadaskar
2011-07-26 21:19 ` [U-Boot] RFC [PATCH 1/5] drivers/rtc: add Marvell Integrated RTC Jason Cooper
2011-07-27 18:12 ` Prafulla Wadaskar
2011-07-28 1:22 ` Jason
2011-07-28 19:09 ` Prafulla Wadaskar
2011-07-26 21:19 ` [U-Boot] RFC [PATCH 2/5] arm/kirkwood: print speeds with cpu info Jason Cooper
2011-07-27 18:21 ` Prafulla Wadaskar
2011-07-28 1:31 ` Jason
2011-07-28 19:14 ` Prafulla Wadaskar
2011-10-06 18:13 ` Wolfgang Denk
2011-10-07 12:37 ` Jason
2011-07-26 21:19 ` [U-Boot] RFC [PATCH 3/5] usb: Some EHCI chipsets are slow to respond Jason Cooper
2011-07-27 18:23 ` Prafulla Wadaskar
2011-07-28 1:37 ` Jason
2011-07-28 19:16 ` Prafulla Wadaskar
2011-07-29 14:31 ` Jason
2011-07-26 21:19 ` [U-Boot] RFC [PATCH 4/5 v5] dreamplug: initial board support Jason Cooper
2011-07-27 18:38 ` Prafulla Wadaskar
2011-07-28 2:02 ` Jason
2011-07-28 19:37 ` Prafulla Wadaskar
2011-07-29 15:18 ` Jason
2011-07-29 18:57 ` Prafulla Wadaskar
2011-07-29 19:43 ` Jason
2011-10-06 18:15 ` Wolfgang Denk
2011-10-07 12:40 ` Jason
2011-07-26 21:19 ` [U-Boot] RFC [PATCH 5/5 v5] dreamplug: use MACH_TYPE_DREAMPLUG Jason Cooper
2011-07-27 18:40 ` Prafulla Wadaskar
2011-07-28 2:08 ` Jason
2011-07-28 7:25 ` Bdale Garbee
2011-07-28 12:43 ` Jason
2011-07-28 13:44 ` Bdale Garbee
2011-07-28 19:39 ` Prafulla Wadaskar
2011-07-29 15:25 ` Jason
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E763136.4010709@aribaud.net \
--to=albert.u.boot@aribaud.net \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox