From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [patch] add support for "eeprom info"
Date: Thu, 24 Jan 2008 00:17:45 -0500 [thread overview]
Message-ID: <200801240017.46171.vapier@gentoo.org> (raw)
In-Reply-To: <479812EB.7060000@gmail.com>
On Wednesday 23 January 2008, Ben Warren wrote:
> Hey Mike,
>
> Mike Frysinger wrote:
> > On Wednesday 23 January 2008, Wolfgang Denk wrote:
> >> In message <200801231729.18316.vapier@gentoo.org> you wrote:
> >>> with eeprom_info behind CONFIG_SPI. most SPI flashes nowadays support
> >>> the jedec id command which allows for dynamic detection (which is how
> >>> the Blackfin SPI driver that i wrote works). hook up any SPI flash and
> >>> it "just works".
> >>
> >> I think you are doing something wrong when you try to use "eeprom" to
> >> access "SPI flash" - these are differnt entities...
> >
> > then what is the "correct" method ? i dont see any other usable option
> > in u-boot for hooking up SPI flashes without writing my own subsystem.
>
> Until recently SPI in U-boot was synonymous with 'SPI-based EEPROM'. In
> fact, CONFIG_SPI doesn't mean 'configure support for a SPI controller',
> it means 'configure support for a SPI EEPROM'. This is of course yet
> another artifact from another day that it would be nice to clean up.
i'm aware of this
> I introduced CONFIG_HARD_SPI in the latest release cycle, and included a
> driver for a Freescale controller. It would be nice to have other
> drivers added for generic SPI support. My preference would be for you
> to expand the 'spi' command with something like:
>
> 'spi eeprom info'
i dont see how in the long run, this is any different from today. Wolfgang
can still argue that the SPI flash is not an eeprom device, so "spi
eeprom ..." is not appropriate. which means there is still no subsystem
whatsoever for accessing SPI flashes.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 827 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20080124/210854d5/attachment.pgp
next prev parent reply other threads:[~2008-01-24 5:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-23 16:13 [U-Boot-Users] [patch] add support for "eeprom info" Mike Frysinger
2008-01-23 21:06 ` Wolfgang Denk
2008-01-23 21:15 ` Mike Frysinger
2008-01-23 21:23 ` Wolfgang Denk
2008-01-23 22:29 ` Mike Frysinger
2008-01-24 0:44 ` Wolfgang Denk
2008-01-24 3:39 ` Mike Frysinger
2008-01-24 4:24 ` Ben Warren
2008-01-24 5:17 ` Mike Frysinger [this message]
2008-01-24 11:13 ` Wolfgang Denk
2008-01-25 13:31 ` Mike Frysinger
2008-01-24 9:13 ` Mike Frysinger
2008-01-24 11:31 ` Wolfgang Denk
2008-01-25 13:33 ` Mike Frysinger
2008-01-25 15:09 ` Wolfgang Denk
2008-01-25 16:02 ` Mike Frysinger
2008-01-25 16:54 ` J. William Campbell
2008-01-25 17:21 ` Mike Frysinger
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=200801240017.46171.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