public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: joakim.tjernlund@lumentis.se
Cc: "Robert Kaiser" <rob@sysgo.de>,
	linux-mtd@lists.infradead.org,
	"J?rn Engel" <joern@wohnheim.fh-wedel.de>
Subject: Re: MTD concat layer
Date: Wed, 13 Feb 2002 11:04:37 +0000	[thread overview]
Message-ID: <31104.1013598277@redhat.com> (raw)
In-Reply-To: <IGEFJKJNHJDCBKALBJLLOEGGFBAA.joakim.tjernlund@lumentis.se>

joakim.tjernlund@lumentis.se said:
>  I thougth this was already supported? Just create a mtd partition
> that will span two or more banks and mount a JFFS2 FS on top of that
> partition. 

Doesn't work if the banks aren't made to appear contiguous by the map 
driver. The probe code can't handle it. 

The case in question has something like:

 --------------
 |  CFI chip  |
 --------------
 |  BIOS chip |
 --------------
 |  CFI chip  |
 --------------

You could hack up a map driver that appears to have the two CFI chips 
contiguously, and then the probe code would find them both and make a 
single MTD device from them -  but there was a reason why he wasn't doing 
this. Perhaps the 'BIOS' bit is in fact the beginning of the second chip, 
not actually a separate chip at all? I don't remember.

--
dwmw2

  reply	other threads:[~2002-02-13 10:53 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-12 18:40 MTD concat layer Robert Kaiser
2002-02-13  7:56 ` Suspend Erase bug in cfi_cmdset0001.c Joakim Tjernlund
2002-02-14  8:17   ` Joakim Tjernlund
2002-02-13 11:00 ` MTD concat layer Joakim Tjernlund
2002-02-13 11:04   ` David Woodhouse [this message]
2002-02-13 11:34     ` Robert Kaiser
2002-02-13 11:37     ` Robert Schwebel
2002-02-13 13:33       ` Daniel Engström
2002-02-13 14:01         ` Eric W. Biederman
2002-02-15 15:58 ` David Woodhouse
2002-02-15 17:43   ` Robert Kaiser
2002-02-15 18:02     ` David Woodhouse
2002-02-15 18:40       ` Jörn Engel
2002-02-16 10:33         ` Robert Kaiser
2002-02-16 10:43       ` Robert Kaiser
2002-02-16 10:43         ` David Woodhouse
2002-02-16 11:03           ` Robert Kaiser
2002-02-16 11:08             ` David Woodhouse
2002-02-16 14:56             ` Brian J. Fox
2002-02-17 10:36               ` Robert Kaiser
2002-02-17 19:05                 ` Brian J. Fox
2002-02-18  8:48                   ` Robert Kaiser
2002-02-18  9:05                     ` David Woodhouse
2002-02-18 15:53                       ` Brian J. Fox
2002-02-18 17:01                         ` Robert Kaiser
2002-02-18 17:02                           ` David Woodhouse
2002-02-18 15:46                     ` Brian J. Fox
2002-02-20 14:28 ` Jonas Holmberg
2002-02-20 15:35   ` Robert Kaiser
2002-02-21 14:51     ` Jonas Holmberg
2002-02-26 11:32       ` Robert Kaiser
2002-03-06 13:37         ` Jonas Holmberg
2002-03-06 16:02           ` Robert Kaiser
  -- strict thread matches above, loose matches on Subject: below --
2002-02-14 11:14 Jonas Holmberg
2002-03-08 16:08 Robert Kaiser
2002-03-08 16:22 ` David Woodhouse

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=31104.1013598277@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=joakim.tjernlund@lumentis.se \
    --cc=joern@wohnheim.fh-wedel.de \
    --cc=linux-mtd@lists.infradead.org \
    --cc=rob@sysgo.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