public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Peter Tyser <ptyser@xes-inc.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 0/6] Clean up top-level directory structure
Date: Tue, 14 Jul 2009 10:20:43 -0500	[thread overview]
Message-ID: <1247584843.30723.18.camel@localhost.localdomain> (raw)
In-Reply-To: <20090712125427.GD21713@game.jcrosoft.org>

On Sun, 2009-07-12 at 14:54 +0200, Jean-Christophe PLAGNIOL-VILLARD
wrote:
> On 22:42 Fri 10 Jul     , Mike Frysinger wrote:
> > On Friday 10 July 2009 21:20:45 Shinya Kuribayashi wrote:
> > > Peter Tyser wrote:
> > > >> Before verifying MIPS builds, I'd like to make sure that why you take
> > > >> lib/$(ARCH)/ alternative, not $(ARCH)/lib/.  If there were any
> > > >> discussion on #IRC, is there any chance we could share the summary or
> > > >> decision to follow?
> > > >
> > > > There was no discussion, /lib/$(ARCH) just made more sense to me and it
> > > > was functionally a direct translation from lib_$(ARCH) to lib/$(ARCH).
> > > >
> > > > Using $(ARCH)/lib wouldn't clean up the top-level directory structure
> > > > much and would open a can of worms that I'm not prepared to deal with at
> > > > this time.  For example, if there was an architecture specific
> > >
> > > Oops, I wanted to say "arch/$(ARCH)/lib/", not $(ARCH)/lib/, sorry.
> > 
> > i thought that originally, but i dont care much either way.  having 
> > arch/$(ARCH)/ would line up with u-boot-v2 and the linux kernel though.
> > 
> > i dont understand needing a lib/ subdir under arch/$(ARCH)/ though.
> > 
> > > > While we're talking about it, I'd always thought it would be nice to
> > > > split out all the cmd_* files from common/ into their own command/
> > > > directory similar to u-boot-v2.
> > >
> > > Ack.  The directory structure in u-boot-v2 looks nice, at least, to me,
> > > anyway.
> I prefer the
> arch/$(ARCH)/lib
> so will could also move the cpu stuff there too

I like the Linux and u-boot-v2 directory layout too the more I think
about it too.  How about if I resend this series but with the final
directory structure looking like:

/arch/$(ARCH)/lib/<source files currently in lib_$(ARCH)

/lib/
	/<source files currently in lib_generic>
	/libfdt/
	/lzma/
	/lzo/

/examples/
	/api/
	/standalone/


That will lay the groundwork for moving additional files
into /arch/$(ARCH)/ down the road.  eg I think it would be nice to move
the directories in /cpu/* into their respective /arch/$(ARCH)/
directory, and possibly the /include/asm-$(ARCH) directories in the long
run.

What do others think of this?

Best,
Peter

  reply	other threads:[~2009-07-14 15:20 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-10 16:03 [U-Boot] [PATCH v2 0/6] Clean up top-level directory structure Peter Tyser
2009-07-10 16:03 ` [U-Boot] [PATCH v2 1/6] Move architecture specific config.mk files into subdirs Peter Tyser
2009-07-20 22:12   ` Wolfgang Denk
2009-07-10 16:03 ` [U-Boot] [PATCH v2 2/6] Move lib_<ARCH> directories to lib/<ARCH> Peter Tyser
2009-11-22 20:54   ` Wolfgang Denk
2009-11-23  2:39     ` Peter Tyser
2009-12-07 21:32       ` Wolfgang Denk
2009-12-07 21:42         ` Scott Wood
2009-12-08  5:39           ` Peter Tyser
2009-07-10 16:03 ` [U-Boot] [PATCH v2 3/6] Move lib_generic to lib/generic Peter Tyser
2009-07-10 16:03 ` [U-Boot] [PATCH v2 4/6] Move libfdt to lib/libfdt Peter Tyser
2009-07-10 16:03 ` [U-Boot] [PATCH v2 5/6] Move examples/ to examples/standalone Peter Tyser
2009-07-10 17:07   ` Mike Frysinger
2009-07-20 22:13   ` Wolfgang Denk
2009-07-22 21:56   ` [U-Boot] [PATCH] Fix "ld: cannot find -lstubs" build error Wolfgang Denk
2009-07-10 16:03 ` [U-Boot] [PATCH v2 6/6] Move api_examples to examples/api Peter Tyser
2009-07-20 22:14   ` Wolfgang Denk
2009-07-11  0:03 ` [U-Boot] [PATCH v2 0/6] Clean up top-level directory structure Shinya Kuribayashi
2009-07-11  0:40   ` Peter Tyser
2009-07-11  1:20     ` Shinya Kuribayashi
2009-07-11  2:42       ` Mike Frysinger
2009-07-12 12:54         ` Jean-Christophe PLAGNIOL-VILLARD
2009-07-14 15:20           ` Peter Tyser [this message]
2009-07-15  3:25             ` Stefan Roese
2009-07-15  3:38             ` Shinya Kuribayashi
2009-07-15  4:39               ` Peter Tyser
2009-07-18 11:19                 ` Jean-Christophe PLAGNIOL-VILLARD
2009-07-18 16:37                   ` Peter Tyser
2009-07-18 16:39                     ` Jean-Christophe PLAGNIOL-VILLARD
2009-07-18 18:07                     ` Wolfgang Denk
2009-07-19 20:01                       ` Peter Tyser
2009-07-19 20:16                         ` Wolfgang Denk
2009-07-20 22:15                         ` Wolfgang Denk
2009-07-20 23:09                           ` Peter Tyser
2009-07-15 14:50             ` Rafal Jaworowski
2009-07-18 16:52               ` Peter Tyser
2009-07-18 18:10                 ` Wolfgang Denk

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=1247584843.30723.18.camel@localhost.localdomain \
    --to=ptyser@xes-inc.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