public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: John Burch <jburch@vincisystems.com>
Cc: 'Kenneth Johansson' <kenneth.johansson@etx.ericsson.se>
Cc: 'Mtd' <linux-mtd@lists.infradead.org>
Cc: tglx@linutronix.de
Cc: 'David Woodhouse' <dwmw2@infradead.org>
Subject: Re: Can mtd partition span multiple devices
Date: Thu, 3 Apr 2003 17:49:25 +0200	[thread overview]
Message-ID: <20030403154925.GC5651@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <003501c2f9f6$dc7373a0$1200a8c0@JOHNB>

On Thu, 3 April 2003 10:36:54 -0500, John Burch wrote:
> 
> I'm using 2.4.17 and I don't think mtdconcat is part of that kernel
> (though I may not need it anyway based on dwmw2's response).  Are the
> changes since then substantial, and can 2.4.17 be patched to support the
> latest mtd/jffs2 code?

I wouldn't patch the mtd/jffs2 part, unless I had to. The better
strategy is to update the whole kernel, but that is always a bit
tricky inside some companies.

> Second, you imply that a single chip probe will handle multiple devices
> (assuming contiguous addressing?).  Is this supported in 2.4.17 and is
> it a common approach to use for multiple devices?

That support has been in the official kernel since 2.4.2 or even
longer.

Jörn

-- 
Measure. Don't tune for speed until you've measured, and even then
don't unless one part of the code overwhelms the rest.
-- Rob Pike

  reply	other threads:[~2003-04-03 15:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-02 22:56 Can mtd partition span multiple devices John Burch
2003-04-03  0:58 ` Thomas Gleixner
2003-04-03 11:15   ` Kenneth Johansson
2003-04-03 11:25     ` David Woodhouse
2003-04-03 15:36       ` John Burch
2003-04-03 15:49         ` Jörn Engel [this message]
2003-04-03  4:26 ` Charles Manning

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=20030403154925.GC5651@wohnheim.fh-wedel.de \
    --to=joern@wohnheim.fh-wedel.de \
    --cc=jburch@vincisystems.com \
    --cc=kenneth.johansson@etx.ericsson.se \
    /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