From: Artem Bityutskiy <dedekind1@gmail.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: linux-mtd@lists.infradead.org,
David Woodhouse <dwmw2@infradead.org>,
Matthieu Castet <matthieu.castet@parrot.com>,
Alexander Shiyan <shc_work@mail.ru>
Subject: Re: [PATCH] mtd: nand: fix NAND_BUSWIDTH_AUTO for x16 devices
Date: Fri, 02 Aug 2013 19:05:20 +0300 [thread overview]
Message-ID: <1375459520.14869.356.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <1374135422-8975-1-git-send-email-computersforpeace@gmail.com>
On Thu, 2013-07-18 at 01:17 -0700, Brian Norris wrote:
> The code for NAND_BUSWIDTH_AUTO is broken. According to Alexander:
>
> "I have a problem with attach NAND UBI in 16 bit mode.
> NAND works fine if I specify NAND_BUSWIDTH_16 option, but not
> working with NAND_BUSWIDTH_AUTO option. In second case NAND
> chip is identifyed with ONFI."
Pushed to l2-mtd.git, thanks!
--
Best Regards,
Artem Bityutskiy
prev parent reply other threads:[~2013-08-02 16:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-18 8:17 [PATCH] mtd: nand: fix NAND_BUSWIDTH_AUTO for x16 devices Brian Norris
2013-08-02 16:05 ` Artem Bityutskiy [this message]
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=1375459520.14869.356.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=matthieu.castet@parrot.com \
--cc=shc_work@mail.ru \
/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