All of lore.kernel.org
 help / color / mirror / Atom feed
From: Troy Kisky <troy.kisky@boundarydevices.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] ARM: Update mach-types
Date: Wed, 29 Feb 2012 13:33:24 -0700	[thread overview]
Message-ID: <4F4E8B94.4030405@boundarydevices.com> (raw)
In-Reply-To: <4F4D6AED.1050006@denx.de>

On 2/28/2012 5:01 PM, stefano babic wrote:
> Am 28/02/2012 04:51, schrieb Marek Vasut:
>>> On 2/27/2012 3:56 PM, Marek Vasut wrote:
>>>>> |ARM: Update mach-types
>>>>> |
>>>>> |This commit updates the mach-types based on the latest in Linus's
>>>>> head |
>>>>> |Signed-off-by: Marek Vasut<marek.vasut@gmail.com>
>>>>>
>>>>> Hi Marek,
>>>>>
>>>>>
>>>>> Can I get you to do this again? I'd the symbol for
>>>>> MACH_MX6Q_SABRELITE.
>>>> No, can you please submit the mach-types update yourself? Thank you!
>>>>
>>> I don't think I'm trusted to do that. I think that some machines may
>>> have been removed
>>> from Linux that u-boot may want to keep.
>> So these machines have to define their mach id in their config (and you need to fix them after replacing mach-types).
>>
>> Since I only want to use the
>>> value in 1 place,
>>> is it acceptable to just use the hex value instead?
>> No, either update the mach types (preffered) or ... Update the mach types ;)
> It was discussed and accepted that the boards can set CONFIG_MACH_TYPE
> directly into the configuration file. In this way, we continue to
> support in U-Boot boards independently if they are pushed to Linux
> mainline or not.
>
> On the other side, everybody can send the current mach-types from the
> Linux kernel to Albert (ARM Maintainer) - if a board is already in
> kernel mainline is the preferred way.
>
> Best regards,
> Stefano Babic
>
Thanks for the information. I'll send to Albert soon.

Troy

  reply	other threads:[~2012-02-29 20:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-27 21:56 [U-Boot] ARM: Update mach-types Troy Kisky
2012-02-27 22:56 ` Marek Vasut
2012-02-28  1:14   ` Troy Kisky
2012-02-28  3:51     ` Marek Vasut
2012-02-29  0:01       ` stefano babic
2012-02-29 20:33         ` Troy Kisky [this message]
2012-02-28  6:50 ` Dirk Behme
2012-02-28  9:28   ` Fabio Estevam
2012-02-28 13:36     ` Eric Nelson
  -- strict thread matches above, loose matches on Subject: below --
2010-02-27 23:35 [U-Boot] ARM " Tom
2009-11-15 17:55 [U-Boot] ARM update mach-types Tom

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=4F4E8B94.4030405@boundarydevices.com \
    --to=troy.kisky@boundarydevices.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.