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 11:33:57 +0200	[thread overview]
Message-ID: <4C875885.9020709@emk-elektronik.de> (raw)
In-Reply-To: <20100908090819.888211506AA@gemini.denx.de>

Wolfgang Denk schrieb:
> Dear Reinhard Meyer,
> 
> In message <4C874C02.9030801@emk-elektronik.de> you wrote:
>>> 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.
> 
> No. This will quicklly result in a maze of merge conflicts.

Not sure about that. I was thinking of a simple script that reads Linux'
mach-types.h (or arch/arm/tools/mach-types directly) and generates the
u-boot's mach-types.h file on the fly. That way only the #define lines could
be generated, producing a less than 100k files instead of > 1MB.

The same script would read the existing mach-types.h file, scanning for
something like

/* MANUAL ENTRIES START */
#define MACH_TYPE_XYZ 4711
#define MACH_TYPE_ABC 4712
/* MANUAL ENTRIES END */

and retain lines that are still above the official limit.
A commit should show only "+" for the new official definitions and a "-"
for all automagically removed manual definitions.

Otherwise:

It essentially means one can send patches for a new ARM based board
only if the MACH_TYPE has trickled through all the instances.

This is, somehow, unpleasing:). We should not "punish" ourselves in u-boot
just because someone has invented a method to prolong time-to-market ;)

Reinhard

  reply	other threads:[~2010-09-08  9:33 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
2010-09-08  9:08     ` Wolfgang Denk
2010-09-08  9:33       ` Reinhard Meyer [this message]
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=4C875885.9020709@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