From: Hannes Petermaier <hannes@petermaier.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Add support for offset of a filesystem within a block-device
Date: Wed, 12 Mar 2014 21:51:21 +0100 [thread overview]
Message-ID: <5320C8C9.40907@petermaier.org> (raw)
In-Reply-To: <20140312202710.GI16805@bill-the-cat>
On 2014-03-12 21:27, Tom Rini wrote:
>>
>> Hi Tom,
>> You're right. SPL could be marked as protected.
>> But how to deal here with u-boot itself ? its address is within a
>> possible area of a partition.
>> Fdisk doesn't know about that :-(
>> We also cannot protect #0 where partition-table is stored, because
>> user should able to create/delete partitions.
> Block size then wouldn't let 0->128K be writable, 128->whatever
> read-only, whatever->end writable ?
>
>> So - maybe be a solution, but unfortunately not for me :-(
>> Today we give to our end-users up to 4 partitiions, exact that what
>> VxWorks can support - so i will be hard to have a 5th one ...
> Well, I guess there's two ways to look at this, either just
> documentation or seeing how hard it would be to make VxWorks behave like
> other OSes and let partition 1 be wherever it says it is, or some
> combination of both.
>
> I do appreciate you posting the code as it may be useful to others but
> at least right now, barring an outcry of "oh wait, I need this too!" I'm
> inclined to mark this as RFC in patchwork. Thanks again!
>
Ok Tom, we can do so ... please mark it for now as RFC.
Maybe in the future other people say "i like this too ..." and we can
apply this feature to the mainline code.
Until this day comes, "block-device offset within flash" will be my
personal "nursing-case" and i have to patch it into my build.
many thanks for your time and best regards,
Hannes
prev parent reply other threads:[~2014-03-12 20:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-06 13:30 [U-Boot] [PATCH] Add support for offset of a filesystem within a block-device Hannes Petermaier
2014-03-12 16:08 ` Tom Rini
2014-03-12 17:19 ` Hannes Petermaier
2014-03-12 19:00 ` Tom Rini
2014-03-12 19:17 ` Hannes Petermaier
2014-03-12 19:33 ` Tom Rini
2014-03-12 20:14 ` Hannes Petermaier
2014-03-12 20:27 ` Tom Rini
2014-03-12 20:51 ` Hannes Petermaier [this message]
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=5320C8C9.40907@petermaier.org \
--to=hannes@petermaier.org \
--cc=u-boot@lists.denx.de \
/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