All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@mvista.com>
To: sshahrom@micron.com
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: [PATCH 1/3] [ARM] OMAP: Adding Support for 2K nand page support for	omap2430
Date: Thu, 16 Aug 2007 17:27:28 -0700	[thread overview]
Message-ID: <46C4EB70.2020802@mvista.com> (raw)
In-Reply-To: <809D758398CC1F49AA8E493528AD4A27014DF6AD@ntxsjombx02.micron.com>

sshahrom@micron.com wrote:
> Hello,
> Following patches would add support for 2k Page nand with Enabled HW ECC on omap2430 v4.0. It has been Tested with Micron Nand. The Patch is against 2.6.22 linux-omap.git tree. As Always all the comments are welcomed.
> 

Shahrom,

Have you done any testing with your driver with the NAND part on the
2430SDP-v5.0 boards?

Using your driver, the chip is probed/reported correctly (see boot
excerpt below), but the I can't seem to use the MTD tools to work with
any of the partitions?

For example, flash_info gives: 'Device /dev/mtdX has 0 erase regions'
for each partition on the NAND device.  And trying a flash_erase gives
'File open error'.

Any ideas?

Kevin


[...]
omap2-nand driver initializing


NAND device: Manufacturer ID: 0xec, Chip ID: 0x46 (Samsung NAND 64MiB
1,8V 16-bi

t)


2048 byte HW ECC not possible on 512 byte page size, fallback to SW ECC


Creating 5 MTD partitions on "omap2-nand":


0x00000000-0x00080000 : "X-Loader"


0x00080000-0x00100000 : "U-Boot"


0x00100000-0x00140000 : "U-Boot Environment"


0x00140000-0x00540000 : "Kernel"


0x00540000-0x04000000 : "File System"
[...]

      reply	other threads:[~2007-08-17  0:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-27 17:10 [PATCH 1/3] [ARM] OMAP: Adding Support for 2K nand page support for omap2430 sshahrom
2007-08-17  0:27 ` Kevin Hilman [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=46C4EB70.2020802@mvista.com \
    --to=khilman@mvista.com \
    --cc=linux-omap-open-source@linux.omap.com \
    --cc=sshahrom@micron.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 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.