linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: Ruedi.Hofer@ascom.ch
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: RomFS
Date: Tue, 01 Feb 2000 08:53:42 +0100	[thread overview]
Message-ID: <200002010753.IAA28148@denx.local.net> (raw)
In-Reply-To: Your message of "Tue, 01 Feb 2000 07:55:45 +0100." <0FP80082UOL8BN@pmdf-it.hasler.ascom.ch>


In message <0FP80082UOL8BN@pmdf-it.hasler.ascom.ch> you write:
>
> I think i've seen a posting before by a guy alex@signum.se who has written
> a flash file system, you might be able to steal some code from him.
> Search the linuxppc-dev and linuxppc-embedded lists.

Right, but he told me that he does not  maintain  this  code,  and  I
found  several  problems  with it. I fixed those for the systems I am
using (TQM8xxL modules). I  have  both  character  device  and  block
device  drivers  for  the FLASH memory on these systems. It works for
me, YMMV.

If my time permits I am willing to help if anybody is going  to  test
this  code  on  other  systems  as well - it will need a bit of work,
though.

You can find my current code as oatch  against  the  original  2.2.13
kernel  in  the  files  FLASH.patch  (for  the  character device) and
FTL.patch (for the block device) which are included in
ftp://ftp.denx.de/pub/LinuxPPC/usr/src/CDK.tar.gz

Not however, that this block device driver  re-uses  the  FTL  (Flash
Translation Layer) code from the PC-Card (PCMCIA) implementation. You
can  use  the charatcer device driver to put a new raw file (with any
filesystem image you like in it) into FLASH memory, but the FTL  code
is  probably  too difficult to include into 8xxrom - and you need it,
since it uses specal formatting of the erase  regions  used  for  the
block device.

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
Contrary to popular belief, thinking does not cause brain damage.

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

  reply	other threads:[~2000-02-01  7:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-01  6:55 Re: RomFS Ruedi.Hofer
2000-02-01  7:53 ` Wolfgang Denk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-02-01  6:55 RomFS Ruedi.Hofer
2000-01-31 15:12 RomFS Ruedi.Hofer

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=200002010753.IAA28148@denx.local.net \
    --to=wd@denx.de \
    --cc=Ruedi.Hofer@ascom.ch \
    --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).