public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Jason Walker" <jasonw@uswo.net>
To: "MTD Mailing List" <mtd@infradead.org>
Subject: MTD and 2.4
Date: Mon, 30 Apr 2001 11:22:15 -0400	[thread overview]
Message-ID: <NEBBIDMHCLDPHDHEGDMLGEFCCBAA.jasonw@uswo.net> (raw)

Greeting all

	I have a rather interesting situation.  I have a box with a DickOnChip on
it, and someone else built a 2.2.x kernel for it.  I need to get a 2.4.x
kernel on it.  I did not build the 2.2.x kernel that is on it now, so I
don't know how it's done.  I *suspect* they used the kernel patxches from
M-systems, but I am not positive.  I have tried their patches for 2.4 but
they are incredibly outdated and don't compile (they were meant for
2.4.0pre8)  On the 2.2.x kernel the devices come up as /dev/fla.  I don't
need to maintain backwards compatibility with the 2.2.x formats, so if I
need to use another one that is cool.  I read all the documentation on the
website and the kernel *still* won't work.  This is a DiskOnChip Millenium
chip, btw.  If I need to post error messages or my kernel config, that is
fine.. Any help would be appreciated. thank!

Jason Walker

US Wireless Online



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

             reply	other threads:[~2001-04-30 15:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-30 15:22 Jason Walker [this message]
2001-04-30 16:03 ` MTD and 2.4 David Woodhouse
2001-05-04 19:54   ` Jason Walker
2001-05-04 21:27     ` David Woodhouse
2001-05-04 23:46       ` Jason Walker
2001-05-05  0:23         ` David Woodhouse
2001-05-05  0:54           ` Jason Walker
2001-05-05 11:13             ` David Woodhouse
2001-05-06 18:57               ` Invalid ioctl Edmund Troche
2001-05-06 19:22                 ` Edmund Troche
2001-05-02  7:14 ` MTD and 2.4 Michel STEMPIN

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=NEBBIDMHCLDPHDHEGDMLGEFCCBAA.jasonw@uswo.net \
    --to=jasonw@uswo.net \
    --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