From: "Eric Bénard" <eric@eukrea.com>
To: Alex Gershgorin <alexg@meprolight.com>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: [PATCH] i.mx35pdk add nand identification
Date: Thu, 6 Sep 2012 16:39:39 +0200 [thread overview]
Message-ID: <20120906163939.74634e1b@eb-e6520> (raw)
In-Reply-To: <4875438356E7CA4A8F2145FCD3E61C0B3074AA38F5@MEP-EXCH.meprolight.com>
Hi,
Le Thu, 6 Sep 2012 17:20:41 +0300,
Alex Gershgorin <alexg@meprolight.com> a écrit :
>
> > > >Hi Alex,
>
> Le Thu, 6 Sep 2012 16:39:33 +0300,
> Alex Gershgorin <alexg@meprolight.com> a écrit :
> > > Without this patch I get following messages
> > >
> > > Board: Freescale MX35 3Stack
> > > NAND type unknown: ec,d7
> > > No NAND device found (-19)!
> > >
> > what is the part number of the NAND ?
> >
> > If I'm not mistaken
> > K9LBG08U0D-PCB0
> >
> > > > this seems to be a 4GiB flash with 4k page + 218 OOB, not a 512MiB
>
> If I understand correctly it should look like
>
> {__NANDSTR("NAND 4GiB 3,3V 8-bit"), 0xD7, 0, 2048, 0, LP_OPTIONS}
>
>
> Right?
no 2048 means 2k page, this nand has 4k page.
kernel has :
{"NAND 4GiB 3,3V 8-bit", 0xD7, 0, 4096, 0, LP_OPTIONS},
which should be the right configuration.
Eric
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2012-09-06 14:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-06 12:48 [PATCH] i.mx35pdk add nand identification Alex Gershgorin
2012-09-06 13:27 ` Eric Bénard
2012-09-06 13:39 ` Alex Gershgorin
2012-09-06 13:54 ` Eric Bénard
2012-09-06 14:20 ` Alex Gershgorin
2012-09-06 14:37 ` Alex Gershgorin
2012-09-06 14:39 ` Eric Bénard [this message]
2012-09-06 13:47 ` Sascha Hauer
2012-09-06 13:51 ` Alex Gershgorin
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=20120906163939.74634e1b@eb-e6520 \
--to=eric@eukrea.com \
--cc=alexg@meprolight.com \
--cc=barebox@lists.infradead.org \
/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.