public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Brian J. Murrell" <4b07d544b5c5062e647d85db08f8d05c@interlinx.bc.ca>
To: linux-mtd@lists.infradead.org
Subject: Re: MTD Config.in items not escaped by bus availability
Date: Thu, 31 Oct 2002 14:05:19 -0500	[thread overview]
Message-ID: <20021031190518.GL27880@pc.ilinx> (raw)
In-Reply-To: <20021031183718.GA31035@wohnheim.fh-wedel.de>

[-- Attachment #1: Type: text/plain, Size: 750 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.

Cool.  Is the memory bus the only bus that MTD devices can be attached
to?  They can't be attached to USB or PCMCIA or anything else?  Or
perhaps the only ones supported by Linux right now are ones attached
to a memory bus?

> Brian, can you define this option for all platforms other tham uml?

I will take a look.

> 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.

Thanx!

b.

-- 
Brian J. Murrell

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2002-10-31 18:35 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 [this message]
2002-10-31 21:00                   ` Jörn Engel
2002-11-03 11:59                 ` Brian J. Murrell
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=20021031190518.GL27880@pc.ilinx \
    --to=4b07d544b5c5062e647d85db08f8d05c@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox