From: Gabriel Tisan <gabriel.tisan@gmail.com>
To: "Eric Bénard" <eric@eukrea.com>
Cc: barebox@lists.infradead.org
Subject: Re: nand_imx 4k support ?
Date: Mon, 2 Apr 2012 11:03:06 +0200 [thread overview]
Message-ID: <CAD9ZU8D0a8BRAtAN8_9Hz_75Lek=N_i_F+jjXvfR1gxMsPNZ3A@mail.gmail.com> (raw)
In-Reply-To: <20120401150507.465b4a6d@eb-e6520>
Yes, Baruch I meant write support, especially ECC layout for 4K flashes.
Actually the 4k flashes could have 128 or 218 bytes OOB.
Could you point me to some docs about this layout ? I use a flash with
218 bytes spare.
Gabriel
On Sun, Apr 1, 2012 at 3:05 PM, Eric Bénard <eric@eukrea.com> wrote:
> Le Sun, 1 Apr 2012 15:52:09 +0300,
> Baruch Siach <baruch@tkos.co.il> a écrit :
>> Does the Linux kernel detect your flash correctly?
>>
> I'm not at this stage for the moment as I'm using a SDcard rootfs to
> validate the hardware for the moment, but I'm sure the actual problem
> (in my case at least) in barebox is a detection problem as I get the
> right values from the flash but these value are ONFI and thus are not
> right with he actual flash detection code which leads to a wrong
> configuration of the NFC. Once I hardcode the NFC settings I manage to
> read/write in the 4k NAND Flash from barebox (environment & kernel
> are in the flash for the moment).
>
> Eric
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2012-04-02 9:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-01 9:58 Gabriel Tisan
2012-04-01 10:49 ` Baruch Siach
2012-04-01 12:45 ` Eric Bénard
2012-04-01 12:52 ` Baruch Siach
2012-04-01 13:05 ` Eric Bénard
2012-04-02 9:03 ` Gabriel Tisan [this message]
2012-04-02 9:08 ` Eric Bénard
2012-04-02 11:30 ` Baruch Siach
2012-04-02 11:39 ` Gabriel Tisan
2012-04-02 11:47 ` Baruch Siach
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='CAD9ZU8D0a8BRAtAN8_9Hz_75Lek=N_i_F+jjXvfR1gxMsPNZ3A@mail.gmail.com' \
--to=gabriel.tisan@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=eric@eukrea.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox