public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: hansolofalcon@worldnet.att.net (Gregg C Levine)
To: linux-mtd@lists.infradead.org
Subject: Suggestions for using a DoC with Linux and a 2.4.20 kernel
Date: Mon, 10 Mar 2003 17:04:55 -0500	[thread overview]
Message-ID: <000001c2e751$1606b220$19c3580c@who5> (raw)

Hello from Gregg C Levine
I have a statement to make, then the question
Okay here's the statement:
I have a system running that was freshly installed, and I have a
kernel being built from fresh source code. This is an unpatched 2.4.20
kernel.

Now the question:
How do I go about setting things up, so that the kernel can see the
DoC on startup, and then work with it? I have turned on the MTD
settings in the kernel, and for the DoC driver as well.
I can supply further information, including name of distribution, and
even supplier of DoC, as well, if needed.=20
-------------------
Gregg C Levine hansolofalcon at worldnet.att.net
------------------------------------------------------------
"The Force will be with you...Always." Obi-Wan Kenobi
"Use the Force, Luke."=A0 Obi-Wan Kenobi
(This company dedicates this E-Mail to General Obi-Wan Kenobi )
(This company dedicates this E-Mail to Master Yoda )

             reply	other threads:[~2003-03-10 22:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-10 22:04 Gregg C Levine [this message]
2003-03-10 23:50 ` Suggestions for using a DoC with Linux and a 2.4.20 kernel Russ Dill
2003-03-11  1:27   ` Gregg C Levine
2003-03-11  1:42     ` Suggestions for using a DoC with Linux and a 2.4.20 kern Russ Dill
2003-03-11  2:07   ` Suggestions for using a DoC with Linux and a 2.4.20 kernel Daniel Toussaint
2003-03-11 10:02     ` Charles Manning

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='000001c2e751$1606b220$19c3580c@who5' \
    --to=hansolofalcon@worldnet.att.net \
    --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