From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Matthieu CASTET <matthieu.castet@parrot.com>
Cc: Huang Shijie <b32955@freescale.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
David Woodhouse <David.Woodhouse@intel.com>,
Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
Subject: Re: [PATCH] mtd/nand: don't use {read,write}_buf for 8-bit transfers
Date: Fri, 1 Mar 2013 10:59:14 +0100 [thread overview]
Message-ID: <20130301095914.GK22886@pengutronix.de> (raw)
In-Reply-To: <513072F5.6010609@parrot.com>
On Fri, Mar 01, 2013 at 10:20:53AM +0100, Matthieu CASTET wrote:
> Huang Shijie a écrit :
> > 于 2013年02月27日 23:10, Uwe Kleine-König 写道:
> >> According to the Open NAND Flash Interface Specification (ONFI) Revision
> >> 3.1 "Parameters are always transferred on the lower 8-bits of the data
> >> bus." for the Get Features and Set Features commands.
> >>
> > yes. the set/get features should works in 8-bit.
> >
> > I have never met a 16-bit onfi nand yet. :)
>
> Beagle board got one.
Which part does it have? Would you volunteer to test access to its OTP
area? (Provided you have a Micron chip of course.)
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2013-03-01 9:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-27 15:10 [PATCH] mtd/nand: don't use {read,write}_buf for 8-bit transfers Uwe Kleine-König
2013-02-28 2:47 ` Huang Shijie
2013-02-28 9:30 ` Uwe Kleine-König
2013-02-28 10:48 ` Uwe Kleine-König
2013-03-01 3:34 ` Huang Shijie
2013-03-01 8:50 ` Uwe Kleine-König
2013-03-01 8:59 ` Huang Shijie
2013-03-01 9:20 ` Matthieu CASTET
2013-03-01 9:59 ` Uwe Kleine-König [this message]
2013-03-01 14:00 ` Matthieu CASTET
2013-02-28 10:33 ` Huang Shijie
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=20130301095914.GK22886@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=David.Woodhouse@intel.com \
--cc=artem.bityutskiy@linux.intel.com \
--cc=b32955@freescale.com \
--cc=linux-mtd@lists.infradead.org \
--cc=matthieu.castet@parrot.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.