All of lore.kernel.org
 help / color / mirror / Atom feed
From: Claudio Lanconelli <lanconelli.claudio@eptar.com>
To: javier Martin <javier.martin@vista-silicon.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: mxc_nand: Problem with K9F1G08X0A Samsung flash
Date: Fri, 26 Jun 2009 12:35:17 +0200	[thread overview]
Message-ID: <4A44A465.7020802@eptar.com> (raw)
In-Reply-To: <eedb5540906260204u518d564o9d862485379eedfe@mail.gmail.com>

Hi Javier,
you can find the patch here:
http://lists.infradead.org/pipermail/linux-mtd/2009-May/025740.html

javier Martin ha scritto:
> Hello, I am using a Samsung K9F1G08X0A NAND flash with my i.mx27 based
> board and last stable 2.6.30 kernel.
> 
> I am experimenting the same problem as Alberto Panizzo
> (http://lists.infradead.org/pipermail/linux-mtd/2009-May/025704.html).
> Linux does not detect any correct block in my NAND flash.
> 
> Scanning device for bad blocks
> Bad eraseblock 0 at 0x000000000000
> Bad eraseblock 1 at 0x000000020000
> Bad eraseblock 2 at 0x000000040000
> Bad eraseblock 3 at 0x000000060000
> Bad eraseblock 4 at 0x000000080000
> Bad eraseblock 5 at 0x0000000a0000
> Bad eraseblock 6 at 0x0000000c0000
> Bad eraseblock 7 at 0x0000000e0000
> .... all blocks ...
> Bad eraseblock 2045 at 0x00000ffa0000
> Bad eraseblock 2046 at 0x00000ffc0000
> Bad eraseblock 2047 at 0x00000ffe0000
> RedBoot partition parsing not available
> Registering mxc_nand as whole device
> 
> I read some people saying that it is due to the lack of 2KB page
> support. Also Vladimir Barinov said he would post a patch for this in
> a separate thread but I couldn't find it.
> 
> Have you already solved this problem?
> 
> Thank you.
> 
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
> 
> 

      reply	other threads:[~2009-06-26 10:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-26  9:04 mxc_nand: Problem with K9F1G08X0A Samsung flash javier Martin
2009-06-26 10:35 ` Claudio Lanconelli [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=4A44A465.7020802@eptar.com \
    --to=lanconelli.claudio@eptar.com \
    --cc=javier.martin@vista-silicon.com \
    --cc=linux-mtd@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.