All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Where to put semi-common files?
Date: Tue, 3 Apr 2007 21:29:36 +0200	[thread overview]
Message-ID: <200704032129.36433.sr@denx.de> (raw)
In-Reply-To: <1175627358.17141.51.camel@ld0161-tx32>

Hi Jon,

On Tuesday 03 April 2007 21:09, Jon Loeliger wrote:
> We are needing to introduce the 8544 DS board soon.
> It's board is essentially identical to the board in the 8641HPCN.
> Both boards have an FPGA on them that controls carious system
> parameters and configuraiton parts, including the reset logic
> that we've already discussed.  That FPGA is called "PIXIS" and
> has support code for it already added to the 8641hpcn's directory.
>
> Naturally, we need exactly the same code for the 8544 DS board
> now too.  But it can't be in a shared board directory, nor are
> the two SoC parts even in the same CPU families.  One is 85xx,
> the other is 86xx.  The FPGA isn't really a device for which one
> might think "driver/", so that likely isn't the right directory
> either.  Perhaps lib_ppc/?

I would suggest to start moving your Freescale boards ports into a freescale 
directly:

board/freescale/mpc8349itx/
	       /mpc832xemds/
...

Then you could add a common freescale directory, as done already for "esd" 
or "prodrive":

board/esd/common/

If you take a look at this directory you will notice here some common FPGA 
code (and others stuff too). This is not CPU specific and not a generic 
driver, so it shouldn't be moved to the cpu/xxx or drivers/xxx directories.

Any other opinions?

> Actually, there are other very similar bodies of code that are
> shared across boards and CPU families (for example, the DDR setup
> code in spd_sdram.c).

spd_sdram should be moved to cpu/xxx/ since it's cpu specific and not really a 
driver. We have this for cpu/ppc4xx already in plance for all sorts of 4xx 
SDRAM controllers.

> Do you have a good place where you would like to see this sort
> of shared code?  It is easy enough to pick up just the parts that
> are wanted during compilation due to CONFIG options, but we need
> a directory from which we can share these sources.
>
> Recommendations?

Please see above. Just my 0.02$.

Best regards,
Stefan

=====================================================================
DENX Software Engineering GmbH, HRB 165235 Munich, CEO: Wolfgang Denk
Office:  Kirchenstr. 5,       D-82194 Groebenzell,            Germany
=====================================================================

  reply	other threads:[~2007-04-03 19:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-03 19:09 [U-Boot-Users] Where to put semi-common files? Jon Loeliger
2007-04-03 19:29 ` Stefan Roese [this message]
2007-04-03 19:47   ` Ben Warren

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=200704032129.36433.sr@denx.de \
    --to=sr@denx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.