public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] flread: new command for reading indirect mapped flashes
Date: Fri, 10 Jul 2009 16:27:15 +0200	[thread overview]
Message-ID: <200907101627.15704.sr@denx.de> (raw)
In-Reply-To: <200907061047.41621.sr@denx.de>

On Monday 06 July 2009 10:47:41 Stefan Roese wrote:
> > > > i guess each flash type would parse the additional commands however
> > > > it liked and so the mtd command would just act as a multiplexer at
> > > > this point. the current spi flash "sf" command is pretty flexible --
> > > > you specify the spi chip select to select the device and you can
> > > > specify other parameters dynamically (like frequency).  so when
> > > > folding it in, we'd have: => mtd device sf <cs> [speed] [mode]
> > > >
> > > > common/cmd_mtd.c
> > > > common/cmd_mtd_sf.c
> > > > common/cmd_mtd_nor.c
> > >
> > > I was more thinking about adding the MTD layer to all FLASH types
> > > supported by this new commandset. Then accessing the device is done via
> > > the MTD functions pointers (mtd->erase, mtd->read, etc). Special FLASH
> > > type specific stuff still needs to be handled in some additional
> > > drivers (like OOB handling for NAND/OneNAND, or SF specific stuff)
> > > though.
> >
> > ok, this seems like it should be doable in a gradual progression.  i.e.
> > today i am only concerned with nor flash, so getting a base framework
> > with that as the only supported flash should be fine.  once we know it
> > can replace the existing cmd_flash.c functions, we can look at folding in
> > other flash types. -mike
>
> I think this is a doable approach. But we first need a general consent on
> this. Other opinions on this are welcome...

No further responses on this. So it seems nobody objects this approach to move 
to a common command interface for all flash types.

Mike, what are your plans here? Will you work in this "mtd" commands interface 
at some time?

Thanks.

Best regards,
Stefan

=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office at denx.de
=====================================================================

  reply	other threads:[~2009-07-10 14:27 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-30 18:44 [U-Boot] [PATCH] flread: new command for reading indirect mapped flashes Mike Frysinger
2009-06-30 19:01 ` Mike Frysinger
2009-07-04 23:39 ` Wolfgang Denk
2009-07-05  3:07   ` Mike Frysinger
2009-07-05 15:15     ` Wolfgang Denk
2009-07-05 17:12       ` Mike Frysinger
2009-07-05 17:55         ` Wolfgang Denk
2009-07-05 19:03           ` Mike Frysinger
2009-07-05 20:34             ` Wolfgang Denk
2009-07-06  5:10               ` Stefan Roese
2009-07-06  5:59                 ` Mike Frysinger
2009-07-06  6:24                   ` Stefan Roese
2009-07-06  7:04                 ` Mike Frysinger
2009-07-06  7:25                   ` Stefan Roese
2009-07-06  8:37                     ` Mike Frysinger
2009-07-06  8:47                       ` Stefan Roese
2009-07-10 14:27                         ` Stefan Roese [this message]
2009-07-10 14:31                         ` Mike Frysinger
2009-07-06  6:42               ` Mike Frysinger
2009-07-06  8:03                 ` 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=200907101627.15704.sr@denx.de \
    --to=sr@denx.de \
    --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