All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vikram Narayanan <vikram186@gmail.com>
To: Huang Shijie <b32955@freescale.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: mtd_oobtest fails with GPMI-NAND
Date: Tue, 29 Jan 2013 21:58:09 +0530	[thread overview]
Message-ID: <5107F899.5090506@gmail.com> (raw)
In-Reply-To: <510735B3.1040509@freescale.com>

On 1/29/2013 8:06 AM, Huang Shijie wrote:
>> May I know in what way the driver is restricted for using with other
>> boards?
> The devicetree. Please check the dts file in arch/arm/boot/dts/.
> If there is no dts file for your board, the gpmi will not works very
> well for your board.
> for example, there is arch/arm/boot/dts/imx6q-arm2.dts for the MX6Q-ARM2
> board.

I've a valid dts file for my board which is good enough to probe the 
Toshiba NAND on-board and mount a UBIFS filesystem.

>> You're right and we knew it earlier as the Kernel detects the OOB size
>> as 128 bytes. So, some remaining bytes become unused at the end of
>> each page. i.e., (224-128). Instead of supporting ecc strength as ECC9
>> we end up using ECC8. Should this be a cause for the -74 error?
> no. this is not the cause. even you get the wrong geometry of the nand
> chip. the gpmi still can works.
>
> I think the root cause is the devicetree issue as above.

Something else is causing the issue. Can you give some other pointers 
which can potentially cause this -74 error while mounting?

Regards,
Vikram

  reply	other threads:[~2013-01-29 16:28 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-18 16:52 mtd_oobtest fails with GPMI-NAND Vikram Narayanan
2013-01-21  2:12 ` Huang Shijie
2013-01-28  2:39   ` Vikram Narayanan
2013-01-28  3:20     ` Huang Shijie
2013-01-28 17:04       ` Vikram Narayanan
2013-01-29  2:06         ` Huang Shijie
2013-01-29  2:26           ` Vikram Narayanan
2013-01-29  2:36             ` Huang Shijie
2013-01-29 16:28               ` Vikram Narayanan [this message]
2013-01-30  2:27                 ` Huang Shijie
2013-02-02  6:41                   ` Vikram Narayanan
2013-02-02  7:42                     ` Huang Shijie
2013-02-02  7:46                       ` Huang Shijie
2013-05-08 14:33                     ` Stefan Roese
2013-05-09 12:30                       ` Vikram Narayanan
2013-05-10  6:20                         ` Stefan Roese
2013-05-12 12:10                           ` Vikram Narayanan
2013-05-12 15:09                             ` Stefan Roese
2013-05-13 16:38                               ` Vikram Narayanan
2013-05-13  2:51                           ` Huang Shijie
2013-05-13  8:01                             ` Stefan Roese
2013-05-13  9:01                               ` Huang Shijie
2013-05-13  9:22                                 ` Stefan Roese
2013-05-13  9:34                                   ` Huang Shijie
2013-05-13 10:02                                     ` Stefan Roese
2013-05-14  2:09                                       ` Huang Shijie
2013-05-14  2:11                                       ` Huang Shijie
2013-05-13 16:51                                 ` Vikram Narayanan
2013-05-14  2:23                                   ` Huang Shijie
2013-05-14  2:33                                     ` Vikram Narayanan
2013-05-14  2:47                                       ` Huang Shijie
2013-05-13 16:43                               ` Vikram Narayanan

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=5107F899.5090506@gmail.com \
    --to=vikram186@gmail.com \
    --cc=b32955@freescale.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.