From: Finn Nielsen <AstroFinn@tiscali.dk>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Generalized dataflash interface
Date: Sat, 11 Feb 2006 10:23:29 +0100 [thread overview]
Message-ID: <43EDAD11.6060802@tiscali.dk> (raw)
Hello All,
New to the list by the way.
Does anyone have a recommendation on how to add general support for
Atmel Dataflash, using generalized access routines (a driver) - and then
what about the existing Atmel AT91xxx specific code ?
I guess one would need to encapsulate the existing Atmel routines, add
config capability for choosing the interface driver code and then test
it. Would anyone be willing to test it on a AT91xxx platform ??
Would be sad if I just added dataflash capability for my own stuff.
Others have talked about generalising the dataflash interface, not too
long ago..
Can anyone confirm that the environment functions are encapsulated, so
that the environment could lie in a Dataflash ? A few systems don't have
a parallel flash at all.
Regards,
Finn Nielsen
next reply other threads:[~2006-02-11 9:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-11 9:23 Finn Nielsen [this message]
2006-02-13 9:45 ` [U-Boot-Users] Generalized dataflash interface Peter Menzebach
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=43EDAD11.6060802@tiscali.dk \
--to=astrofinn@tiscali.dk \
--cc=u-boot@lists.denx.de \
/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