From: "George Williams" <george@itvd.sel.sony.com>
To: "Brian K. Michalk" <michalk@awpi.com>
Cc: mtd@infradead.org
Subject: Re: Beginner with DoC
Date: Tue, 14 Dec 1999 18:04:05 +0000 [thread overview]
Message-ID: <38568695.468F14FF@itvd.sel.sony.com> (raw)
In-Reply-To: 199912142231.QAA08264@sisko.awpi.com
Brian,
> So, what nodes am I supposed to make?
I ran MAKEDEV in the util directory (it creates a lot of nodes).
> insmod mtd -- cool
> insmod doc2000 -- cool
insmod nftl.o
Now you should be able to mount /dev/nftla1 provided it has a filesystem
on it.
You can run fdisk on /dev/nftla to create partitions, etc.
Look at /dev/mtd0 (I captured it with dd) and you can see the start of
the firmware bios extension (0x55aa).
> I get a compile error for the various utilities.
I also had trouble building the utils. It goes wrong with
../include/linux/mtd/mtd.h:6: parse error
My kernel sources are in /usr/src/linux and I think this is where the
Makefile expects them.
> Eventually I want to be able to boot off of the DoC, but for now,
> I'll settle for making the kernel modules work.
Same here. Now I'm doing what some others on this list have suggested
and using syslinux to boot the kernel with an initial ramdisk.
George
--
George Williams
Sony Electronics
3300 Zanker Road SJ-1A6
San Jose CA 95134
+1 408 955 4918
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~1999-12-15 1:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-14 22:31 Beginner with DoC Brian K. Michalk
1999-12-14 18:04 ` George Williams [this message]
1999-12-16 21:35 ` Dvir Oren
[not found] <199912162127.PAA21998@sisko.awpi.com>
1999-12-16 22:11 ` Brian K. Michalk
-- strict thread matches above, loose matches on Subject: below --
1999-12-17 15:57 Brian Michalk
1999-12-17 16:04 ` David Woodhouse
1999-12-17 16:48 Brian Michalk
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=38568695.468F14FF@itvd.sel.sony.com \
--to=george@itvd.sel.sony.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox