From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Tony Wan <visual2me@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Fwd: anyone can help me about nand_get_flash_type
Date: Tue, 07 Sep 2010 06:29:01 -0700 [thread overview]
Message-ID: <4C863E1D.3050600@gmail.com> (raw)
In-Reply-To: <AANLkTikyM=XmFp2RSQtiHpoF3gVZKyEfpDFg2_Cd_ssW@mail.gmail.com>
On 09/06/2010 11:37 PM, Tony Wan wrote:
> Anyone can help me with this problem? even some ideas how to debug and
> find the problem? Thank you!
>
>
> ---------- Forwarded message ----------
> From: Tony Wan<visual2me@gmail.com>
> Date: Wed, Aug 25, 2010 at 5:36 PM
> Subject: anyone can help me about nand_get_flash_type
> To: linux-mtd@lists.infradead.org
>
>
> Hi there,
>
> I got an ARM device from Marvell with a NAND rom, running Linux
> 2.6.22.18. These days I'm working on upgrading the kernel to 2.6.31.8.
> After the upgrade, all devices work well except the NAND rom. I found
> it's because that the device and manufacturer IDs cannot be retrieved
> correctly in nand_get_flash_type. In 2.6.22.18, the IDs can be
> retrieved as expected; but in 2.6.31.8, the IDs always be 0, which
> leads to an error in nand_scan.
>
> I'm a definitely newbie with MTD, and currently have no idea about the
> problem. Except IO_ADDR_R& IO_ADDR_W are remapped to different
> addresses, I can't find any differences between the 2 versions from
> the system log -- may it be the reason? Anyone can give me some tips
> about this problem -- how to fix it or how to debug? Any suggestions
> will be appreciated.
>
> --
> Best regards,
> Tony Wan
>
>
>
in this case if 2.6.22 worked and 2.6.31 is broken Id suggest bisecting
this, since you have a good/bad starting point.
http://linux.yyz.us/git-howto.html
Justin P. Mattock
prev parent reply other threads:[~2010-09-07 13:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-25 9:36 anyone can help me about nand_get_flash_type Tony Wan
2010-09-07 6:37 ` Fwd: " Tony Wan
2010-09-07 13:29 ` Justin P. Mattock [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=4C863E1D.3050600@gmail.com \
--to=justinmattock@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=visual2me@gmail.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.