public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Reinhard Meyer <u-boot@emk-elektronik.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] ARM mach-types.h (was: Re: [PATCH 1/5] add DOCKSTAR machine type)
Date: Wed, 08 Sep 2010 10:40:34 +0200	[thread overview]
Message-ID: <4C874C02.9030801@emk-elektronik.de> (raw)
In-Reply-To: <20100908081358.2FA96153798@gemini.denx.de>

Dear Wolfgang Denk,
> Dear Reinhard Meyer,
>
> In message<4C873717.6000403@emk-elektronik.de>  you wrote:
>>
>> Since it apparently takes roughly two months for additions to the database
>> at http://www.arm.linux.org.uk/developer/machines/ (last entry: 3061 right now)
>> to trickle to the u-boot file, there seems to be a need for an interim solution.
>
> In theory it would be possible to sync against www.arm.linux.org.uk
> directly, but people with better ARM knowledge than me recommended not
> to do that, but refer to a more stable reference like the mainline
> Linux kernel instead.
>
> I'm open to suggestions.

I'd allow manual adding of a #define MACH_TYPE_xxxx at the end of the list
provided its value is higher than the last "official" entry. Once the official
list reaches or goes beyond that value the manual line(s) would be removed.
Not being a shell script guru, I think that could be easily done.

Another option would be to derive the file directly from above website.

One catch remains, of course: I someone changed their entry at the database,
compilation of u-boot for that board could break. I think that entries that
have propagated to the mainline Linux kernel cannot be changed anymore.

I'd also think the u-boot mach-type.h could do well without all the function
definitions. I have not grepped, however, if someone in u-boot uses them.

Reinhard

  reply	other threads:[~2010-09-08  8:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-08  7:11 [U-Boot] ARM mach-types.h (was: Re: [PATCH 1/5] add DOCKSTAR machine type) Reinhard Meyer
2010-09-08  8:13 ` Wolfgang Denk
2010-09-08  8:40   ` Reinhard Meyer [this message]
2010-09-08  9:08     ` Wolfgang Denk
2010-09-08  9:33       ` Reinhard Meyer
2010-09-08 12:55         ` Wolfgang Denk
2010-09-08 18:58       ` Paulraj, Sandeep
2010-09-08 19:22         ` Reinhard Meyer
2010-09-08 19:53         ` Wolfgang Denk
2010-09-08 20:05           ` Paulraj, Sandeep
2010-09-13 13:49             ` Thomas Weber

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=4C874C02.9030801@emk-elektronik.de \
    --to=u-boot@emk-elektronik.de \
    --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