public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: "Jürgen Lambrecht" <J.Lambrecht@televic.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: "john@dallaway.org.uk" <john@dallaway.org.uk>,
		"ecos-devel@ecos.sourceware.org"
	<ecos-devel@ecos.sourceware.org>,
	Deroo  Stijn <S.Deroo@TELEVIC.com>
Subject: Re: Re: NAND review
Date: Wed, 03 Jun 2009 13:33:00 -0000	[thread overview]
Message-ID: <4A267B93.3040401@televic.com> (raw)
In-Reply-To: <20090603085115.GA27508@lunn.ch>

Andrew Lunn wrote:
>> Date: Tue, 02 Jun 2009 19:17:58 +0100
>> From: John Dallaway <john@dallaway.org.uk>
>> To: Andrew Lunn <andrew.lunn@ascom.ch>
>> CC: eCos Maintainers <ecos-maintainers@ecos.sourceware.org>
>> Subject: Re: NAND & YAFFS
>>
>> Have you been able to form a view on the relative merits of the VU
>> Amsterdam and eCosCentric implementations so far? Just wanting to ensure
>> that this process is not stalled for any reason...
>>
>> John Dallaway
>>     
>
>   
<snip>

> There was an email from Rutger that Televic are willing to contribute
> their drivers for an AT91SAM9260 based board. If that happens, it
> would mean two real implementations for Rutgers, vs one for Ross.
>
>   
Indeed, we would like to contribute, but it takes time...
Stijn will try to do the contribution, I will get the FSF copyright 
assignment (but the site is down today..).

Kind regards,
Jürgen

<snip>
>          Andrew
>   


  parent reply	other threads:[~2009-06-03 13:33 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-19  8:27 Simon Kallweit
2009-05-19 13:47 ` Ross Younger
2009-05-19 14:17   ` Andrew Lunn
2009-05-20 13:24     ` Bart Veer
2009-05-20 13:34       ` Rutger Hofman
2009-05-20 13:53         ` Andrew Lunn
2009-05-20 13:56           ` Gary Thomas
2009-05-20 14:22             ` Andrew Lunn
2009-05-20 15:22               ` Andrew Lunn
2009-05-20 15:34               ` Bart Veer
2009-05-20 13:58           ` Rutger Hofman
2009-05-20 14:16     ` Ross Younger
2009-05-20 14:21       ` Gary Thomas
2009-05-20 15:25         ` Ross Younger
2009-05-20 15:37           ` Gary Thomas
2009-05-19 16:29 ` Andrew Lunn
2009-06-03  8:51   ` Andrew Lunn
2009-06-03 10:21     ` Ross Younger
2009-06-03 10:48       ` Andrew Lunn
2009-06-03 11:52         ` Simon Kallweit
2009-06-03 12:26         ` Rutger Hofman
2009-06-03 13:33     ` Jürgen Lambrecht [this message]
2009-06-10 17:39     ` Nick Garnett
2009-06-11 11:25       ` Rutger Hofman
2009-06-13 16:31       ` Andrew Lunn
2009-06-18 14:10         ` Nick Garnett
2009-06-19  7:47           ` Andrew Lunn
2009-06-19 14:14             ` Ross Younger
2009-06-19 15:02               ` Andrew Lunn
2009-06-19 16:54               ` Jürgen Lambrecht
2009-06-29 11:09             ` Nick Garnett
2009-06-19  8:07           ` Andrew Lunn
2009-06-19 11:37             ` Daniel Morris
2009-06-19 12:06               ` Andrew Lunn
2009-05-20  1:02 ` Jonathan Larmour
2009-05-20  7:11   ` Simon Kallweit
2009-05-20 11:12     ` Rutger Hofman
2009-05-20 11:29       ` Simon Kallweit
2009-05-20 13:37         ` Rutger Hofman

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=4A267B93.3040401@televic.com \
    --to=j.lambrecht@televic.com \
    --cc=S.Deroo@TELEVIC.com \
    --cc=andrew@lunn.ch \
    --cc=ecos-devel@ecos.sourceware.org \
    --cc=john@dallaway.org.uk \
    /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).