linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: "Brown, David (dbrown03)" <DBrown03@harris.com>
Cc: "'duncanp@research.canon.com.au'" <duncanp@research.canon.com.au>,
	linuxppc-embedded@lists.linuxppc.org
Subject: Re: flash drivers
Date: Wed, 10 May 2000 16:10:36 +0200	[thread overview]
Message-ID: <200005101410.QAA21548@denx.local.net> (raw)
In-Reply-To: Your message of "Wed, 10 May 2000 09:41:50 EDT." <BE1C564723B3D21191FD0000F840E39801D81514@rfcmx2.rfc.comm.harris.com>


In message <BE1C564723B3D21191FD0000F840E39801D81514@rfcmx2.rfc.comm.harris.com> you wrote:
>
> I'm planning to use drivers/char/amd_flash.c myself, as a flat stream
> "file".

This works fine, and if you have just a  bit  of  configuration  data
which  can  be  mapped  to corresponding erase regions this is a very
straightforward approach. [Maybe you noted that the flash driver does
auto-erase when the length of data written per write() is exactly the
corresponding erase block size. So usually you sill just need to  do:
open   (/dev/flash???),  lseek(specific  erase  region),  write(data,
region size).]

> The ftp://ftp.denx.de/pub/LinuxPPC/usr/src/CDK.tar.gz sources also include a
> flash translation layer (ftl.c) so flash can be used as a read/write
> filesystem.  I won't be using that though, since I noticed a patent
> reference in drivers/block/ftl.c, which an exemption for PCMCIA drivers.  In

Yes, this is a handicap. I tried several times to  get  a  permission
from  M-Systems similar to that they gave for PCMCIA use, but I never
received any repoly.

> linuxppc we're usually talking about on-board flash, so be careful.  I'd
> guess that such encumbered code won't make the standard kernel.

No, and it's not intended to. In fact, this code is more or less just
for demo purposes, not for use in a real product.

> It would be nice if we could have something like drivers/block/ftl.c without
> using patented methods.  If that's not possible, the next best thing would
> be a specific exemption for use on the linuxppc kernels, even if flash is
> on-board instead of PCMCIA.

Have a look  at  ftp://ftp.linux-mtd.infradead.org/pub/mtd/  -  David
Woodhouse  has  provided  some  code  there  which is at least a good
starting point. That's what I will use as  base  if  I  need  such  a
feature in a project.

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
When it is incorrect, it is, at least *authoritatively* incorrect.
- Hitchiker's Guide To The Galaxy

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-05-10 14:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-10 13:41 flash drivers Brown, David (dbrown03)
2000-05-10 14:10 ` Wolfgang Denk [this message]
2000-05-11 21:05 ` Scott Anderson
     [not found] <BE1C564723B3D21191FD0000F840E39801D8151A@rfcmx2.rfc.comm.harris.com>
2000-05-10 20:32 ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2000-04-26  9:29 duncanp
2000-04-26  9:08 ` 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=200005101410.QAA21548@denx.local.net \
    --to=wd@denx.de \
    --cc=DBrown03@harris.com \
    --cc=duncanp@research.canon.com.au \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    /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).