From: David Woodhouse <dwmw2@infradead.org>
To: "Sleepy" <sleepygod@sina.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: MTD 16M Flash module detection error?
Date: Fri, 14 Jun 2002 08:35:46 +0100 [thread overview]
Message-ID: <17698.1024040146@redhat.com> (raw)
In-Reply-To: <001c01c2134d$6811ed10$8ea8a8a8@yuanfei>
sleepygod@sina.com said:
> I have a flash module come with Linkup7205SDB, which got total 8
> AM29LV160DT chips on it. We use it in 32bit mode 4way interleave. But
> some how I only can detect the first 8M, the kernel give me the
> following messages:
> Physmap flash device: 1000000 at 80000000
> Physically mapped flash: Found 4 x16 devices at 0x0 in 32-bit mode A
OK... can you try configuring the Physmap device to probe only for the
_second_ set of flash chips -- are they at 0x80800000?
If it finds them there, we need to add some debugging code and work out why
it's not doing so after finding the first set.
--
dwmw2
prev parent reply other threads:[~2002-06-14 7:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-14 2:44 MTD 16M Flash module detection error? Sleepy
2002-06-14 7:35 ` David Woodhouse [this message]
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=17698.1024040146@redhat.com \
--to=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=sleepygod@sina.com \
/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