Suggestions for using a DoC with Linux and a 2.4.20 kernel

Suggestions for using a DoC with Linux and a 2.4.20 kernel

[Gregg C Levine]

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 )

Suggestions for using a DoC with Linux and a 2.4.20 kernel

[Russ Dill]

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.

Additional info would probably be helpful, like what steps you are
taking, and what messages you are getting.

Suggestions for using a DoC with Linux and a 2.4.20 kernel

[Gregg C Levine]

For my message please see at the bottom!
> -----Original Message-----
> From: linux-mtd-admin at lists.infradead.org [mailto:linux-mtd-
> admin at lists.infradead.org] On Behalf Of Russ Dill
> Sent: Monday, March 10, 2003 6:51 PM
> To: Gregg C Levine
> Cc: linux-mtd at lists.infradead.org
> Subject: Re: Suggestions for using a DoC with Linux and a 2.4.20
kernel
>=20
> 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.
>=20
> are you using the modules? or is it build into the kernel?
>=20
> modules:
>=20
> modprobe doc2000
> modprobe doc_probe (at this point it should identify the doc)
>=20
> then load whatever you need to talk to the doc, like mtdchar,
mtdblock,
> nftl, etc
>=20
> If its built into the kernel, it should detect on boot.
>=20
> 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.
>=20
> 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
>=20
> 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.
>=20
> Additional info would probably be helpful, like what steps you are
> taking, and what messages you are getting.
>=20
>=20
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/

Hello again from Gregg C Levine
Right now I am doing a recompile of my kernel, after patching it,
using the patches found in that directory of today's snapshot.
=20
So far, I am working my way through. Only the DoC ones were built as
modules.
More, as I work my way through. This is a new aspect of working with
Linux, so I am quite literally groping in the dark here.
Ladies and Gentlemen: Because I suspect there are others out there,
who have gone through this, I would greatly appreciate a response from
everyone else who has had these problems happen to them before.
-------------------
Gregg C Levine hansolofalcon at worldnet.att.net
------------------------------------------------------------
"The Force will be with you...Always." Obi-Wan Kenobi
"Use the Force, Luke."  Obi-Wan Kenobi
(This company dedicates this E-Mail to General Obi-Wan Kenobi )
(This company dedicates this E-Mail to Master Yoda )

Suggestions for using a DoC with Linux and a 2.4.20 kern

[Russ Dill]

> Hello again from Gregg C Levine
> Right now I am doing a recompile of my kernel, after patching it,
> using the patches found in that directory of today's snapshot.

you don't neccessarily need todays snapshot, stock kernel is probably
good enough, unless maybe you want to play with things like JFFS2 on
NAND flash.

> So far, I am working my way through. Only the DoC ones were built as
> modules.

then you must load them in the order of doc2000, doc_probe, nftl

> More, as I work my way through. This is a new aspect of working with
> Linux, so I am quite literally groping in the dark here.
> Ladies and Gentlemen: Because I suspect there are others out there,
> who have gone through this, I would greatly appreciate a response from
> everyone else who has had these problems happen to them before.

could you be more specific when you talk about "this" and "these
problems". BTW, if they are common problem you are having, its likely
they are in the mailing list archives.

Suggestions for using a DoC with Linux and a 2.4.20 kernel

[Daniel Toussaint]

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/
>  
>

Suggestions for using a DoC with Linux and a 2.4.20 kernel

[Charles Manning]

As a matter of interest, has anyone tried YAFFS on DOC?

I seem to recall Thomas Gleixner saying it should work (or is very close).

-- CHarles