linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Ronald Madrid <ron_madrid@hotmail.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: NAND command line partiions
Date: Thu, 1 May 2008 14:01:04 -0500	[thread overview]
Message-ID: <20080501190104.GA2645@loki.buserror.net> (raw)
In-Reply-To: <BAY114-W26E8656DD55138DB5CC3A6F4DB0@phx.gbl>

On Thu, May 01, 2008 at 11:24:35AM -0700, Ronald Madrid wrote:
> I am using u-boot-1.3.1 in order to boot linux 2.6.25 on a custom MPC8313
> based board.  In past versions of the kernel I was able to pass the NAND
> partition information to the kernel with this line: root=/dev/mtdblock2
> rootfstype=jffs2 rw console=ttyS0,115200
> mtdparts=nand0:1M(u-boot),3M(kernel),-(jffs2).  In this latest version the
> kernel will not mount the partitions because the name that is parsed from
> the command line (nand0) is different from that of the name of the NAND
> that comes from ./drivers/mtd/nand/nand_ids.c (NAND 256MiB 3,3V 8-bit).

This is fixed in the current mtd tree (commit 9ebed3e60f9, fsl_elbc_nand:
fix mtd name).

> I have tried to change the name of the NAND that is passed in via the
> command line, but u-boot does not seem to like the format of the name that
> linux compares against.  It doesn't like the ,(comma) in 3,3V.

Why would u-boot care about the format of the kernel command line?

-Scott

      reply	other threads:[~2008-05-01 19:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1410.216.70.248.131.1209657620.squirrel@mechanicalanarchy.com>
2008-05-01 18:24 ` NAND command line partiions Ronald Madrid
2008-05-01 19:01   ` Scott Wood [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=20080501190104.GA2645@loki.buserror.net \
    --to=scottwood@freescale.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=ron_madrid@hotmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).