From: "Koeller, T." <Thomas.Koeller@baslerweb.com>
To: ecos-discuss@sources.redhat.com
Subject: RE: [ECOS] RE: AT91 patches
Date: Thu, 30 Jan 2003 13:13:00 -0000 [thread overview]
Message-ID: <850597605E79D21182830008C7A4B9CF1EB4250E@COMM1> (raw)
Yes, of course, those two things are totally unrelated.
Thomas
-----------------------------------------------
Thomas Koeller, Software Development
Basler Vision Technologies
An der Strusbek 60-62
22926 Ahrensburg
Germany
Tel +49 (4102) 463-390
Fax +49 (4102) 463-46390
mailto:Thomas.Koeller@baslerweb.com
http://www.baslerweb.com
> -----Original Message-----
> From: Jani Monoses [mailto:jani@iv.ro]
> Sent: Thursday, January 30, 2003 1:24 PM
> To: ecos-discuss@sources.redhat.com
> Subject: Re: [ECOS] RE: AT91 patches
>
>
> Jifl, Thomas
> can't the AT91 patch be merged without the flash changes initially?
> The existing EB40 is not using it's first half of the flash anyway
> being reserved for angel.
> So IMHO ther would be a more logical layout for other AT91 variants to
> be worked on and no regression introduced since the EB40
> flash is not multiple sector
> aware AFAIK.
>
> Jani.
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
next reply other threads:[~2003-01-30 12:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-30 13:13 Koeller, T. [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-06 14:15 Koeller, T.
2003-03-06 16:37 ` Jonathan Larmour
2003-01-30 16:12 Koeller, T.
2003-01-30 16:12 Doug Fraser
2003-01-30 16:18 ` Jonathan Larmour
2003-01-30 14:54 Doug Fraser
2003-01-30 15:32 ` Jonathan Larmour
2003-01-30 12:22 Koeller, T.
2003-01-30 12:37 ` Jani Monoses
2003-01-30 15:29 ` Jonathan Larmour
2003-01-30 19:54 ` Daniel Leu
2003-01-30 23:12 ` Jonathan Larmour
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=850597605E79D21182830008C7A4B9CF1EB4250E@COMM1 \
--to=thomas.koeller@baslerweb.com \
--cc=ecos-discuss@sources.redhat.com \
/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).