All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: "Rogério Brito" <rbrito@ime.usp.br>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: Old regression with MTD devices disappearing from a Kurobox HD/HG
Date: Thu, 16 Apr 2015 18:27:41 -0500	[thread overview]
Message-ID: <1429226861.32545.30.camel@freescale.com> (raw)
In-Reply-To: <20150416225526.GB3373@ime.usp.br>

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

  reply	other threads:[~2015-04-16 23:28 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-04  5:40 Old regression with MTD devices disappearing from a Kurobox HD/HG Rogério Brito
2015-04-07 22:34 ` Scott Wood
2015-04-07 23:58   ` Rogério Brito
2015-04-08  0:02     ` Scott Wood
2015-04-08  0:37       ` Rogério Brito
2015-04-08  0:50         ` Scott Wood
2015-04-08  1:13           ` Rogério Brito
2015-04-08  1:27             ` ) Scott Wood
2015-04-08  1:56               ` Old regression with MTD devices disappearing from a Kurobox HD/HG Rogério Brito
2015-04-09 21:54                 ` Rogério Brito
2015-04-09 22:28                   ` Scott Wood
2015-04-09 23:12                     ` Rogério Brito
2015-04-16 22:55                       ` Rogério Brito
2015-04-16 23:27                         ` Scott Wood [this message]
2015-04-17  0:01                           ` Rogério Brito
2015-04-17  0:03                             ` Scott Wood
2015-04-17  0:14                               ` Rogério Brito

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=1429226861.32545.30.camel@freescale.com \
    --to=scottwood@freescale.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=rbrito@ime.usp.br \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.