public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Alessandro Rubini <rubini-list@gnudd.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [STATUS] Heads-up: Reorganize directory structure
Date: Thu, 15 Apr 2010 19:58:45 +0200	[thread overview]
Message-ID: <20100415175845.GA2680@morgana.gnudd.com> (raw)
In-Reply-To: <1271347099.6519.18.camel@localhost.localdomain>

>> Most boards are very similar to the original evaluation kit.  For
>> example, [...]

>> Similarly, I'm working on a dave-tech.eu board series based on
>> ep9302-ep9315.  [...]

> I don't follow either argument, or the name-switching argument...

Well, the name-switching is half a joke (but the philips 21xx is now nxp,
motorola went freescale and so on).

> How does putting boards in their appropriate CPU directory make
> your coding any easier?

Because if all boars with the same SoC are in the same directory they
can share source files. In my example, st/nhk8815 and calao/usb-s8815
had several files replicated -- so Wolfgang rejected the patch.  But
in a vendor-based structure I won't merge in a single board dir boards
from two different vendors. Same will happen for dave/zefeer where a
lot is in commong with edb93xx.

That's what the kernel is doing, actually. In arch-pxa, arch-at91 and
other directories at the same level I have board file and some files
that are used by several boards.  Some are SoC wide, so would fit in
cpu/ within u-boot, but some not (although, my fault, I'm not digging
for filenames to show).  I think there already is some replication in
u-boot currently, but I haven't stats right now.

On the other hand, having boards as subdirs of the same parent doesn't
automatically make replication go away, but at least may avoid new
replication in future boards

thanks for your patience
/alessandro

  reply	other threads:[~2010-04-15 17:58 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-13  9:23 [U-Boot] [STATUS] Heads-up: Reorganize directory structure Wolfgang Denk
2010-04-13 16:49 ` Ben Warren
2010-04-13 17:28   ` Stefano Babic
2010-04-13 17:29     ` Ben Warren
2010-04-13 19:24       ` Wolfgang Denk
2010-04-13 20:32         ` Remy Bohmer
2010-04-13 21:01           ` Wolfgang Denk
2010-04-13 19:22   ` Wolfgang Denk
2010-04-13 18:55 ` Remy Bohmer
2010-04-13 19:47 ` Jerry Van baren
2010-04-15  7:05 ` Michal Simek
2010-04-15  7:52   ` Wolfgang Denk
2010-04-15 15:04     ` Peter Tyser
2010-04-15 15:22       ` Wolfgang Denk
2010-04-15 15:31         ` Alessandro Rubini
2010-04-15 15:58           ` Peter Tyser
2010-04-15 17:58             ` Alessandro Rubini [this message]
2010-04-15 22:44               ` Peter Tyser
2010-04-16  2:42             ` Graeme Russ
2010-04-16  6:58               ` Alessandro Rubini
2010-04-16  7:50                 ` Wolfgang Denk
2010-04-16  7:41               ` Wolfgang Denk
2010-04-16 11:45                 ` Graeme Russ
2010-04-16 13:23                   ` Wolfgang Denk
2010-04-15 23:14           ` Wolfgang Denk
2010-04-17  8:25 ` Graeme Russ

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=20100415175845.GA2680@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