From: Pink Boy <dasfoo@yahoo.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/5] ARM: Add/Improve support for Atmel AT91RM9200DK/E
Date: Tue, 6 Jan 2009 15:50:52 -0800 (PST) [thread overview]
Message-ID: <374753.76709.qm@web31813.mail.mud.yahoo.com> (raw)
In-Reply-To: <4963BD17.6020703@atmel.com>
Ulf!
Here I was getting ready to try and add support for the AT91RM9200EK
and I see your patches.
I have a question? Does the new AT91RM9200EK support CFI? Is so
no problem for me, otherwise I got that working on last week for my
board based on the AT91RM9200EK (with AT49BV642D flash).
The changes to the at91rm9200ek.h were trivial, however I had to
disable buffered writes as the AT91BV642D didn't support it as
the '642 lies about supporting buffered writes.
I suspect that the AT49BV6414 used on the ek, may have the same issue
as when I was fixing the kernel to support the '642 there was an
identical patch for the 6414 + plus the data sheet doesn't mention
it in the summary.
Matt Harper
Tehama Wireless
next prev parent reply other threads:[~2009-01-06 23:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-06 20:20 [U-Boot] [PATCH 2/5] ARM: Add/Improve support for Atmel AT91RM9200DK/E Ulf Samuelsson
2009-01-06 23:50 ` Pink Boy [this message]
2009-01-07 1:11 ` Jean-Christophe PLAGNIOL-VILLARD
2009-01-07 19:55 ` Ulf Samuelsson
2009-01-07 20:04 ` Jean-Christophe PLAGNIOL-VILLARD
2009-01-08 0:04 ` Ulf Samuelsson
2009-01-07 20:29 ` Ulf Samuelsson
2009-01-07 20:37 ` Ulf Samuelsson
2009-01-07 20:42 ` Jean-Christophe PLAGNIOL-VILLARD
2009-01-07 22:32 ` Ulf Samuelsson
2009-01-07 20:52 ` [U-Boot] new "dataflash_mmc_mux" command in u-boot-at91.git Ulf Samuelsson
2009-01-10 17:12 ` [U-Boot] [PATCH 2/5] ARM: Add/Improve support for Atmel AT91RM9200DK/E Wolfgang Denk
[not found] <20090111041938.GB14620@game.jcrosoft.org>
2009-01-11 22:10 ` Pink Boy
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=374753.76709.qm@web31813.mail.mud.yahoo.com \
--to=dasfoo@yahoo.com \
--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