From: Nick Garnett <nickg@ecoscentric.com>
To: Andrew Lunn <andrew.lunn@ascom.ch>
Cc: John Dallaway <john@dallaway.org.uk>,
ecos-maintainers@ecos.sourceware.org
Subject: Re: AT91EB55 and DataFlash
Date: Thu, 12 Feb 2009 14:43:00 -0000 [thread overview]
Message-ID: <m3k57vsokd.fsf@xl5.calivar.com> (raw)
In-Reply-To: <20090212143209.GO24614@donkey.ma.tech.ascom.ch>
Andrew Lunn <andrew.lunn@ascom.ch> writes:
> On Thu, Feb 12, 2009 at 02:27:13PM +0000, Nick Garnett wrote:
> > All of the redboot ECM files for our boards with dataflash contain
> > CYGPKG_ERROR. CYGPKG_DEVS_FLASH_ATMEL_DATAFLASH does not, but the AT91
> > SPI driver needs it.
>
> Yep, that was were it exploded. However, it should of been at
> ecosconfig time it complained. The AT91 SPI driver is missing a
> requires statement for CYGPKG_ERROR.
Yes, I can add that easily enough.
> I guess the error package should
> be added to all targets which use the AT91 SPI driver.
That's a bit tricky, since it would require CYGPKG_ERROR to be added
to the target in ecos.db. Which is not really right. I guess normally
we rely on CYGPKG_ERROR being in the template to resolve this.
--
Nick Garnett eCos Kernel Architect
eCosCentric Limited http://www.eCosCentric.com The eCos experts
Barnwell House, Barnwell Drive, Cambridge, UK. Tel: +44 1223 245571
Registered in England and Wales: Reg No: 4422071
Besuchen Sie uns vom 3.-5.03.09 auf der Embedded World 2009, Stand 11-300
Visit us at Embedded World 2009, Nürnberg, Germany, 3-5 Mar, Stand 11-300
prev parent reply other threads:[~2009-02-12 14:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 12:08 John Dallaway
2009-02-12 12:56 ` Andrew Lunn
2009-02-12 13:50 ` Andrew Lunn
2009-02-12 14:23 ` John Dallaway
2009-02-12 14:31 ` Nick Garnett
2009-02-12 14:38 ` John Dallaway
2009-02-12 14:27 ` Nick Garnett
2009-02-12 14:32 ` Andrew Lunn
2009-02-12 14:43 ` Nick Garnett [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=m3k57vsokd.fsf@xl5.calivar.com \
--to=nickg@ecoscentric.com \
--cc=andrew.lunn@ascom.ch \
--cc=ecos-maintainers@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).