public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Ian" <Relativity@HumanHeuristic.com>
To: mtd@infradead.org
Subject: Re: Problems with r/w on mtdblock0
Date: Tue, 5 Dec 2000 10:42:34 +1000	[thread overview]
Message-ID: <200012050042.KAA16622@singularity.tronunltd.com> (raw)




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@humanheuristic.com>
>To: <mtd@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@infradead.org
> 

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



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

             reply	other threads:[~2000-12-05  0:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-05  0:42 Ian [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-12-06  4:33 Problems with r/w on mtdblock0 Ian
2000-12-06  3:07 Ian
2000-12-06  2:45 Ian
2000-12-06  2:28 Ian
2000-12-06  2:52 ` Nicolas Pitre
2000-12-06  0:19 Ian
2000-12-06  0:41 ` Ollie Lho
2000-12-06  2:18   ` Nicolas Pitre
2000-12-05  1:54 Ian
2000-12-05  9:15 ` David Woodhouse
2000-12-05 14:50 ` Ronald G Minnich
2000-12-05 14:54   ` David Woodhouse
2000-12-05 15:34     ` Nicolas Pitre
2000-12-05 15:36       ` David Woodhouse
2000-12-05 19:38         ` Ronald G Minnich
2000-12-04 22:36 Ian
2000-12-05  1:10 ` Ollie Lho

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=200012050042.KAA16622@singularity.tronunltd.com \
    --to=relativity@humanheuristic.com \
    --cc=mtd@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