All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Scharsig <js_at_ng@scharsoft.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [Patch 0/8] add at91 SoC access with c structures
Date: Sat, 19 Dec 2009 21:08:29 +0100	[thread overview]
Message-ID: <hgjbk8$agt$1@ger.gmane.org> (raw)

Hello,

on request by Wolfgang, I have try to implement SoC access for AT91
arch with c structures. Additional I have add support for AT91RM9200
in at91 tree.
I need to switch to a different project for more than half a year.
So I think, it's time to publish the result.

What this Patch set do:

* add's the new temporary CONFIG_AT91_LEGACY to all board configs
  that not converted by this patch
* add's a warning to all files, that not converted by this patch
* add's the support for AT91RM9200 in at91 tree
* add's c stucture SoC defines
* convert all files cpu/../at91 to use c stucture SoC access
* move the at gpio access to a real driver
* add's at91_emac (AT91RM9200) network driver (NET_MULTI)
* add's a new board (eb_cpux9k2) which demonstrates, how to use
  boards with AT91RM9200 cpu in at91 arch tree
* convert following board: at91sam9263ek

this patch was tested with at91sam9263ek, eb_cpux9k2 and
eol board with at91sam9261 cpu. 

What is to do:

* convert all at91sam boards to new soc access
* convert all at91rm9200 boards from AT91RM9200 arch to at91 arch
* convert driver to new soc access
* remove legacy code, if all boards and drives are ready

I hope there are somewhere a some volunteers to make the next steps.

Best regards

Jens Scharsig

             reply	other threads:[~2009-12-19 20:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-19 20:08 Jens Scharsig [this message]
     [not found] ` <4B2FF24A.9020201@windriver.com>
2009-12-22  7:39   ` [U-Boot] [Patch 0/8] add at91 SoC access with c structures Jens Scharsig

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='hgjbk8$agt$1@ger.gmane.org' \
    --to=js_at_ng@scharsoft.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.