public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale•com>
To: "Matthew L. Creech" <mlcreech@gmail•com>
Cc: linuxppc-dev@ozlabs•org
Subject: Re: NAND partition names in DTS must be named "partition"?
Date: Mon, 21 Sep 2009 17:36:25 -0500	[thread overview]
Message-ID: <4AB7FFE9.8050206@freescale.com> (raw)
In-Reply-To: <5ee96a840909211527g45b47b3fgff907df69fe48666@mail.gmail.com>

Matthew L. Creech wrote:
> I upgraded from 2.6.29 to 2.6.31, and the kernel no longer recognized
> the partitions embedded within my DTS file.  I had to revert this
> change:
> 
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=4b08e149c0e02e97ec49c2a31d14a0d3a02f8074
> 
> in order to boot.  This code looks like it expects all partitions to
> be named "partition", otherwise they're just skipped.  Is there some
> peculiarity in my setup that makes this not work, or is it a general
> problem?  I see no major differences between my DTS file and the
> stardard "mpc8313erdb.dts".

It looks like mpc8313erdb.dts needs to be updated.

That, and Documentation/powerpc/dts-bindings/mtd-physmap.txt, which 
still says, "Each node's name represents the name of the corresponding
partition of the flash device," and has examples whose names are not 
"partition". :-P

-Scott

  reply	other threads:[~2009-09-21 22:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-21 22:27 NAND partition names in DTS must be named "partition"? Matthew L. Creech
2009-09-21 22:36 ` Scott Wood [this message]
2009-09-21 23:01   ` Anton Vorontsov
2009-09-21 23:05     ` Scott Wood

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=4AB7FFE9.8050206@freescale.com \
    --to=scottwood@freescale$(echo .)com \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    --cc=mlcreech@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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