On Thu, 2015-04-16 at 19:55 -0300, Rogério Brito wrote: > Hi, Scott and others. > > On Apr 09 2015, Rogério Brito wrote: > > On Apr 09 2015, Scott Wood wrote: > > > On Thu, 2015-04-09 at 18:54 -0300, Rogério Brito wrote: > > > > > > > > mtdparts=myflash:4096k(allflash),3072k(firmimg),448k@3072k(bootcode),64k@3520k(status),512k@3584k(conf) > > > > > > What is "myflash"? You need to match the device name that the kernel > > > uses. > > > > From the documentation that I read, it *seemed* to be an arbitrary name and, > > to be screamingly different from anything else, I just picked "myflash". > > So, in my case (see dmesg snippet below), I would use "physmap-flash.0", > > right? Or would that be "physmap-flash"? Or something else entirely? > > Is there any "proper" way for me to discover what device name the kernel > uses? I have tried the following command lines without success: > > 1 - > mtdparts=myflash:4096k(allflash),3072k(firmimg),448k@3072k(bootcode),64k@3520k(status),512k@3584k(conf) > 2 - > mtdparts=physmap-flash:3072k(firmimg),448k@3072k(bootcode),64k@3520k(status),512k@3584k(conf) > 3 - > mtdparts=cfi_cmdset_0002:3072k(firmimg),448k@3072k(bootcode),64k@3520k(status),512k@3584k(conf)
Look in sysfs. -Scott _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
