Re: 64M DOC2000

Re: 64M DOC2000

[David Woodhouse]

ithompson@coollogic.com said:
> I've just tried a 64M Doc2000 with kernel 2.2.16 and the IGEL driver,
> and it is not recognised. I have no problems with 16M and 32M parts.
> Can someone on the list confirm that this is the case? 

No clue. Try it with the free driver and see what happens.

--
dwmw2




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

64M DOC2000

[Ian Thompson]

I've just tried a 64M Doc2000 with kernel 2.2.16 and the IGEL driver, 
and it is not recognised. I have no problems with 16M and 32M parts. 
Can someone on the list confirm that this is the case? 

Ian T.


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

Re: 64M DOC2000

[David Woodhouse]

ithompson@coollogic.com said:
> The part is recognised by the mtd driver with 2.4.0. I can partition
> it with fdisk /dev/nftl and create  ext2 disks.  

Good.

> However, when I try
> to copy data to it I start getting input/output errors after I've got
> a certain amount of data (yet to be determined) on it. 

Urgh. That may be normal though :(

Can you post the whole of the kernel's output while you're doing this, 
including what it says when it probes and finds the device?

--
dwmw2




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

Re: 64M DOC2000

[Ian Thompson]

The part is recognised by the mtd driver with 2.4.0.
I can partition it with fdisk /dev/nftl and create 
ext2 disks. 
However, when I try to copy data to it I start getting input/output
errors after I've got a certain amount of data (yet to be determined)
on it.

Ian T.

David Woodhouse wrote:
> 
> ithompson@coollogic.com said:
> > I've just tried a 64M Doc2000 with kernel 2.2.16 and the IGEL driver,
> > and it is not recognised. I have no problems with 16M and 32M parts.
> > Can someone on the list confirm that this is the case?
> 
> No clue. Try it with the free driver and see what happens.
> 
> --
> dwmw2


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

RE: 64M DOC2000

[Oron Ogdan]

A small issue I think you guys should know about. From 15/7/2000 we are
using Samsung parts as well as Toshiba parts. I am pasting the list of parts
that could be used on the DOC2000. 

Samsung (Manufacture ID = 0xEC )
=================================
(0x64) :             /* 2 Mb */
(0xEA) :

(0xE3) :             /* 4 Mb */
(0xE5) :

(0xE6) :             /* 8 Mb */

(0x73) :             /* 16 Mb  */

(0x75) :             /* 32 Mb */

(0x76) :             /* 64 Mb */

Toshiba (Manufacture ID 0x98) 
=================================
(0x64) :             /* 2 Mb */
(0xEA) :

(0x6B) :             /* 4 Mb */
(0xE5) :

(0xE6) :             /* 8 Mb */

(0x73) :             /* 16 Mb */

(0x75) :             /* 32 Mb */

(0x76) :             /* 64 Mb */

Regards

Oron

> -----Original Message-----
> From: David Woodhouse [mailto:dwmw2@infradead.org]
> Sent: Tuesday, July 25, 2000 3:32 PM
> To: Ian Thompson
> Cc: mtd@infradead.org
> Subject: Re: 64M DOC2000 
> 
> 
> 
> ithompson@coollogic.com said:
> > I've just tried a 64M Doc2000 with kernel 2.2.16 and the 
> IGEL driver,
> > and it is not recognised. I have no problems with 16M and 32M parts.
> > Can someone on the list confirm that this is the case? 
> 
> No clue. Try it with the free driver and see what happens.
> 
> --
> dwmw2
> 
> 
> 
> 
> To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
> 


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

Re: 64M DOC2000

[David Woodhouse]

Orono@m-sys.com said:
> A small issue I think you guys should know about. From 15/7/2000 we
> are using Samsung parts as well as Toshiba parts. I am pasting the
> list of parts that could be used on the DOC2000.  

Thanks for the update. I've just committed the appropriate fix, albeit 
without the actual device names.



--
dwmw2




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

Re: 64M DOC2000

[Ian Thompson]

Actually I had to play with the code to get it to recognise the device.
This 
is probably due to my test setup.

I boot from a hard drive and set the DOC up from within Linux. This
means contending
with the LILO/DOC interaction so I use DOC2.FFF to blank out the
conflicting region.
The detection code misses the device when using this, because it reads
FFs instead of the
55 and AA signature. I took out that detection and restricted
doc_locations[] to 
the actual location of the DOC and the device is found. 

Kernel output to follow.

Ian T.


David Woodhouse wrote:
> 
> ithompson@coollogic.com said:
> > The part is recognised by the mtd driver with 2.4.0. I can partition
> > it with fdisk /dev/nftl and create  ext2 disks.
> 
> Good.
> 
> > However, when I try
> > to copy data to it I start getting input/output errors after I've got
> > a certain amount of data (yet to be determined) on it.
> 
> Urgh. That may be normal though :(
> 
> Can you post the whole of the kernel's output while you're doing this,
> including what it says when it probes and finds the device?
> 
> --
> dwmw2


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