From: "Rogério Brito" <rbrito@ime.usp.br>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: Old regression with MTD devices disappearing from a Kurobox HD/HG
Date: Thu, 16 Apr 2015 21:01:07 -0300 [thread overview]
Message-ID: <20150417000107.GA5106@ime.usp.br> (raw)
In-Reply-To: <1429226861.32545.30.camel@freescale.com>
Dear Scott.
On Apr 16 2015, Scott Wood wrote:
> On Thu, 2015-04-16 at 19:55 -0300, Rogério Brito wrote:
> > 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.
The output that I get from sysfs is:
# ls -l /sys/block/mtdblock0
lrwxrwxrwx 1 root root 0 Apr 16 20:42 /sys/block/mtdblock0 -> ../devices/platform/physmap-flash.0/mtd/mtd0/mtdblock0
# cat /sys/devices/platform/physmap-flash.0/uevent
DRIVER=physmap-flash
MODALIAS=platform:physmap-flash
# cat /sys/devices/platform/physmap-flash.0/driver_override
(null)
So, it is saying that the driver is physmap-flash, right? I will compile
now a (new) kernel 4.0 with the parameter passed as my 2nd attempt above
(just to make sure that I have not messed up before). Just to confirm, this
should (in theory) work, right?
Anything else that I can provide? Again, just ask me and I will do my best
to collect the needed information.
Thanks once again,
--
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
next prev parent reply other threads:[~2015-04-17 0:01 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
2015-04-17 0:01 ` Rogério Brito [this message]
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=20150417000107.GA5106@ime.usp.br \
--to=rbrito@ime.usp.br \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=scottwood@freescale.com \
/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.