From: Rob Landley <rob@landley.net>
To: linux-embedded@vger.kernel.org
Subject: Re: [RFC PATCH 0/1] Add driver for bootstage stash
Date: Fri, 23 May 2025 14:43:57 -0500 [thread overview]
Message-ID: <5b8d51e8-92af-469d-9d05-253a63e31230@landley.net> (raw)
In-Reply-To: <473a062e4f939bc58a5c0e636569b826@giovanardi.dev>
On 5/23/25 02:34, Federico Giovanardi wrote:
> Hello,
>
> The note about the data format also was my initial thought, by just
> copying a C structure we might have issues as soon one party changes it,
> and they might not be perfectly aligned.
>
> To avoid inventing yet-another-data-format I've used msgpack in the past
> for that (the format https://github.com/msgpack/msgpack/blob/master/
> spec.md, not the library ); because the specs are so simple they can be
> implemented in a few lines, and it's something with a reference. But I
> don't have a lot of experience in upstreaming stuff on the kernel, so I
> don't know if it might cause someone to don't be happy. Anyway, I can
> contribute the implementation if needed.
I note that if it has an external build-time dependency, I will not only
never enable it, I will go to great lengths to _disable_ it. I maintain
a patch to build x86-64 without that ridiculous fourth ELF library, for
example:
https://landley.net/bin/mkroot/latest/linux-patches/0005-x86-64-elfcrap.patch
The traditional approach to exporting data was to have synthetic
filesystems like /sys and /blah produce human readable ascii output that
could be easily parsed, because unix is textual.
Ala "Write programs to handle text streams, because that is a universal
interface." from https://en.wikipedia.org/wiki/Unix_philosophy (quoting
Peter Salus's "a quarter century of unix" in 1994 which was itself
quoting... I think Doug McIlroy?
Rob
P.S. The whole digression into Plan 9 muddied the waters, not because
they backed off on it but because the original authors of unix doubled
down on their sequel project, and then unix copied things like the
concept of synthetic filesystems from that. The difference is Unix was
published freely in 1974 and Plan 9 was closed source proprietary until
2000, so the first changed the world and the second is a footnote must
people weren't aware existed until it had basically died, and then mined
it for ideas they could port to what they were using without ever
touching the incompatibly licensed code...
next prev parent reply other threads:[~2025-05-23 20:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 22:42 [RFC PATCH 0/1] Add driver for bootstage stash Francesco Valla
2025-05-22 22:42 ` [PATCH 1/1] drivers: misc: add " Francesco Valla
2025-05-23 6:29 ` Krzysztof Kozlowski
2025-05-23 19:34 ` Rob Landley
2025-05-24 6:16 ` Krzysztof Kozlowski
2025-05-23 19:43 ` Francesco Valla
2025-05-24 6:15 ` Krzysztof Kozlowski
2025-05-23 23:43 ` Bird, Tim
2025-05-24 7:18 ` kernel test robot
2025-05-23 7:04 ` [RFC PATCH 0/1] Add " Geert Uytterhoeven
2025-05-23 20:06 ` Francesco Valla
[not found] ` <PA4PR08MB604681FF6392B25A19926A11ED98A@PA4PR08MB6046.eurprd08.prod.outlook.com>
2025-05-23 7:34 ` Federico Giovanardi
2025-05-23 19:43 ` Rob Landley [this message]
2025-05-23 20:11 ` Francesco Valla
2025-05-24 0:07 ` Bird, Tim
2025-05-24 0:28 ` Bird, Tim
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=5b8d51e8-92af-469d-9d05-253a63e31230@landley.net \
--to=rob@landley.net \
--cc=linux-embedded@vger.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 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).