From: Marek Vasut <marek.vasut@gmail.com>
To: Robert Jarzmik <robert.jarzmik@free.fr>
Cc: linux-mtd@lists.infradead.org, Mike Dunn <mikedunn@newsguy.com>
Subject: Re: [PATCH] Add driver for M-sys / Sandisk diskonchip G4 nand flash
Date: Thu, 13 Oct 2011 02:26:38 +0200 [thread overview]
Message-ID: <201110130226.38567.marek.vasut@gmail.com> (raw)
In-Reply-To: <8762jtlx19.fsf@free.fr>
On Wednesday, October 12, 2011 11:28:34 PM Robert Jarzmik wrote:
> Mike Dunn <mikedunn@newsguy.com> writes:
> > This is a driver for the diskonchip G4 in my Palm Treo680. I've tested
> > it fairly well; it passes the nandtest utility, and I've been able to
> > create a ubifs using it.
>
> Hi Mike,
>
Hi Robert,
> I had a look at your driver, to see how close it was to the docg3 I
> submitted before and if we could share some code.
>
> My feeling is that the 2 chips are a bit different, and that the deserve
> each a separate driver, until one can manage them both (if that ever is
> possible). The discrepencies I noticed are :
> - docg4 doesn't need to write to an "address register" before reading some
> random register (ie. between io+0x1000 and io+0x1800), docg3 needs it
This can be done on both ...
> - docg4 adressing is larger (4 bytes against 3 in docg3)
if (drvdata->version == 4) {} ?
> - docg4 adressing is different (the calculation 0x108 * page_number),
> while docg3 is more straight forward (0x100 * page)
See above ... you can determine if it's G3 or G4 by version register iirc ?
> - in docg4 driver, I didn't see the "2 pages per block notion". I think
> it's there, but I couldn't find it
> - some read/write sequences are different, with different registers, and
> with additionnal reads in your case (ie. the MYSTERY register for
> example).
This can be done on G3 too?
>
> The good part is that I think we share the same registers, although you
> seem to have more of them. And I think the BCH algorithm is the same, and
> I'm really interested in the outcome of your work with Ivan.
>
> Therefore, I'll help review your driver as much as I can, so that you can
> merge it in mainline.
>
Definitelly looking forward to this too. I can try on PalmT5 if you like, it
SHOULD have a G3. You can also prep me a testing patch on top of this one which
would add support for G3 and I can test that too.
Cheers
next prev parent reply other threads:[~2011-10-13 0:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-10 14:48 [PATCH] Add driver for M-sys / Sandisk diskonchip G4 nand flash Mike Dunn
2011-10-10 15:51 ` Marek Vasut
2011-10-10 18:12 ` Ivan Djelic
2011-10-10 21:02 ` Mike Dunn
2011-10-11 11:50 ` Ivan Djelic
2011-10-11 19:17 ` Mike Dunn
2011-10-12 18:49 ` Ivan Djelic
2011-10-13 1:18 ` Mike Dunn
2011-10-13 6:58 ` Robert Jarzmik
2011-10-13 8:37 ` Ivan Djelic
2011-10-13 15:52 ` Mike Dunn
2011-10-10 20:20 ` Mike Dunn
2011-10-12 21:28 ` Robert Jarzmik
2011-10-13 0:26 ` Marek Vasut [this message]
2011-10-13 2:25 ` Mike Dunn
2011-10-13 1:53 ` Mike Dunn
2011-10-17 21:45 ` Mike Dunn
2011-10-20 16:31 ` Artem Bityutskiy
2011-10-20 19:57 ` Mike Dunn
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=201110130226.38567.marek.vasut@gmail.com \
--to=marek.vasut@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=mikedunn@newsguy.com \
--cc=robert.jarzmik@free.fr \
/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;
as well as URLs for NNTP newsgroup(s).