From: "Brian J. Murrell" <ae211dd25992457126b87e47964e2ed8@interlinx.bc.ca>
To: linux-mtd@lists.infradead.org
Subject: Re: MTD Config.in items not escaped by bus availability
Date: Sun, 3 Nov 2002 06:59:41 -0500 [thread overview]
Message-ID: <20021103115941.GJ16306@pc.ilinx> (raw)
In-Reply-To: <20021031183718.GA31035@wohnheim.fh-wedel.de>
[-- Attachment #1: Type: text/plain, Size: 1034 bytes --]
On Thu, Oct 31, 2002 at 07:37:18PM +0100, Jörn Engel wrote:
>
> All right. This patch will only create the mtd devices from ram and
> block devices, unless $CONFIG_MEMORY_BUS is defined.
> Brian, can you define this option for all platforms other tham uml?
>
> Also, this might still be a little too broad for nand flash. Nand
> needs more than just a memory bus, but I don't know what exactly.
> But this should be close enough for now.
OK. I have taken your patch and added the bits to define
CONFIG_MEMORY_BUS on existing hardware architectures in the 2.4.19
tree and sent the patch to Marcelo. Let's see what happens.
I don't know what Marcelo's normal mode of operations is, whether he
responds to patch sumbitters with a confirmation of the patch being
applied or not (I still have not gotten response from a patch I sent a
few weeks ago doing pretty much this same thing for PC Appletalk
cards), but I guess we can just wait and see what's in 2.4.20 when
it's released.
b.
--
Brian J. Murrell
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2002-11-03 11:29 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-30 16:22 MTD Config.in items not escaped by bus availability Hicks, Jamey
2002-10-30 17:30 ` Brian J. Murrell
[not found] ` <20021030185507.GA31547@wohnheim.fh-wedel.de>
2002-10-30 19:38 ` Brian J. Murrell
[not found] ` <20021030201608.GA28523@wohnheim.fh-wedel.de>
2002-10-30 20:49 ` Brian J. Murrell
[not found] ` <20021030214341.GC25383@wohnheim.fh-wedel.de>
2002-10-30 22:46 ` Brian J. Murrell
2002-10-31 16:53 ` Jörn Engel
2002-10-31 18:37 ` Jörn Engel
2002-10-31 19:05 ` Brian J. Murrell
2002-10-31 21:00 ` Jörn Engel
2002-11-03 11:59 ` Brian J. Murrell [this message]
2002-11-04 14:17 ` Jörn Engel
2002-11-04 14:29 ` Brian J. Murrell
2002-11-04 17:13 ` Jörn Engel
2002-11-06 20:45 ` Brian J. Murrell
2002-11-07 8:00 ` David Woodhouse
2002-11-07 13:50 ` Brian J. Murrell
2002-11-07 14:00 ` David Woodhouse
2002-11-07 15:33 ` Jörn Engel
2002-11-07 15:34 ` David Woodhouse
2002-11-07 15:54 ` Jörn Engel
2002-11-07 15:58 ` David Woodhouse
2002-11-07 16:00 ` Jörn Engel
2002-11-07 15:21 ` Jörn Engel
2002-11-07 12:13 ` Unable to handle kernel NULL pointer dereference at virtual address 0000000c nur
-- strict thread matches above, loose matches on Subject: below --
2002-10-30 22:09 MTD Config.in items not escaped by bus availability Hicks, Jamey
2002-10-28 13:48 Brian J. Murrell
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=20021103115941.GJ16306@pc.ilinx \
--to=ae211dd25992457126b87e47964e2ed8@interlinx.bc.ca \
--cc=linux-mtd@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.