From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] fsl_elbc_nand bug
Date: Mon, 18 May 2015 17:41:54 -0500 [thread overview]
Message-ID: <1431988914.27761.18.camel@freescale.com> (raw)
In-Reply-To: <1431987027.14341.111.camel@andreilinux>
On Mon, 2015-05-18 at 15:10 -0700, Andrei Yakimov wrote:
> I will try, It will take a while due to I am not working with
> latest code. I do have a chip with first 2 parameter blocks
> corrupted. So I can test it. I can not send it to Linux -
> I am not subscribed to any Linux mailing lists.
You don't need to be subscribed to a list to send a patch (but it does
need to be based on the latest upstream tree).
> As of patch structure:
>
> 1) separate READID and PARAM command.
> 2) READID will read 5 bytes as per ONFI spec.
> 3) PARAM command will read 768 bytes as per ONFI spec.
> I will check is path to send read size are valid
> for this command - but it will affect every NAND driver,
It wouldn't affect every NAND driver. There should be a default
implementation that calls cmdfunc, so that things work the same way as
now unless a driver overrides it.
-Scott
prev parent reply other threads:[~2015-05-18 22:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-15 21:48 [U-Boot] fsl_elbc_nand bug Andrei Yakimov
2015-05-18 21:17 ` Scott Wood
2015-05-18 22:10 ` Andrei Yakimov
2015-05-18 22:41 ` Scott Wood [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=1431988914.27761.18.camel@freescale.com \
--to=scottwood@freescale.com \
--cc=u-boot@lists.denx.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