From: Neil Armstrong <narmstrong@baylibre.com>
To: Peter Korsgaard <peter@korsgaard.com>
Cc: linux-amlogic@lists.infradead.org,
Andreas Fenkart <afenkart@gmail.com>,
krzysztof.michonski@digitalstrom.com
Subject: Re: amlogic mmc_partitions support
Date: Mon, 14 Jan 2019 15:46:19 +0100 [thread overview]
Message-ID: <1f584568-7071-141e-b551-f64bb7215608@baylibre.com> (raw)
In-Reply-To: <87ef9fxq5z.fsf@dell.be.48ers.dk>
Hi Peter,
On 14/01/2019 15:35, Peter Korsgaard wrote:
>>>>>> "Neil" == Neil Armstrong <narmstrong@baylibre.com> writes:
>
> > Hi Andreas,
> > On 14/01/2019 10:54, Andreas Fenkart wrote:
> >> Hi,
> >>
> >> What is a feasible way to port the vendor supplied
> >> drivers/amlogic/mmc/emmc_partitions.c into something that could be
> >> mainlined? My thought is to create a custom block/partition/amlogic.c
> >> driver. Would that have a chance to be included in mainline?
>
> > Basically, Amlogic uses the eMMC main partition as a MTD devices and uses a
> > custom DT partition scheme to export named MTD partitions to user-space.
>
> > They don't use any "standard" partitions schemes on the eMMC main HW partition.
>
> > Mainline will never support DT-defined MMC partitions, and will never support
> > a MTD indirection to a MMC HW partition either.
>
> > You can try to implement something similar using FUSE, but it won't be simple.
>
> Not knowing anything about the vendor driver, if this is just about
> splitting up a single eMMC partition in sub blocks and not about MTD,
> then this can be easily done with the dm-linear target of device mapper,
> E.G. something like:
>
> dmsetup create FOO --table "0 <size> linear /dev/mmcblk0 <offset>"
>
Indeed, it would help, thanks for the pointer.
Andreas, this should be done from user-space in an initramfs code right before
switching root to the legacy userspace, for example, nothing in the kernel will
be accepted to do that.
Neil
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2019-01-14 14:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-14 9:54 Andreas Fenkart
2019-01-14 10:00 ` Neil Armstrong
2019-01-14 14:35 ` Peter Korsgaard
2019-01-14 14:46 ` Neil Armstrong [this message]
2019-01-14 14:42 ` Andreas Fenkart
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=1f584568-7071-141e-b551-f64bb7215608@baylibre.com \
--to=narmstrong@baylibre.com \
--cc=afenkart@gmail.com \
--cc=krzysztof.michonski@digitalstrom.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=peter@korsgaard.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
all inboxes | Powered by JetHome®