From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] MTD/SPI/FLASH: add support for Ramtron FRAMs using SPI
Date: Sat, 28 Aug 2010 18:26:50 -0400 [thread overview]
Message-ID: <201008281826.51296.vapier@gentoo.org> (raw)
In-Reply-To: <4C798A8F.2040402@emk-elektronik.de>
On Saturday, August 28, 2010 18:15:43 Reinhard Meyer wrote:
> Dear Mike Frysinger,
> > On Thursday, August 26, 2010 16:00:50 Reinhard Meyer wrote:
> > interesting, but what if we push it further. something like this
> > (untested):
>
> That code does not address the following issues to complete extend:
>
> 1. JEDEC conformant that have ID in first byte
> 2. JEDEC conformant that have ID in later byte
why doesnt it ? look at the structure i created a bit closer as well as the
code that parses it.
> The question that remains is if any ID can be assigned twice in different
> positions and them meaning different manufacturers?
>
> 7f 7f 7f 7f 7f 7f c2 = ramtron
{ 6, 0xc2, ramtron_probe, },
> 7f 7f 7f c2 = some other manufacturer?
{ 3, 0xc2, some_other_manu_probe, },
> 3. non JEDEC conformant or those that do not honor the read-id command
> and thus present 0xff _if_ the MISO line is pulled up
that isnt really changed at all by my patch. there is a simple idcode[0] ==
0xff branch for people to call probe functions which are prepared to handle
non-jedec compatible probes.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20100828/aba6ebe5/attachment.pgp
next prev parent reply other threads:[~2010-08-28 22:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-25 12:47 [U-Boot] [PATCH] MTD/SPI/FLASH: add support for Ramtron FRAMs using SPI Reinhard Meyer
2010-08-26 2:31 ` Mike Frysinger
2010-08-26 5:57 ` Reinhard Meyer
2010-08-26 6:12 ` Mike Frysinger
2010-08-26 6:24 ` Reinhard Meyer
2010-08-26 8:27 ` Reinhard Meyer
2010-08-26 9:11 ` Mike Frysinger
2010-08-26 20:00 ` Reinhard Meyer
2010-08-28 21:48 ` Mike Frysinger
2010-08-28 22:15 ` Reinhard Meyer
2010-08-28 22:26 ` Mike Frysinger [this message]
2010-08-28 23:17 ` Mike Frysinger
2010-08-28 23:45 ` Reinhard Meyer
2010-08-29 0:14 ` Mike Frysinger
2010-08-29 1:59 ` Reinhard Meyer
2010-08-29 2:26 ` Mike Frysinger
2010-08-29 3:35 ` Reinhard Meyer
2010-08-29 4:34 ` Mike Frysinger
2010-08-29 4:52 ` Reinhard Meyer
2010-09-07 20:12 ` Peter Tyser
2010-09-07 19:38 ` Wolfgang Denk
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=201008281826.51296.vapier@gentoo.org \
--to=vapier@gentoo.org \
--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;
as well as URLs for NNTP newsgroup(s).