From: David Woodhouse <dwmw2@infradead.org>
To: " Brian Michalk" <michalk@awpi.com>
Cc: mtd@infradead.org
Subject: Re: compiling DOC
Date: Wed, 24 Jan 2001 16:07:35 +0000 [thread overview]
Message-ID: <19215.980352455@redhat.com> (raw)
In-Reply-To: <NEBBLKIBMLGPAFMHEJICMEKNCEAA.michalk@awpi.com>
michalk@awpi.com said:
> I tried with 2.4 kernels as well. I know you guys are busy, but I
> would like a little cookbook help to be able to compile a kernel, and
> then boot off DOC.
Get stock 2.4.0 kernel.
Do this:
CONFIG_MTD=y
CONFIG_MTD_DOC2000=y
CONFIG_MTD_DOCPROBE_ADDRESS=0 ( autoprobe)
CONFIG_MTD_DOCPROBE_HIGH=n
CONFIG_MTD_DOCPROBE_55AA=y
CONFIG_NFTL=y
CONFIG_NFTL_RW=y
boot with root=/dev/nftla1 (or /dev/nftla2)
If you have to use 2.2, there are patches at
ftp://ftp.linux-mtd.infradead.org/pub/mtd/patches/
If you apply these, you can then get the latest code from CVS (Don't use
the ancient tarballs) and drop in the contents of the include/linux/mtd and
drivers/mtd directories.
--
dwmw2
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~2001-01-24 16:08 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 [this message]
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 ` mtdblock module & I'm Back again 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=19215.980352455@redhat.com \
--to=dwmw2@infradead.org \
--cc=michalk@awpi.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 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.