From: Alessandro Rubini <rubini-list@gnudd.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] Add Nomadik board "usb-s8815" by Calao vendor
Date: Fri, 22 Jan 2010 19:36:00 +0100 [thread overview]
Message-ID: <20100122183559.GA15378@morgana.gnudd.com> (raw)
In-Reply-To: <20100118233218.94F213F6C0@gemini.denx.de>
Wolfgang Denk:
> I don't like to see such heavy copying of code. This is a clear
> indication that we should factor out the common parts
While I disagree (as explained), I'm trying hard to do
it. Unfortunately what is currently a Makefile decision (COBJS-y and
such) will sometimes become ifdef in the code.
However, i've moved platform.S and lcd.c to the cpu directory, so they
can be shared (the assembly really ought to be personalized for each
board, as some cruft is still there from past history, and the lcd.c
is really two small data structures, but let's ignore this by now).
Now, reading better your message I see this that I don't understand.
> Actually differences are so small that common code can be used
> completely, and no separate board directories are needed.
On one side we are asked to use the vendor directories, and now I
should merge vendor/st/nhk8815 and vendor/calao/usb-8815. Now,
I wonder where am I expected to place che board files. In
cpu/arm926ejs/nomadik ? And using #ifdef in a single file to sort out
differences?
I got the idea a board should be a separate object (directory), which
bases on the available infrastructure to pick up pieces and define own
parameters. Adding a board should be as easy as adding a directory.
Such parameters sometimes happen to match other parameters, but
coalescing two boards just to save a few lines is not an advantage, in
my opinion.
Could you please explain how to proceed to have both boards upstream in
the best possible way? I currently don't understand the policy.
Please forgive me if the message looks aggressive. It's not meant to
be, but ascii doesn't proprely convey tone.
/alessandro
prev parent reply other threads:[~2010-01-22 18:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-18 22:13 [U-Boot] [PATCH 0/2] Add a new Nomadik board Alessandro Rubini
2010-01-18 22:13 ` [U-Boot] [PATCH 1/2] NAND Nomadik: add CONFIG_NAND_NOMADIK_16BIT option Alessandro Rubini
2010-01-18 23:26 ` Wolfgang Denk
2010-01-18 23:31 ` Scott Wood
2010-01-19 0:02 ` Alessandro Rubini
2010-01-18 22:13 ` [U-Boot] [PATCH 2/2] Add Nomadik board "usb-s8815" by Calao vendor Alessandro Rubini
2010-01-18 23:32 ` Wolfgang Denk
2010-01-18 23:54 ` Alessandro Rubini
2010-01-22 18:36 ` Alessandro Rubini [this message]
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=20100122183559.GA15378@morgana.gnudd.com \
--to=rubini-list@gnudd.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox