public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Brian K. Michalk" <michalk@sisko.awpi.com>
To: mtd@infradead.org
Subject: Beginner with DoC
Date: Tue, 14 Dec 1999 16:31:58 -0600 (CST)	[thread overview]
Message-ID: <199912142231.QAA08264@sisko.awpi.com> (raw)

My system:
Advantech biscuit PC
DoC2000, 72 megabyte
Linux (slackware) 2.2.6

Eventually I want to be able to boot off of the DoC, but for now, 
I'll settle for making the kernel modules work.  I read the 
documentation I could find, but still had problems.  Here's
what I did:

Downloaded mtd-19991025.tar.gz, extracted, compiled.
	I get a compile error for the various utilities.
Download mtd-19991025.diff, patch and compile -- no help,
	so I comment out the offending utilities.
insmod mtd -- cool
insmod doc2000 -- cool
Okay, now I want to see if I can see them with fdisk, but I've
	got only a few clues as to the nodes.  I tried
	mknod fla b 62 0 through fla4 for major IDs 62, 90, 31, 93,
	and 44.  Fdisk never finds any of the devices.

So, what nodes am I supposed to make?

Thanks for the help.

-- 
Brian Michalk  <http://www.awpi.com/michalk>
Life is what you make of it ... never wish you had done something.
Aviator, experimental aircraft builder, motorcyclist, SCUBA diver
musician, home-brewer, entrepreneur and SINGLE!


To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

             reply	other threads:[~1999-12-14 22:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-14 22:31 Brian K. Michalk [this message]
1999-12-14 18:04 ` Beginner with DoC George Williams
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=199912142231.QAA08264@sisko.awpi.com \
    --to=michalk@sisko.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