From: Nicolas Pouillon <nipo@ssji.net>
To: tglx@linutronix.de
Cc: linux-mtd@lists.infradead.org
Subject: Re: Patch !
Date: Sun, 3 Oct 2004 22:18:27 +0200 [thread overview]
Message-ID: <20041003221827.7bea56fc.nipo@ssji.net> (raw)
In-Reply-To: <1096768161.21297.129.camel@thomas>
[-- Attachment #1: Type: text/plain, Size: 1879 bytes --]
[Sun, 03 Oct 2004 03:49:21 +0200]
Thomas Gleixner <tglx@linutronix.de> eut le bonheur d'écrire:
> It's quite stable now. The experimental will go away soon.
;)
> I see. But you will not be able to use the chip really, as the code in
> mtd/devices and the old inftl driver are missing functionality (e.g.
> write support).
Short term I dont care about write support, as I wont have two chances
to rewrite the DoC, if I screw things up, the only thing I will be able
to do is get the device back to service (and they wont want to repair
it, I opened it...)
Unless... Is there some means to access DoC through JTAG ?
I've seens some pages saying it works, but I'm not too sure it actually
was speaking of the case I have : A PXA and a M-Sys DoC.
> The new code supports the usage of NAND aware
> filesystems like JFFS2 too. So you don't even need the INFTL stuff, if
> you must not provide compability with the M-Sys stuff.
Mh, what is "compatibility with M-Sys stuff" ?
> The MTD CVS patch (use patches/patchin.sh) should work with 2.6.7.
> Hmm, the __iomem related changes are not in 2.6.7. Thats just a simple
> #define. The code runs on 2.4 too. See compatmac.h
I'll have a look at it ;)
> > Things I can read on the chip (hoping i'm correct, it is not very
> > readable) are:
> > "M-Systems
> > Disc-on-chip
> > MD333-D64-V3-X
> > Japan 033-----" (dunno what's under "----")
>
> MD3331-D64-V3-T 64MB/512Mb FBGA 3.3V
64MB, 3.3V, BGA, yes ;)
Picture here, to confirm (I actually forgot the 1 after "333"):
http://a620.zwischenstand.de/Photos/DoC/dscn2499.jpg
(photos I have without the sticker are bad)
> That's the only one I found on the M-Sys webpage which has a similar
> type code.
This is it. Is chip ID 0xa5 ?
Cheers !
--
Nipo <nipo@ssji.net>
Gnu-PGP: 1024D/1DBF658F
http://nipo.ssji.net/nipo.asc
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-10-03 20:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-01 13:46 Issues with a Doc Milplus Nicolas Pouillon
2004-10-01 13:57 ` David Woodhouse
2004-10-01 14:27 ` Nicolas Pouillon
2004-10-02 13:55 ` Patch ! Nicolas Pouillon
2004-10-02 20:42 ` Thomas Gleixner
2004-10-03 1:11 ` Nicolas Pouillon
[not found] ` <20041003030653.2e0452a7.nipo@ssji.net>
[not found] ` <1096768161.21297.129.camel@thomas>
2004-10-03 20:18 ` Nicolas Pouillon [this message]
2004-10-04 8:05 ` Thomas Gleixner
2004-10-04 16:38 ` Nicolas Pouillon
2004-10-04 17:59 ` Thomas Gleixner
2004-10-04 20:47 ` Nicolas Pouillon
2004-10-04 21:04 ` 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=20041003221827.7bea56fc.nipo@ssji.net \
--to=nipo@ssji.net \
--cc=linux-mtd@lists.infradead.org \
--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