Problems with r/w on mtdblock0

[Ian]

I am a scumbag.  I have just re-run it up as modules and redone my test, and the data *is* 
sticking .. and *is* surviving reboots.  I have no idea how it failed my previous test 
(considering I'm using the same test scripts and configs).


I apologise profusely for this tripe .. and will retest my "inbuilt" scenario aswell ...  


<whipping back with rosaries>
 I will not post to public mailling lists after 18hours of programming ..
 I will not post to public mailling lists after 18hours of programming ..
 I will not post to public mailling lists after 18hours of programming ..
  <etc ad nauseum>


If the inbuilt stuff isn't problematic, then I'll go back to Hamish's suggestions ..

'night.


  ----- Original Message -----
>From: "Ian" <Relativity at humanheuristic.com>
>To: <mtd at infradead.org>
>Subject:  Re: Problems with r/w on mtdblock0
>Date: Tue, 05 Dec 2000 10:42:34 +1000
>
> 
> 
> 
> I can also confirm that this problem exists when compiled as modules (and also with
> the #define DOC_SINGLE_DRIVER commented out).
> 
> 
> It isn't recent.  Before this mornings attempts I was using a CVS from about 4-5days 
> ago and it was in that bundle that I noticed it (I'm pretty sure it was pre the combo
> mods that Ollie did)
> 
> 
> 
>   ----- Original Message -----
> >From: "Ian" <Relativity at humanheuristic.com>
> >To: <mtd at infradead.org>
> >Subject:  Problems with r/w on mtdblock0
> >Date: Tue, 05 Dec 2000 08:36:59 +1000
> >
> > 
> > 
> >   Have I done something wrong to get this error?
> > 
> >     bash# dd if=/dev/zero of=/dev/mtdblock0 bs=512 count=1
> >     end_request: I/O error, dev 1f:00 (mtdblock), sector 0
> >     dd: /dev/mtdblock0: Input/output error
> >     1+0 records in
> >     0+0 records out
> > 
> >     bash# /bin/dd if=/dev/mtdblock0 of=/dev/null bs=512 count=1
> >     end_request: I/O error, dev 1f:00 (mtdblock), sector 0
> >     /bin/dd: /dev/mtdblock0: Input/output error
> >     0+0 records in
> >     0+0 records out
> > 
> > 
> >   I have no problems reading and writing to nftla on my DoC Millennium ... just
> > not the block device.
> > 
> >   NB: I'm trying to use the block device, because dd'ing to the first and second
> > 512bytes of the character device, while appearing successful,  does not "stick".
> > A hexdump immediately after a dd shows no sign of the dd data.
> > 
> >   Note, too, that dd'ing to a non existent DoC yields a different error;
> >     bash# /bin/dd if=/dev/mtdblock1 of=/dev/null bs=512 count=1
> >     /bin/dd: /dev/mtdblock1: No such device
> > 
> >     brw-r--r--   1 root     root      31,   0 Dec  4 20:14 /dev/mtdblock0
> >     brw-r--r--   1 root     root      31,   1 Dec  4 20:14 /dev/mtdblock1
> > 
> > 
> > Erm;
> >     bash# cat  /proc/mtd
> >     mtd0: 00800000 "DiskOnChip Millennium"
> > 
> > is that supposed to be the memory location for the DoC ?
> > 
> > 
> > Boot process  (My DoC drivers are compiled internally to the kernel, *not* as modules)
> >     Initializing MTD Layer
> >     M-Systems DiskOnChip driver. (C) 1999 Machine Vision Holdings, Inc.
> >     DiskOnChip Millennium found at address 0xDC000
> >     Flash chip found: Manufacture ID: 98, Chip ID: E6 (Toshiba TC58V64AFT/DC)
> >     1 flash chips found. Total DiskOnChip size: 8 Mbytes
> > 
> > 
> > 
> > 
> > --
> > http://HumanHeuristic.com/
> > "Bringing people together in a world full of computers"
> > 
> > 
> > 
> > To unsubscribe, send "unsubscribe mtd" to majordomo at infradead.org
> > 
> 
> --
> http://HumanHeuristic.com/
> "Bringing people together in a world full of computers"
> 
> 
> 
> To unsubscribe, send "unsubscribe mtd" to majordomo at infradead.org
> 

--
http://HumanHeuristic.com/
"Bringing people together in a world full of computers"



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