From: Holger Brunck <holger.brunck@keymile.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2] ARM: Update mach-types
Date: Mon, 12 Sep 2011 16:20:20 +0200 [thread overview]
Message-ID: <4E6E1524.2050904@keymile.com> (raw)
In-Reply-To: <4E6E13BC.7080802@denx.de>
On 09/12/2011 04:14 PM, Stefano Babic wrote:
>>>>
>>>> No, but then the respective maintainers will get a warning and will be forced to
>>>> fix their boards in both linux and uboot.
>>>
>>> Maybe the simplest way to catch these boards (if any) is to run MAKEALL
>>> on arm targets with your mach-types file. If no board is broken, we have
>>> not to worry about.
>>>
>>
>> sorry, I didn't follow the whole discussion, but this patch will remove the
>> mach type for our km_kirkwood board.
>>
>> -#define MACH_TYPE_KM_KIRKWOOD 2255
>>
>> This board is supported in u-boot but not mainlined in linux. So how should we
>> handle this?
>
> Well, I think we cannot check for each update of this file which board
> are dropped - this requires too much effort. The way we currently use
> (Linux is the master of this file, and we update it directly from the
> kernel) is IMHO the right way to get it in sync.
>
Yes I agree. And I think our KM_KIRKWOOD may be a special case, because in the
past we were present in mainline mach-types, but during a cleanup we were
dropped, because we missed to get the associated board mainlined.
> Maybe the best way, if you want to have your board maintained in u-boot
> but not in kernel (however, why ?) is to define your MACH in the board
> configuration file.
>
ok I will do this. When is this patch supposed to go in?
regards
Holger
next prev parent reply other threads:[~2011-09-12 14:20 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-12 3:54 [U-Boot] [PATCH V2] ARM: Update mach-types Marek Vasut
2011-09-12 9:53 ` Igor Grinberg
2011-09-12 13:36 ` Marek Vasut
2011-09-12 13:54 ` Stefano Babic
2011-09-12 14:04 ` Holger Brunck
2011-09-12 14:10 ` Marek Vasut
2011-09-13 7:46 ` Igor Grinberg
2011-09-12 14:11 ` Jason
2011-09-12 14:14 ` Stefano Babic
2011-09-12 14:20 ` Holger Brunck [this message]
2011-09-12 14:37 ` Stefano Babic
2011-09-12 15:01 ` Marek Vasut
2011-09-12 18:27 ` Wolfgang Denk
2011-09-12 14:51 ` Valentin Longchamp
2011-09-12 15:42 ` Marek Vasut
2011-09-13 11:49 ` Prafulla Wadaskar
2011-09-12 14:48 ` Nick Thompson
2011-09-12 14:53 ` Stefano Babic
2011-09-12 14:57 ` Nick Thompson
2011-10-19 6:31 ` Albert ARIBAUD
2011-10-28 9:03 ` Mike Frysinger
2011-10-28 9:22 ` Marek Vasut
2011-10-28 9:57 ` Stefano Babic
2011-10-28 15:22 ` Albert ARIBAUD
2011-10-28 16:32 ` Tom Rini
2011-10-28 17:24 ` Albert ARIBAUD
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=4E6E1524.2050904@keymile.com \
--to=holger.brunck@keymile.com \
--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