public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: John Dallaway <john@dallaway.org.uk>
To: Andrew Lunn <andrew.lunn@ascom.ch>, Nick Garnett <nickg@ecoscentric.com>
Cc: ecos-maintainers@ecos.sourceware.org
Subject: Re: AT91EB55 and DataFlash
Date: Thu, 12 Feb 2009 14:23:00 -0000	[thread overview]
Message-ID: <499430C6.90209@dallaway.org.uk> (raw)
In-Reply-To: <20090212134950.GL24614@donkey.ma.tech.ascom.ch>

Andrew Lunn wrote:

> It looks like the requires statement is wrong, CYGPKG_ERROR is not
> needed by dataflash. This fixes this problem, but it then explodes
> later.
> 
> I think somebody from eCosCentric needs to look at this and compare
> with there working code in their private branch.

Andrew, many thanks for looking at this. It appears that the data type
expected in the second parameter of the CYG_DATAFLASH_FLASH_DRIVER()
macro has changed.

Nick, it looks like you were the one who added the DataFlash
declarations for AT91EB55 originally. Do you have any time to
investigate this build failure at present?

> /var/local/ecos-test/packages/devs/flash/arm/eb55/current/src/eb55_flash.c:76: error: initializer element is not constant
> /var/local/ecos-test/packages/devs/flash/arm/eb55/current/src/eb55_flash.c:76: error: (near initialization for ‘cyg_dataflash_priv_cyg_eb55_dataflash.dev.spi_dev’)

Please let me know either way, so I can plan accordingly.

Thanks

John Dallaway

  reply	other threads:[~2009-02-12 14:23 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 [this message]
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

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=499430C6.90209@dallaway.org.uk \
    --to=john@dallaway.org.uk \
    --cc=andrew.lunn@ascom.ch \
    --cc=ecos-maintainers@ecos.sourceware.org \
    --cc=nickg@ecoscentric.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).