public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Brendan J Simon <BrendanSimon@fastmail.fm>
To: linux-mtd <linux-mtd@lists.infradead.org>
Subject: 128MB DOC2000 with 2.4.X kernel
Date: Thu, 05 Aug 2004 13:51:02 +1000	[thread overview]
Message-ID: <4111AEA6.2080605@fastmail.fm> (raw)

I've just been reading the archives about 128MB DOCs looking like a 
Millenium device and the soltion being to do 4 reads, etc.
The 2.4.26 kernel doesn't support this device but I see that the 2.6.X 
kernels do.

If I modify docprobe.c to detect the 128MB DOC2000 correctly, will the 
rest of the MTD code work correctly with it ???
I hope so as this would be a quick fix, however I do recall seeing 
something about 3 and 4 byte addresses.  Is this relevant to getting 
128MB DOC working with 2.4.X kernels ?

To summarise, I have an embedded board with a 64MB DOC2000 and a 2.4.18 
kernel.  I need to have a 128MB DOC2000 working on it pretty quickly and 
am considering the options of making a few source code changes to the 
2.4.18 kernel or porting a newer 2.6.x kernel to the embedded board.  
I'm looking for the quickest solution.  Any ideas, comments or 
suggestions would be greatly appreciated.

Is INTFL needed for the 128MB DOC2000 or can I use the NFTL code that I 
am currently using on the 64MB doc?

Many thanks,
Brendan Simon.

             reply	other threads:[~2004-08-05  3:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-05  3:51 Brendan J Simon [this message]
2004-08-05 12:55 ` 128MB DOC2000 with 2.4.X kernel Dan Brown
2004-08-11  1:11   ` Brendan Simon
2004-08-11 12:49     ` Dan Brown
2004-08-12  5:27       ` Brendan Simon
2004-09-09  3:16         ` 96MB/128MB " Brendan Simon
2004-09-09 22:44           ` Kurt A. Freiberger

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=4111AEA6.2080605@fastmail.fm \
    --to=brendansimon@fastmail.fm \
    --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