public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [patch] add support for "eeprom info"
Date: Fri, 25 Jan 2008 12:21:11 -0500	[thread overview]
Message-ID: <200801251221.12389.vapier@gentoo.org> (raw)
In-Reply-To: <479A1450.40805@comcast.net>

On Friday 25 January 2008, J. William Campbell wrote:
> Mike Frysinger wrote:
> > On Friday 25 January 2008, Wolfgang Denk wrote:
> >> Well, there is a big difference between NOR flash  and  your  device:
> >> NOR  flash is memory, but your's is a storage device attached to some
> >> bus interface (SPI here). The problem is that we don't  have  a  good
> >> solution to interface with such devices yet.
> >>
> >> Using the eeprom command for such devices is misleading, IMO. If  you
> >> can  live  with the spiflash command, then this is not perfect, but I
> >> guess it will have to do for now as we don't have a  better  solution
> >> yet.
> >
> > so we're clear, the proposed interface is:
> > spiflash info
> > spiflash <read|write> address offset count
> > spiflash erase offset count
>
> This sounds fine to me. The address is obviously a ram
> source/destination address. I vote for an offset in bytes and a count in
> bytes. If the offset is not an appropriate sector boundary, it is an
> error. The count can be a partial sector without problems. Having the
> offset and count in different units is confusing IMHO, so bytes for
> both.

it would be exactly the same as all other interfaces.  we dont hold the users 
hand by calculating pages for them in other places, so we wont here either.  
in other words, yes. ;)

> Also, Mike, I assume you will also add a module similar to 
> env_eeprom.c to support environment in spiflash?

yes
-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/20080125/9352d0aa/attachment.pgp 

      reply	other threads:[~2008-01-25 17:21 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
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 [this message]

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=200801251221.12389.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