From: Richard Weinberger <richard@nod.at>
To: Hauke Mehrtens <hauke@hauke-m.de>, dwmw2@infradead.org
Cc: robh+dt@kernel.org, mark.rutland@arm.com, dedekind1@gmail.com,
computersforpeace@gmail.com, devicetree@vger.kernel.org,
linux-mtd@lists.infradead.org
Subject: Re: [PATCH 1/2] ubi: mount partitions specified in device tree
Date: Sat, 18 Jun 2016 21:46:01 +0200 [thread overview]
Message-ID: <5765A4F9.3050107@nod.at> (raw)
In-Reply-To: <48242f26-7812-6957-6bf5-c12989b875b4@hauke-m.de>
Am 18.06.2016 um 21:35 schrieb Hauke Mehrtens:
> There are some devices on the market that are storing the root file
> system in an ubi layer.
> To make this work there are currently two options.
> 1. patch the kernel to specify which partitions to open in the code.
> 2. provide some kernel command line parameter which specifies what to open.
>
> I would like to specify this in device tree.
What is wrong with command line parameters? If there is some parameter
the UBI module misses I'll happily add it.
You can also put your kernel command line into device tree.
Thanks,
//richard
WARNING: multiple messages have this Message-ID (diff)
From: Richard Weinberger <richard-/L3Ra7n9ekc@public.gmane.org>
To: Hauke Mehrtens <hauke-5/S+JYg5SzeELgA04lAiVw@public.gmane.org>,
dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org
Cc: robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
mark.rutland-5wv7dgnIgG8@public.gmane.org,
dedekind1-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
computersforpeace-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-mtd-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH 1/2] ubi: mount partitions specified in device tree
Date: Sat, 18 Jun 2016 21:46:01 +0200 [thread overview]
Message-ID: <5765A4F9.3050107@nod.at> (raw)
In-Reply-To: <48242f26-7812-6957-6bf5-c12989b875b4-5/S+JYg5SzeELgA04lAiVw@public.gmane.org>
Am 18.06.2016 um 21:35 schrieb Hauke Mehrtens:
> There are some devices on the market that are storing the root file
> system in an ubi layer.
> To make this work there are currently two options.
> 1. patch the kernel to specify which partitions to open in the code.
> 2. provide some kernel command line parameter which specifies what to open.
>
> I would like to specify this in device tree.
What is wrong with command line parameters? If there is some parameter
the UBI module misses I'll happily add it.
You can also put your kernel command line into device tree.
Thanks,
//richard
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-06-18 19:46 UTC|newest]
Thread overview: 88+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-18 19:17 [PATCH 1/2] ubi: mount partitions specified in device tree Hauke Mehrtens
2016-06-18 19:17 ` Hauke Mehrtens
2016-06-18 19:17 ` [PATCH 2/2] ubi: open volumes define " Hauke Mehrtens
2016-06-18 19:17 ` Hauke Mehrtens
2016-06-18 23:36 ` Daniel Golle
2016-06-18 23:36 ` Daniel Golle
2016-06-19 21:21 ` Hauke Mehrtens
2016-06-19 21:21 ` Hauke Mehrtens
2016-06-24 18:45 ` Ezequiel Garcia
2016-06-24 18:45 ` Ezequiel Garcia
2016-06-25 20:24 ` Hauke Mehrtens
2016-06-25 20:24 ` Hauke Mehrtens
2016-06-18 19:30 ` [PATCH 1/2] ubi: mount partitions specified " Richard Weinberger
2016-06-18 19:30 ` Richard Weinberger
2016-06-18 19:35 ` Hauke Mehrtens
2016-06-18 19:35 ` Hauke Mehrtens
2016-06-18 19:46 ` Richard Weinberger [this message]
2016-06-18 19:46 ` Richard Weinberger
2016-06-18 22:54 ` Hauke Mehrtens
2016-06-18 22:54 ` Hauke Mehrtens
2016-06-19 8:41 ` Richard Weinberger
2016-06-19 8:41 ` Richard Weinberger
2016-06-18 23:20 ` Daniel Golle
2016-06-18 23:20 ` Daniel Golle
2016-06-19 8:53 ` Richard Weinberger
2016-06-19 8:53 ` Richard Weinberger
2016-06-19 9:16 ` Richard Weinberger
2016-06-19 9:16 ` Richard Weinberger
2016-06-19 11:25 ` Daniel Golle
2016-06-19 11:25 ` Daniel Golle
2016-06-19 12:02 ` Richard Weinberger
2016-06-19 12:02 ` Richard Weinberger
2016-06-19 13:05 ` Daniel Golle
2016-06-19 13:05 ` Daniel Golle
2016-06-19 13:19 ` Richard Weinberger
2016-06-19 13:19 ` Richard Weinberger
2016-06-19 14:09 ` Daniel Golle
2016-06-19 14:09 ` Daniel Golle
2016-06-19 14:35 ` Richard Weinberger
2016-06-19 14:35 ` Richard Weinberger
2016-06-19 15:24 ` Daniel Golle
2016-06-19 15:24 ` Daniel Golle
2016-06-19 15:31 ` Richard Weinberger
2016-06-19 15:31 ` Richard Weinberger
2016-06-19 16:13 ` Daniel Golle
2016-06-19 16:13 ` Daniel Golle
2016-06-19 16:53 ` Boris Brezillon
2016-06-19 16:53 ` Boris Brezillon
2016-06-19 19:42 ` Daniel Golle
2016-06-19 19:42 ` Daniel Golle
2016-06-19 20:14 ` Boris Brezillon
2016-06-19 20:14 ` Boris Brezillon
2016-06-19 21:48 ` Daniel Golle
2016-06-19 21:48 ` Daniel Golle
2016-06-19 22:21 ` Hauke Mehrtens
2016-06-19 22:21 ` Hauke Mehrtens
2016-06-20 8:09 ` Arnd Bergmann
2016-06-20 8:09 ` Arnd Bergmann
2016-06-20 8:26 ` Richard Weinberger
2016-06-20 8:26 ` Richard Weinberger
2016-06-20 15:08 ` Arnd Bergmann
2016-06-20 15:08 ` Arnd Bergmann
2016-06-20 17:24 ` Brian Norris
2016-06-20 17:24 ` Brian Norris
2016-06-20 19:57 ` Richard Weinberger
2016-06-20 19:57 ` Richard Weinberger
2016-06-20 21:18 ` Hauke Mehrtens
2016-06-20 21:18 ` Hauke Mehrtens
2016-06-20 17:05 ` Brian Norris
2016-06-20 17:05 ` Brian Norris
2016-06-19 15:43 ` Boris Brezillon
2016-06-19 15:43 ` Boris Brezillon
2016-06-19 16:23 ` Daniel Golle
2016-06-19 16:23 ` Daniel Golle
2016-06-20 17:03 ` Brian Norris
2016-06-20 17:03 ` Brian Norris
2016-06-24 18:28 ` Ezequiel Garcia
2016-06-24 18:28 ` Ezequiel Garcia
2016-06-25 20:20 ` Hauke Mehrtens
2016-06-25 20:20 ` Hauke Mehrtens
2016-06-25 20:33 ` Richard Weinberger
2016-06-25 20:33 ` Richard Weinberger
2016-06-18 23:56 ` Daniel Golle
2016-06-18 23:56 ` Daniel Golle
2016-06-19 21:36 ` Hauke Mehrtens
2016-06-19 21:36 ` Hauke Mehrtens
2016-06-19 21:52 ` Daniel Golle
2016-06-19 21:52 ` Daniel Golle
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=5765A4F9.3050107@nod.at \
--to=richard@nod.at \
--cc=computersforpeace@gmail.com \
--cc=dedekind1@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dwmw2@infradead.org \
--cc=hauke@hauke-m.de \
--cc=linux-mtd@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
/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.