From: Jan Kardell <jan.kardell@telliq.com>
To: Richard Weinberger <richard.weinberger@gmail.com>,
Emil Lenngren <emil.lenngren@gmail.com>
Cc: Richard Weinberger <richard@nod.at>,
linux-mtd <linux-mtd@lists.infradead.org>,
Patrick Doyle <wpdster@gmail.com>,
Artem Bityutskiy <dedekind1@gmail.com>
Subject: Re: [PATCH 1/1] ubi: Allow ubiblock devices nodes to be created by volume name instead of volume ID.
Date: Sun, 29 Sep 2019 15:39:23 +0200 [thread overview]
Message-ID: <f07e281f-a8e1-b4f8-de4a-264501f565f5@telliq.com> (raw)
In-Reply-To: <CAFLxGvxT3qDJT+7T4DQOq2j45OPV1AuvErEaYfpLP6SH7LX0OQ@mail.gmail.com>
Richard Weinberger skrev:
> On Wed, Aug 28, 2019 at 3:39 PM Emil Lenngren <emil.lenngren@gmail.com> wrote:
>> Will this really work when passing the rootfs to the kernel command
>> line like "root=/dev/ubiblock0_rootfs"? If the udev rules that set up
>> the symbolic link /dev/ubiblock0_rootfs are stored in a file on the
>> rootfs itself, I guess that symlink can't be made available before the
>> rootfs is mounted...
> No, this will not work directly from the kernel command line.
> For any kind non-trivial root you need an initramfs,
> that's the whole point of initramfs. :-)
>
I have this on my cmdline:
root=ubi0:rootfs rw ubi.mtd=rootfs,2048 rootfstype=ubifs
Maybe a bit confusing that both the MTD partition and the UBI volume are
named rootfs:-) The board uses a very old 3.14 kernel from OpenWrt, I
believe the MTD parts is vanilla. Doesn't this work on a more recent kernel?
//Jan
--
"I have always wished for my computer to be as easy to use as my telephone; my wish has come true because I can no longer figure out how to use my telephone."
- Bjarne Stroustrup
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2019-09-29 13:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-04 15:29 [PATCH 1/1] ubi: Allow ubiblock devices nodes to be created by volume name instead of volume ID Patrick Doyle
2019-04-04 19:37 ` Richard Weinberger
2019-08-14 12:34 ` Emil Lenngren
2019-08-14 18:06 ` Patrick Doyle
2019-08-18 21:03 ` Richard Weinberger
2019-08-18 20:49 ` Richard Weinberger
2019-08-28 13:38 ` Emil Lenngren
2019-08-28 14:13 ` Richard Weinberger
2019-09-29 13:39 ` Jan Kardell
2019-09-29 13:39 ` Jan Kardell [this message]
2019-09-29 17:40 ` Richard Weinberger
2019-12-30 17:31 ` Ezequiel Garcia
2020-01-02 19:06 ` Patrick Doyle
2020-01-08 22:43 ` Richard Weinberger
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=f07e281f-a8e1-b4f8-de4a-264501f565f5@telliq.com \
--to=jan.kardell@telliq.com \
--cc=dedekind1@gmail.com \
--cc=emil.lenngren@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=richard.weinberger@gmail.com \
--cc=richard@nod.at \
--cc=wpdster@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).