From: Huang Shijie <b32955@freescale.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: linux-mtd@lists.infradead.org, Huang Shijie <shijie8@gmail.com>,
dedekind1@gmail.com
Subject: Re: [PATCH] mtd : add parsing code for one kind of Hynix's nand chip
Date: Wed, 18 Apr 2012 15:52:19 +0800 [thread overview]
Message-ID: <4F8E72B3.1090205@freescale.com> (raw)
In-Reply-To: <CAN8TOE_yhvB+xnyS_UZn0ko+QySFZJsYBk5w0PB_O37eZaQj9g@mail.gmail.com>
于 2012年04月18日 13:00, Brian Norris 写道:
> Now that I've given them all a second read, it really looks like this
> new Hynix chip actually follows no discernible pattern, which seems to
> suggest that we have to know all the chip parameters in order to know
> which ID decode table to use...but if we know all the parameters, then
> why do we need the table?? (Just being devil's advocate) If I had
This makes me confused too.
It looks like hardcode when i use the 0xd7 to disdinguish this nand chip.
> samples of all the chips, perhaps I could test some to determine other
> patterns, like ID wraparound behavior, but I doubt it...
>
> So really, I'd be interested in asking Hynix (and Toshiba and probably
> Samsung, for that matter): what do you expect software developers to
> do when you provide datasheets with useless ID decode tables? Are we
> supposed to read your mind to determine which chips are supposed to
> follow a given decode table?
>
> But seriously: let me know if you have better insight into how to
> associate this table with a set of chip IDs. Otherwise, I might as
I only have the H27UBG8T2A nand chip in my hand, and test it in the
imx28 board.
I do not have other nand chips which may also follow the same parsing
code as the H27UBG8T2A.
Best Regards
Huang Shijie
> well finish adding an 8-byte ID table and adding this one chip
> manually.
next prev parent reply other threads:[~2012-04-18 7:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-10 2:56 [PATCH] mtd : add parsing code for one kind of Hynix's nand chip Huang Shijie
2012-04-11 16:52 ` Brian Norris
2012-04-12 2:43 ` Huang Shijie
2012-04-18 5:00 ` Brian Norris
2012-04-18 7:52 ` Huang Shijie [this message]
2012-09-15 5:27 ` Brian Norris
2012-04-18 5:00 ` Brian Norris
2012-08-17 8:43 ` Huang Shijie
2012-08-18 2:51 ` Brian Norris
2012-08-20 6:01 ` Huang Shijie
2012-09-15 4:39 ` Brian Norris
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=4F8E72B3.1090205@freescale.com \
--to=b32955@freescale.com \
--cc=computersforpeace@gmail.com \
--cc=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=shijie8@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.