Old regression with MTD devices disappearing from a Kurobox HD/HG

[Rogério Brito]

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 at 3072k(bootcode),64k at 3520k(status),512k at 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 at 3072k(bootcode),64k at 3520k(status),512k at 3584k(conf)
2 - mtdparts=physmap-flash:3072k(firmimg),448k at 3072k(bootcode),64k at 3520k(status),512k at 3584k(conf)
3 - mtdparts=cfi_cmdset_0002:3072k(firmimg),448k at 3072k(bootcode),64k at 3520k(status),512k at 3584k(conf)

The first one is the one from my previous post. The next ones had the name
of the device changed *and* the 4MB at the start removed.

Do you want my config file? Do you want any dmesg output?  Anything else
that I can provide?

> > What is "allflash"?  If the flash is only 4 MiB and you're trying to
> > make the first partition refer to the entire flash, it won't work.
> > It'll see that 4 MiB partition and ignore the rest as being beyond the
> > end of the device.
> 
> OK, I was just trying to mimic the layout that you can see here:
> 
>     http://buffalo.nas-central.org/wiki/Flash_ROM#Checking_the_layout_.28with_kernel_2.6.x.29

I have removed that parameter from the command line.


Thanks a lot for your help,

-- 
Rogério Brito : rbrito@{ime.usp.br,gmail.com} : GPG key 4096R/BCFCAAAA
http://cynic.cc/blog/ : github.com/rbrito : profiles.google.com/rbrito
DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br