public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Ulf Samuelsson <ulf@atmel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] arm SoC code in U-Boot.
Date: Tue, 6 Mar 2007 22:55:51 +0100	[thread overview]
Message-ID: <006701c7603a$95ed3930$01c4af0a@Glamdring> (raw)
In-Reply-To: 20070306213633.ACDFE352B84@atlas.denx.de

link: www.avrfreaks.net
----- Original Message ----- 
From: "Wolfgang Denk" <wd@denx.de>
To: "Peter Pearse" <Peter.Pearse@arm.com>
Cc: <u-boot-users@lists.sourceforge.net>; "Ulf Samuelsson" <ulf@atmel.com>; 
"Txema Lopez" <tlopez@aotek.es>; "Grant Likely" <grant.likely@secretlab.ca>
Sent: Tuesday, March 06, 2007 10:36 PM
Subject: Re: [U-Boot-Users] arm SoC code in U-Boot.


> In message <89A528FE6DB0FA44877BB2F05B84671805650CA4@ZIPPY.Emea.Arm.com> 
> you wrote:
>>
>> I could live with cpu/freescale/imx. Presumably it would be built in
>> via the SOC value?
>
> Do we really need the "freescale" subdirectory here? Maybe
> cpu/arm_imx would be a shorter and more descriptive name?
>
> Best regards,
>
> Wolfgang Denk
>


I think it is a matter of taste.
You actually do not need to have any subdirectories in U-boot at all.
Some people prefer using a directory structure to hide information
which is of little interest to them

There seems to be shared code for PowerPCs and NIOS(2).
Do we want to create new subdirectories for every share, cluttering up 
"cpu"?

I think the likelyhood for shared code between different Freescale
PPC is higher than shared code between IBM and Freescale PPC.
Therefore a "freescale" directory could also contains shared PPC code.

Some people would like to have consistency
making it easy to find where things are located.

If you look at what is driving duplication, then you find
that the peripherals are either developed inside a semiconductor
company, or they are licensed from an IP provider.

It makes a lot of sense therefore to dedicate directories
to the providers of IP:
ARM is a provider, but so are also Freescale, Atmel and others.


Best Regards
Ulf Samuelsson

  reply	other threads:[~2007-03-06 21:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-06 17:02 [U-Boot-Users] arm SoC code in U-Boot Peter Pearse
2007-03-06 21:36 ` Wolfgang Denk
2007-03-06 21:55   ` Ulf Samuelsson [this message]
2007-03-06 22:32     ` Wolfgang Denk
2007-03-06 22:45       ` Ulf Samuelsson
2007-03-06 23:51         ` [U-Boot-Users] SDRAM cache inhibit David Clark
2007-03-07  0:06           ` Wolfgang Denk
2007-03-07 15:35             ` David Clark
2007-03-07  6:30         ` [U-Boot-Users] arm SoC code in U-Boot Stefan Roese
2007-03-07 12:37           ` Haavard Skinnemoen
2007-03-07 14:27             ` Ben Warren
2007-03-07 14:39             ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2007-03-08  8:17 TXEMA LOPEZ
2007-03-08  8:40 ` Wolfgang Denk
2007-03-02 10:03 Txema Lopez
2007-03-05 11:38 ` Ulf Samuelsson

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='006701c7603a$95ed3930$01c4af0a@Glamdring' \
    --to=ulf@atmel.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