From: David Woodhouse <dwmw2@infradead.org>
To: tglx@linutronix.de
Cc: linux-mtd@lists.infradead.org, skorinkod@mail.ru
Subject: Re: Problems with DiskOnChip 2000
Date: Sat, 02 Oct 2004 22:12:36 +0100 [thread overview]
Message-ID: <1096751556.18638.16.camel@localhost.localdomain> (raw)
In-Reply-To: <1096751135.21297.73.camel@thomas>
On Sat, 2004-10-02 at 23:05 +0200, Thomas Gleixner wrote:
> > Possible DiskOnChip with unknown ChipID 36 found at 0xe8000
> > Possible DiskOnChip with unknown ChipID C6 found at 0xea000
> > Possible DiskOnChip with unknown ChipID F6 found at 0xec000
> > Possible DiskOnChip with unknown ChipID C1 found at 0xee000
>
> None of those ID's is a valid chip ID except the 0x36, which is a
> 64MiB,1.8V chip. I doubt, that there are DoC's available with 1.8V
> supply. The stuff looks more like random nonsense.
That's DiskOnChip ChipID, not NAND chip ID. But yes, it looks like
random crap from other addresses, probably BIOS or extension ROMs.
--
dwmw2
next prev parent reply other threads:[~2004-10-02 21:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-01 14:58 Problems with DiskOnChip 2000 Dmitry
2004-10-02 21:05 ` Thomas Gleixner
2004-10-02 21:12 ` David Woodhouse [this message]
2004-10-02 21:20 ` Thomas Gleixner
2004-10-04 17:26 ` Dmitry Skorinko
2004-10-04 17:56 ` Thomas Gleixner
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=1096751556.18638.16.camel@localhost.localdomain \
--to=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=skorinkod@mail.ru \
--cc=tglx@linutronix.de \
/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