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 5/9] SPEAr600 SoC support added
Date: Wed, 16 Dec 2009 12:28:05 -0600	[thread overview]
Message-ID: <1260988086.11634.3576.camel@localhost.localdomain> (raw)
In-Reply-To: <4B29205B.9040100@st.com>

Hi Arm,

<snip>

> > It'd also be nice to give a description of each board and SOC you add.
> > Eg what's the difference between the 300, 310, 320, 600?  What
> > peripherals do they support?  What does SPEAr stand for?  More commit
> > messages in general wouldn't hurt:)
> >   
> SPEAr (Structured Processor Enhanced Architecture).
> You can find some description throughout Internet, for example here:
> 
> http://embedded-system.net/spear-basic-customizable-arm-based-soc-stmicroelectronics.html
> (SPEARBasic means SPEAr300.)
> 
> As you can see this SoC family embeds a customizable logic that could
> be programmed one-time by a customer at silicon mask level (i.e. not at 
> runtime!).
> 
> We are now adding the support in u-boot for two SoC: SPEAr600 and SPEAr3xx.
> Pls note that SPEAr300/310/320 differs only for the default customization.
> 
> All 4 SoCs share common peripherals.
> 
> 1. ARM926ejs core based (sp600 has two AMP cores, the 2nd handled only 
> in Linux)
> 2. FastEthernet (sp600 has Gbit version, but same controller - GMAC)
> 3. USB Host
> 4. USB Device
> 5. NAND controller (FSMC)
> 6. Serial NOR ctrl
> 7. I2C
> 8. SPI
> 9. CLCD
> 10. others ..
> 
> sp600 is not customized by default.
> 
> sp3xx are differently customized...
> sp300 is more oriented to TELECOM/video (it has tdm, i2s, ITU i/f support)
> sp310 for networking (a part GMAC in fixed part, it has 5 MACB ctrls in 
> custom)
> sp320 for industrial (SPP ctrl, CAN ctrl, 2 MACBs, ...)
> 
> Everything is supported in Linux.
> u-boot is not currently supporting all peripeharls (just a few).

I see.  It'd be nice to put some of the above information in the U-Boot
commit logs to give people an idea about what's going on without having
to use google, etc.

I haven't looked at the code differences between the sp3xx boards, but
you might be able to use 1 common board file/header file to support them
all.  For example, take a look at the M5475AFE_config rule in
U-Boot's ./Makefile.  Some extra code in the Makefile and some #ifdefs
in the sp3xx code might accommodate all 3 boards.

Best,
Peter

  reply	other threads:[~2009-12-16 18:28 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-16  9:18 [U-Boot] [PATCH 0/9] Support for SPEAr SoCs Vipin KUMAR
2009-12-16  9:18 ` [U-Boot] [PATCH 1/9] i2c driver support " Vipin KUMAR
2009-12-16  9:18   ` [U-Boot] [PATCH 2/9] smi " Vipin KUMAR
2009-12-16  9:18     ` [U-Boot] [PATCH 3/9] nand " Vipin KUMAR
2009-12-16  9:18       ` [U-Boot] [PATCH 4/9] usbd driver and usb boot firmware " Vipin KUMAR
2009-12-16  9:18         ` [U-Boot] [PATCH 5/9] SPEAr600 SoC support added Vipin KUMAR
2009-12-16  9:18           ` [U-Boot] [PATCH 6/9] SPEAr300 " Vipin KUMAR
2009-12-16  9:18             ` [U-Boot] [PATCH 7/9] SPEAr310 " Vipin KUMAR
2009-12-16  9:18               ` [U-Boot] [PATCH 8/9] SPEAr320 " Vipin KUMAR
2009-12-16  9:18                 ` [U-Boot] [PATCH 9/9] SPEAr600 build " Vipin KUMAR
2009-12-17 20:14                   ` Wolfgang Denk
2009-12-19  7:26                     ` Vipin Kumar
2009-12-17 20:14                 ` [U-Boot] [PATCH 8/9] SPEAr320 SoC " Wolfgang Denk
2009-12-19  7:21                   ` Vipin Kumar
2009-12-17 20:13               ` [U-Boot] [PATCH 7/9] SPEAr310 " Wolfgang Denk
2009-12-19  7:19                 ` Vipin Kumar
2009-12-17 20:09             ` [U-Boot] [PATCH 6/9] SPEAr300 " Wolfgang Denk
2009-12-19  7:10               ` Vipin Kumar
2009-12-19  7:25                 ` Wolfgang Denk
2009-12-19  7:58                   ` Vipin Kumar
2009-12-16 17:30           ` [U-Boot] [PATCH 5/9] SPEAr600 " Peter Tyser
2009-12-16 18:00             ` Armando VISCONTI
2009-12-16 18:28               ` Peter Tyser [this message]
2009-12-17 22:44                 ` Wolfgang Denk
2009-12-17 22:54                   ` Peter Tyser
2009-12-17 23:13                     ` Wolfgang Denk
2009-12-19  7:31                       ` Vipin Kumar
2009-12-16 23:09           ` Wolfgang Denk
2009-12-19  8:56             ` Vipin Kumar
2009-12-16 22:56         ` [U-Boot] [PATCH 4/9] usbd driver and usb boot firmware support for SPEAr SoCs Wolfgang Denk
2009-12-19  7:02           ` Vipin Kumar
2009-12-19  7:24             ` Wolfgang Denk
2009-12-19  8:46               ` Vipin Kumar
2010-01-04 23:06       ` [U-Boot] [PATCH 3/9] nand driver " Scott Wood
2010-01-05  3:53         ` Vipin KUMAR
2009-12-16 22:44     ` [U-Boot] [PATCH 2/9] smi " Wolfgang Denk
2009-12-19  6:44       ` Vipin Kumar
2009-12-19  7:20         ` Wolfgang Denk
2009-12-19  7:56           ` Vipin Kumar
2009-12-19  7:59             ` Albert ARIBAUD
2009-12-19  8:28               ` Vipin Kumar
2009-12-19 21:37             ` Wolfgang Denk
2009-12-16 22:31   ` [U-Boot] [PATCH 1/9] i2c " Wolfgang Denk
2009-12-16 16:49 ` [U-Boot] [PATCH 0/9] Support " Armando VISCONTI

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=1260988086.11634.3576.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