From: Raphael Hertzog <eng@eipm.ch>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Henrik Nordstrom <hno@marasystems.com>, linux-mtd@lists.infradead.org
Subject: Re: NFTL not recognizing disk on chip in some cases
Date: 30 Jan 2003 09:05:22 +0100 [thread overview]
Message-ID: <1043913922.556.4.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.44.0301292238560.4791-100000@imladris.demon.co.uk>
Am Mit, 2003-01-29 um 23.41 schrieb David Woodhouse:
> Does one of your files have 'ANAND' at the start of it (or at an offset of
> n*512 bytes withing the file? :)
Yes.
$ find . -type f | xargs grep -l ANAND
./root/lib/modules/2.4.19-eipm/kernel/drivers/block/doc.o
./root/lib/modules/2.4.19-eipm/kernel/drivers/block/doc/doc.o
./root/usr/lib/grub/i386-pc/stage2
./root/usr/lib/grub/i386-pc/grub_firmware
After inspection, grub_firmware does have 'ANAND' at offset 87040 (170 *
512).
> That may get seen as an 'extra' NFTL media header sector; we should do
> more sanity checks and refrain from looking inside an already-detected
> NFTL partition.
I'm happy to test any patch since I can reproduce the problem here very
regularly ... :-)
> Because in the first case the 'ANAND' went somewhere other than the first
> page of an erase block, so wasn't seen as an 'extra' media header? Taking
> raw dumps of the flash would confirm this.
I'll do that to check it.
Cheers,
--
Raphaël Hertzog - EIPM SA
next prev parent reply other threads:[~2003-01-30 7:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-29 12:47 NFTL not recognizing disk on chip in some cases Raphael Hertzog
2003-01-29 14:48 ` Henrik Nordstrom
2003-01-29 16:42 ` Raphael Hertzog
2003-01-29 17:05 ` Henrik Nordstrom
2003-01-29 18:30 ` Mark Meade
2003-01-29 22:41 ` David Woodhouse
2003-01-30 8:05 ` Raphael Hertzog [this message]
2003-01-30 8:19 ` David Woodhouse
2003-01-30 10:56 ` Raphael Hertzog
2003-01-30 10:14 ` Raphael Hertzog
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=1043913922.556.4.camel@localhost \
--to=eng@eipm.ch \
--cc=dwmw2@infradead.org \
--cc=hno@marasystems.com \
--cc=linux-mtd@lists.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