All of lore.kernel.org
 help / color / mirror / Atom feed
From: daniel@arbor.com.tw (Daniel Toussaint)
To: linux-mtd@lists.infradead.org
Subject: Suggestions for using a DoC with Linux and a 2.4.20 kernel
Date: Tue, 11 Mar 2003 10:07:36 +0800	[thread overview]
Message-ID: <3E6D44E8.4040606@arbor.com.tw> (raw)
In-Reply-To: 1047340255.2207.10.camel@gobbles


Russ Dill wrote:

>On Mon, 2003-03-10 at 15:04, Gregg C Levine wrote:
>  
>
>>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. 
>>    
>>
>
>are you using the modules? or is it build into the kernel?
>
>modules:
>
>modprobe doc2000
>modprobe doc_probe (at this point it should identify the doc)
>
>then load whatever you need to talk to the doc, like mtdchar, mtdblock,
>nftl, etc
>
>If its built into the kernel, it should detect on boot.
>
>if you are using nftl, you should have access to it at /dev/nftla, and
>the partitions at /dev/nftla1, /dev/nftla2, etc. nftl is a transition
>layer that makes NAND flash look like a normal block device. It does
>wear leveling, bad sector handling, partial writes, etc so that things
>like ext2 and vfat can exist on the NAND flash.
>
>Most of the mtd utils will talk to it via the char device, /dev/mtd0,
>such as doc_loadbios (usually for installing grub), erase, nftl_format,
>etc
>
>If you are using jffs2 on NAND (I'm not sure about this one, because
>I've never tried it) you probably want /dev/mtdblock0.
>
About this using jffs2 on DiskOnChip, etc.
I've tried this a few times, but it doesn't seem to work, and I am 
assuming it can't (not without modifcations)(???)
Is there anyone who can make an authoritive statement on this?

Greetings,

>
>Additional info would probably be helpful, like what steps you are
>taking, and what messages you are getting.
>
>
>______________________________________________________
>Linux MTD discussion mailing list
>http://lists.infradead.org/mailman/listinfo/linux-mtd/
>  
>

  parent reply	other threads:[~2003-03-11  2:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-10 22:04 Suggestions for using a DoC with Linux and a 2.4.20 kernel Gregg C Levine
2003-03-10 23:50 ` 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   ` Daniel Toussaint [this message]
2003-03-11 10:02     ` Suggestions for using a DoC with Linux and a 2.4.20 kernel 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=3E6D44E8.4040606@arbor.com.tw \
    --to=daniel@arbor.com.tw \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.