public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: John Eigelaar <jeigelaar@mweb.co.za>
Cc: ecos-devel@sources.redhat.com
Subject: Re: AT91SAM7X Port
Date: Fri, 12 May 2006 12:09:00 -0000	[thread overview]
Message-ID: <20060512120940.GC23687@lunn.ch> (raw)
In-Reply-To: <pan.2006.05.12.12.05.11.874626@mweb.co.za>

On Fri, May 12, 2006 at 02:05:13PM +0200, John Eigelaar wrote:
> On Fri, 12 May 2006 13:04:41 +0200, Andrew Lunn wrote:
> 
> > 
> > Not yet. There is a strong chance that i will need such a port next
> > month. If this happens i will be tasked by my employer to make the
> > port. So if you are doing a port i suggest we work together. Which of
> > the X peripherals are you interested in? I need an Ethernet driver
> > which i can connect to lwip.
> 
> SPI, UART, EMAC with lwip, probably the same as you do ...

I don`t need SPI. However the existing AT91 SPI driver compiles
cleanly with the SAM7S. So it just needs testing...

> > What may be more of a problem is the two GPIO controllers. The
> > existing code, var HAL, SPI, USART etc, assumes that the pins they use
> > are on GPIO port A. If this is not true with the X it might get
> > messy. We need to compare the S and X and see what is connected where
> > with respect to the GPIO controllers.
> 
> This is actually a problem with the existing S port as well, as the
> alternative peripheral pinouts is not really addressed. This might be a
> good oppurtunity to devise a proper solution for this if we are forced to.

If i remember correctly, i did add them to var_io.h. However nothing
actually uses them.

         Andrew

      reply	other threads:[~2006-05-12 12:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-12  9:25 John Eigelaar
2006-05-12 11:05 ` Andrew Lunn
2006-05-12 12:05   ` John Eigelaar
2006-05-12 12:09     ` Andrew Lunn [this message]

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=20060512120940.GC23687@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=ecos-devel@sources.redhat.com \
    --cc=jeigelaar@mweb.co.za \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).