From: Ollie Lho <ollie@sis.com.tw>
To: Ian <Relativity@HumanHeuristic.com>
Cc: mtd@infradead.org
Subject: Re: Problems with r/w on mtdblock0
Date: Tue, 05 Dec 2000 09:10:11 +0800 [thread overview]
Message-ID: <3A2C4073.8AA079B3@sis.com.tw> (raw)
In-Reply-To: 200012042236.IAA16219@singularity.tronunltd.com
Ian wrote:
>
> 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.
>
Ian,
The /dev/mtdblockN device the the "block device" node for MTD devices.
In the DoC case, it can only read/write data in 8KB block (the erase size).
You can not read/write 512B on itm it will get "cached" by the driver. If
you are playing with the IPL stuff, WRITE TO /dev/mtd0.
Ollie
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~2000-12-05 1:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-04 22:36 Problems with r/w on mtdblock0 Ian
2000-12-05 1:10 ` Ollie Lho [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-12-05 0:42 Ian
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-06 0:19 Ian
2000-12-06 0:41 ` Ollie Lho
2000-12-06 2:18 ` Nicolas Pitre
2000-12-06 2:28 Ian
2000-12-06 2:52 ` Nicolas Pitre
2000-12-06 2:45 Ian
2000-12-06 3:07 Ian
2000-12-06 4:33 Ian
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=3A2C4073.8AA079B3@sis.com.tw \
--to=ollie@sis.com.tw \
--cc=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