From: David Woodhouse <dwmw2@infradead.org>
To: Gregory Schallert <gschallert@dawning.com>
Cc: "mtd@infradead.org" <mtd@infradead.org>
Subject: Re: mtdblock module & I'm Back again
Date: Thu, 02 Nov 2000 10:09:52 +0000 [thread overview]
Message-ID: <3593.973159792@redhat.com> (raw)
In-Reply-To: <3A005A52.E95F536@dawning.com>
gschallert@dawning.com said:
> 2) What does mtdblock.c actually do? If I load mtd.o, mapped.o, and
> mtdblock.o what additional functionality do I need to program to get
> a minix file system on the flash chips?
You don't need 'mapped.o' which is going to go away fairly shortly.
You need to ensure that 'jedec.c' both works and supports the interleaved
arrangement of your flash chips.
Then you need to provide a 'map' driver through which it can access the
chips. If the flash chips are linearly mapped into your physical address
space, then physmem.c is a good place to start.
--
dwmw2
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
prev parent reply other threads:[~2000-11-02 10:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-01 18:00 mtdblock module & I'm Back again Gregory Schallert
2000-11-01 19:37 ` Nicolas Pitre
2000-11-01 22:43 ` David Woodhouse
2000-11-01 22:52 ` Nicolas Pitre
2000-11-02 7:51 ` David Woodhouse
2001-01-18 23:27 ` mtdblock: module -vs- kernel Gregory Schallert
2001-01-19 1:19 ` Nicolas Pitre
2001-01-24 15:42 ` compiling DOC Brian Michalk
2001-01-24 16:07 ` David Woodhouse
2001-01-25 16:48 ` fdisk problems Brian Michalk
2001-01-25 18:33 ` David Woodhouse
2001-01-25 18:56 ` Brian Michalk
2001-01-25 20:31 ` Brian Michalk
2001-01-25 20:56 ` David Woodhouse
2001-01-25 21:19 ` Brian Michalk
2001-01-26 17:41 ` Brian Michalk
2001-01-28 13:19 ` David Woodhouse
2001-01-28 15:52 ` Brian Michalk
2000-11-02 10:09 ` David Woodhouse [this message]
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=3593.973159792@redhat.com \
--to=dwmw2@infradead.org \
--cc=gschallert@dawning.com \
--cc=mtd@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