From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-patches@ecos.sourceware.org
Subject: [Bug 1001449] AT25DFxxx SPI flash test application
Date: Sun, 08 Jan 2012 08:46:00 -0000 [thread overview]
Message-ID: <20120108084639.F117F2F78006@mail.ecoscentric.com> (raw)
In-Reply-To: <bug-1001449-104@http.bugs.ecos.sourceware.org/>
Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001449
--- Comment #3 from Christophe Coutand <ecos@hotmail.co.uk> 2012-01-08 08:46:38 GMT ---
Hi Ilija,
I replaced the CDL with CYGNUM_DEVS_FLASH_SPI_AT25XXX_MAP_ADDR but maybe the
name shall still specify device 0. The platform could have several SPI flash.
In the attached solution CYGNUM_DEVS_FLASH_SPI_AT25XXX_MAP_ADDR is defined at
the platform level. The SPI flash test application accesses the definition by
including the platform header file:
#include CYGDAT_DEVS_FLASH_SPI_AT25DFXXX_PLF_CDL
I agree, more could be defined in the platform CDL such as the speed. Bus and
chip select are usually fix.
Christophe
--
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2012-01-08 8:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-08 8:37 [Bug 1001449] New: " bugzilla-daemon
2012-01-08 8:38 ` [Bug 1001449] " bugzilla-daemon
2012-01-08 8:38 ` bugzilla-daemon
2012-01-08 8:46 ` bugzilla-daemon [this message]
2012-01-09 20:39 ` bugzilla-daemon
2012-02-26 11:24 ` bugzilla-daemon
2012-02-26 20:23 ` bugzilla-daemon
2012-03-12 21:58 ` bugzilla-daemon
2012-03-13 19:18 ` bugzilla-daemon
2012-03-13 21:05 ` bugzilla-daemon
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=20120108084639.F117F2F78006@mail.ecoscentric.com \
--to=bugzilla-daemon@bugs.ecos.sourceware.org \
--cc=ecos-patches@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).