Scott, Thanks for your help, I was able to get it working with the open firmware option you suggested. I had tried this a few days back with no luck, but I think my problem at that time was that my label "nand0" did not match what was in the dts file. I didn't give open firmware much attention because I am using the command line for the partition information in my working 2.6.20 kernel. After spending this much time on it though, I'll take what I can get.
Thanks, Joaquin Luna PS U-boot did not accept "ff800000.flash" as the MTD ID and could not load the kernel image with that in the command line. -----Original Message----- From: Scott Wood [mailto:[EMAIL PROTECTED] Sent: Monday, November 17, 2008 11:59 AM To: Joaquin Luna Cc: linuxppc-embedded@ozlabs.org Subject: Re: command line partition information Joaquin Luna wrote: > I do not list any partitions in my dts file, though I tried and not seen > any change in the behavior. I have enabled the option in the kernel to > parse the partition information from the kernel command line, is there > something else I need to do to set up the mtdblockX devices? Did you enable CONFIG_MTD_OF_PARTS for device-tree-based partitions? > mtdparts=mtdparts=nand0:2m(u-boot),3M(kernel),128K(dtb),30M(jffs2),32M(m ycust),90M(myfs),90M(myfs2) Try replacing "nand0" with "ff800000.flash". -Scott _______________________________________________ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded