From: "Ian" <Relativity@HumanHeuristic.com>
To: "Nicolas Pitre" <nico@cam.org>
Cc: mtd@infradead.org, linuxbios@lanl.gov
Subject: Re: Problems with r/w on mtdblock0
Date: Wed, 6 Dec 2000 13:07:36 +1000 [thread overview]
Message-ID: <200012060307.NAA20262@singularity.tronunltd.com> (raw)
> The above should be considered as a mtdblock bug IMHO.
As long as its not my own doofusness ... but I can't see how ...
> It shouldn't matter. The driver will actually write 8k if that's the erase
> size regardless of the size of your access.
Yeah ... that's what I reckon too ... but Ollie's part of (if not all of) the DoC
writing team ... so I try not to doubt it (the software's) ability :)
> > > you are playing with the IPL stuff, WRITE TO /dev/mtd0.
> Hmmm.... What's IPL?
Initial program loader ... there's a bunch of us @ linuxBIOS taking these things
and sticking them into the Motherboard's BIOS socket, then booting linux off of
it. Unfortunately, I'm the only guy *not* doing that at night .. because mines
broken :-(
> No it's not, unless you actually reboot before dd return to the shell
> prompt.
Yeah .. that's what I would've thought .. (after yesterday's thread).
> ... and that you shouldn't.
>
> I just don't have any hardware with DiskOnChip or NAND flash to test and fix
> the problem... therefore I'm not aware of the difference with NOR flash as
> far as the block interface is concerned.
>
> Any hints someone?
If you want me to try things and send you results, I'm cool with that. I'd *rather* be
writing to the block device (at least you should be able to "sync" it).
--
http://HumanHeuristic.com/
"Bringing people together in a world full of computers"
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next reply other threads:[~2000-12-06 3:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-06 3:07 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 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-05 0:42 Ian
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=200012060307.NAA20262@singularity.tronunltd.com \
--to=relativity@humanheuristic.com \
--cc=linuxbios@lanl.gov \
--cc=mtd@infradead.org \
--cc=nico@cam.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.