From: Thomas Gleixner <tglx@linutronix.de>
To: Kalev Lember <kalev@colleduc.ee>
Cc: Nicolas Pouillon <nipo@ssji.net>, linux-mtd@lists.infradead.org
Subject: Re: [PATCH]Probing at 0x0
Date: Fri, 08 Oct 2004 21:05:53 +0200 [thread overview]
Message-ID: <1097261009.11402.1703.camel@thomas> (raw)
In-Reply-To: <4166DC47.5010104@colleduc.ee>
On Fri, 2004-10-08 at 20:28, Kalev Lember wrote:
> No, it is not supported. According to
> http://www.tri-m.com/products/msystems/files/specs/mddoc_spec.pdf the 32
> MB Millennium Plus has 16 bit data bus while the supported 16 MB Mil+
> has 8 bit bus.
Hmm, I think you talk about different things.
>> This time, chip is probed as a DoC-Mil+ 32MB, driver complains about
>> it not being supported. It seems ok, and as mtd are much like rocket
>> science to me, I'll wait a little until it is (i hope) supported...
The DoC has Doc-chip-ID 0x41 according to the datasheet.
http://www.m-systems.com/files/documentation/doc/Mobile_Plus_32_64MB_DS_Rev1.7.pdf
from include/linux/mtd/doc2000.h
#define DOC_ChipID_DocMilPlus32 0x40
#define DOC_ChipID_DocMilPlus16 0x41
So how is it identified as a Mil+32 ?
The chip can be accessed in 16 bit mode, but it does not need the two
parallel chip magic which are neccecary for the Mil+32.
Please correct me, if I'm wrong or talking about something different :)
tglx
next prev parent reply other threads:[~2004-10-08 19:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-04 19:50 [PATCH]Probing at 0x0 Nicolas Pouillon
2004-10-04 21:53 ` Thomas Gleixner
2004-10-05 8:59 ` Kalev Lember
2004-10-06 19:34 ` Nicolas Pouillon
2004-10-08 18:28 ` Kalev Lember
2004-10-08 19:05 ` Thomas Gleixner [this message]
2004-10-11 9:00 ` Kalev Lember
2004-10-11 12:41 ` Nicolas Pouillon
2004-10-08 19:15 ` David Woodhouse
2004-10-11 12:23 ` Kalev Lember
2004-10-11 12:25 ` David Woodhouse
2004-10-11 13:12 ` 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=1097261009.11402.1703.camel@thomas \
--to=tglx@linutronix.de \
--cc=kalev@colleduc.ee \
--cc=linux-mtd@lists.infradead.org \
--cc=nipo@ssji.net \
/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