public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: "Jürgen Lambrecht" <J.Lambrecht@televic.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: ecos-maintainers@ecos.sourceware.org
Subject: Re: AT91
Date: Fri, 18 Jul 2008 14:16:00 -0000	[thread overview]
Message-ID: <4880A599.3040008@televic.com> (raw)
In-Reply-To: <20080718115742.GA24316@lunn.ch>

Andrew Lunn wrote:
> On Fri, Jul 18, 2008 at 01:50:40PM +0200, J?rgen Lambrecht wrote:
>   
>> We work with AT91 ARM chips. I can help there.
>> OK, now I have a clear deadline to commit a (nearly ;-) bugfree at91  
>> EMAC ethernet driver.
>>     
>
> Help with AT91 platforms would be great. I have AT91SAM7X-EK and
> AT91SAM7S-EK boards. What i don't have is any boards with external
> memory interfaces. Without that, using the FreeBSD stack is
> impossible, which is why you have found all these EMAC issues. So if
> you can test on bigger AT91 systems that would be great.
>   
ok. We have boards with an AT91M55800A with NOR flash, SRAM, Compact 
Flash and memory-mapped Ethernet. And we have boards with an AT91SAM9260 
with NOR flash, NAND flash, SDRAM and MII Ethernet.
We also have the Atmel EKs with those processors. I would like to add 
the arm9 board to ecos ... one day.

Our network is the backbone of the system and must be very reliable, 
hence the heavy tests we run. (Our UDP test perl script is GPL if you 
would be interested)
> Also, please don't leave you patch to the last minute. We need to work
> on a clean way to handle the copy from SDRAM into SRAM for your
> platform without imposing it on other AT91 devices which don't need
> it. This might take a couple of iterations to get right.
>   
OK.
Kind regards,
Juergen
>         Andrew
>   


      reply	other threads:[~2008-07-18 14:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-18 11:51 AT91 Jürgen Lambrecht
2008-07-18 11:58 ` AT91 Andrew Lunn
2008-07-18 14:16   ` Jürgen Lambrecht [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=4880A599.3040008@televic.com \
    --to=j.lambrecht@televic.com \
    --cc=andrew@lunn.ch \
    --cc=ecos-maintainers@ecos.sourceware.org \
    /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).