public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Michael Schwingen <rincewind@discworld.dascon.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Update and Cut down mach types
Date: Wed, 20 Apr 2011 21:26:57 +0200	[thread overview]
Message-ID: <4DAF3381.7000804@discworld.dascon.de> (raw)
In-Reply-To: <4DAF1CBA.9020902@aribaud.net>

On 04/20/2011 07:49 PM, Albert ARIBAUD wrote:
> Le 20/04/2011 19:15, Michael Schwingen a ?crit :
>
>> Why don't we pull the original master mach-types file, and generate the
>> required .h file(s) during make using the same (or a similar) script
>> Linux uses?
> Hmm, because it would mean maintaining the same script as Linux uses.
> With the current solution, there's work to be done on mach-types only
> when someone needs new machine IDs.
I don't see how much maintaining the script would need - if the input 
format does not change, the script does not need changes, and if changes 
are needed, the can be copied 1:1 from the Linux version.

On the plus side: the mach-types file is much more terse than the 
generated headers, so updates that pull in new machines would generate 
diffs that are a lot smaller than they are now.


>>> Have you checked that none of the removed boards are in U-Boot tree?
>>> Because if there are some, then their build will be broken...
>> It will break ACTUX1-ACTUX4 (which are in-tree, and work fine as soon as
>> the relocation-breakage-patch is accepted), plus  DVLHOST, for which I
>> have patches submitted to add support.
>>
>> For my own boards, I can go to the ARM machine database, touch the
>> entry, and wait until the define re-emerges in Linux, and await until
>> that is marged back to u-boot, but this is plain silly. However, for
>> DVLHOST, I am not the registered maintainer in the machine database, so
>> I would have to create a duplicate entry for this to work.
> IIUC the machines that would disappear are those for which the is no
> actual mainline Linux support and which have not been touched in over a
> year, right? Do ACTUX* and DVLHOST boards fit in this description?
Yes. The ACTUX board ports are by me, while the DVLHOST machine type 
seems to be allocated by the manufacturer, Devolo, who never mainlined 
their Linux adaptions, so my goal is to get an independent port up. 
However, that means I can't update the machine type to get it back in 
mainline Linux by the 12-month-rule.

cu
Michael

  reply	other threads:[~2011-04-20 19:26 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-19 12:42 [U-Boot] Update and Cut down mach types Paulraj, Sandeep
2011-04-19 13:39 ` Matthias Weißer
2011-04-19 13:45   ` Paulraj, Sandeep
2011-04-20  8:44     ` Albert ARIBAUD
2011-04-19 14:21   ` Wolfgang Denk
2011-04-19 18:42     ` Matthias Weisser
2011-04-19 18:44     ` Michael Schwingen
2011-04-20  8:15       ` Detlev Zundel
2011-04-20  8:58 ` Igor Grinberg
2011-04-20 17:15   ` Michael Schwingen
2011-04-20 17:49     ` Albert ARIBAUD
2011-04-20 19:26       ` Michael Schwingen [this message]
2011-04-21 11:39         ` Albert ARIBAUD
2011-04-26 18:14           ` Michael Schwingen
2011-04-26 19:40             ` Wolfgang Denk
2011-04-26 20:38               ` Albert ARIBAUD
2011-04-26 21:32                 ` Wolfgang Denk
2011-04-26 21:38                   ` Reinhard Meyer
2011-04-27 10:19                     ` Michael Schwingen
2011-04-28  6:20                       ` Igor Grinberg
2011-04-29  8:58                         ` Detlev Zundel
2011-05-01 10:10                           ` [U-Boot] [PATCH 1/3] arm: omap: innovator: fix compilation error Igor Grinberg
2011-05-17 12:40                             ` Igor Grinberg
2011-05-21 21:40                               ` Paulraj, Sandeep
2011-05-01 10:10                           ` [U-Boot] [PATCH 2/3] arm: omap: innovator: Prepare for mach-types.h changes Igor Grinberg
2011-05-01 20:28                             ` Alessandro Rubini
2011-05-02  7:18                               ` Igor Grinberg
2011-05-03 10:08                                 ` [U-Boot] [PATCH v2 " Igor Grinberg
2011-05-03 12:29                                   ` Wolfgang Denk
2011-05-03 13:00                                     ` Igor Grinberg
2011-05-04  7:13                                       ` [U-Boot] [PATCH v3 " Igor Grinberg
2011-05-01 10:10                           ` [U-Boot] [PATCH 3/3] arm: at91: ether: " Igor Grinberg
2011-05-01 19:38                             ` Reinhard Meyer
2011-05-02  7:29                               ` Igor Grinberg
2011-05-02 10:09                                 ` Detlev Zundel
2011-05-02 12:49                                   ` [U-Boot] [PATCH v2 " Igor Grinberg
2011-05-16 13:31                                     ` Igor Grinberg
2011-04-27 11:44                     ` [U-Boot] Update and Cut down mach types Detlev Zundel

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=4DAF3381.7000804@discworld.dascon.de \
    --to=rincewind@discworld.dascon.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