Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Maciej Borzecki <maciej.borzecki@open-rnd.pl>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: Tom Zanussi <tom.zanussi@linux.intel.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] wic: allow creation of partitions not in table
Date: Thu, 5 Feb 2015 10:02:26 +0100	[thread overview]
Message-ID: <20150205090226.GC3628@localhost.localdomain> (raw)
In-Reply-To: <1423090996-14918-1-git-send-email-alexandre.belloni@free-electrons.com>

On 02/05 00:03, Alexandre Belloni wrote:
> For some architectures it is necessary to reserve space on disk without
> it being present in the partition table.
>
> For example, u-boot on i.mx is placed at an offset of 1kB on the sdcard.
> While it would be possible to create a partition at that offset and
> place u-boot there, it would then be necessary to update the default
> u-boot environment to use partition 2 on the mmc instead of partition
> 1.

I'm wondering if reusing parition here is the right choice. How about
making this a separate command, since the operation of putting some
binary data at a particular location within the image sounds like
something very specific to wic.

Could name it 'raw-copy', with options --source and --offset. The
command would be applied after image assembly is complete. Offset could
be expressed in bytes by default (plus k/M/G suffix). Source could
either be a 'bootloader', that implies a default bootloader for this
target, or a name of a file from $DEPLOY_DIR_IMAGE.

Assuming IMAGE_BOOTLOADER='u-boot.img' is set somewhere, the kickstart
could look like:

part / --source rootfs --ondisk mmcblk --fstype=ext4 --label root --align 4 --start 1M
raw-copy --source bootloader --offset 1kB


If at some point we extend the bootloader command to include the name of
bootloader file:

part / --source rootfs --ondisk mmcblk --fstype=ext4 --label root --align 4 --start 1M
bootloader --name u-boot.img
raw-copy --source bootloader --offset 1kB

What do you think?

--
Maciej Borzęcki
Senior Software Developer at Open-RnD Sp. z o.o., Poland
www.open-rnd.pl
mobile: +48 889 117 365, fax: +48 42 657 9079


Niniejsza wiadomość wraz z załącznikami może
zawierać chronione prawem lub poufne informacje i została
wysłana wyłącznie do wiadomości i użytku osób, do których
została zaadresowana. Jeśli wiadomość została otrzymana
przypadkowo zabrania się jej kopiowania lub rozsyłania do osób
trzecich. W takim przypadku uprasza się o natychmiastowe
zniszczenie wiadomości oraz poinformowanie nadawcy o
zaistniałej sytuacji za pomocą wiadomości zwrotnej.
Dziękujemy.

This message, including any attachments hereto,
may contain privileged or confidential information and is sent
solely for the attention and use of the intended addressee(s).
If you are not an intended addressee, you may neither use this
message nor copy or deliver it to anyone. In such case, you
should immediately destroy this message and kindly notify the
sender by reply email. Thank you.


  reply	other threads:[~2015-02-05  9:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-04 23:03 [PATCH] wic: allow creation of partitions not in table Alexandre Belloni
2015-02-05  9:02 ` Maciej Borzecki [this message]
2015-02-05 10:27   ` Alexandre Belloni
2015-02-05 11:18     ` Maciej Borzecki
2015-02-05 17:39 ` Alexandre Belloni

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=20150205090226.GC3628@localhost.localdomain \
    --to=maciej.borzecki@open-rnd.pl \
    --cc=alexandre.belloni@free-electrons.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=tom.zanussi@linux.intel.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