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 09:11:19 +0200	[thread overview]
Message-ID: <4C873717.6000403@emk-elektronik.de> (raw)

Dear all,
 >>   #define MACH_TYPE_WLAN_COMPUTER        2966
 >> +#define MACH_TYPE_DOCKSTAR             2998
 >>
 >
 > NAK.  We don't edit mach-types.h manually.
 >
 > If you need it updated, please send a request to do so to the acting
 > ARM custodian (ahem).
 >
 > But also note that we always sync against the current mainline Linux
 > kernel, and this does not have an entry for DOCKSTAR yet (it ends at
 > WLAN_COMPUTER), so a new sync would not change the file yet.

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.

Currently I conditionally add the MACH_TYPE_xxx locally to the <board>.h
file, but I am quite sure a patch with that would be rejected...

Of course best would be to get rid of mach-types.h completely. It does not
really seem suited to differentiate between board variants...

Reinhard

             reply	other threads:[~2010-09-08  7:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-08  7:11 Reinhard Meyer [this message]
2010-09-08  8:13 ` [U-Boot] ARM mach-types.h (was: Re: [PATCH 1/5] add DOCKSTAR machine type) Wolfgang Denk
2010-09-08  8:40   ` Reinhard Meyer
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=4C873717.6000403@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