From: Sebastian Frias <sf84@laposte.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] Sharing code between Linux and bootloader (U-boot) ?
Date: Fri, 20 May 2016 16:28:23 +0200 [thread overview]
Message-ID: <573F1F07.6040202@laposte.net> (raw)
Hi,
Some bootloaders (like U-boot) support several HW devices: serial, network, NAND, USB, etc. most of which are also supported by Linux.
So the question is: is code shared? I mean, I understand that the drivers need to talk to the appropriate API, and such API could be different between Linux and U-boot.
But putting that aside, would it be naive to imagine that some "core" functionality could be shared? Or would that part be so small it is not worth the effort?
Since many companies use both, U-boot and Linux, I would figure they try their best to optimize engineering resources and share code, right?
In that case, I also wonder how do they share DT descriptions that right now are being stored in the Linux kernel tree.
We'd like to share code/DT for obvious reasons, what would you guys suggest?
Best regards,
Sebastian
next reply other threads:[~2016-05-20 14:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-20 14:28 Sebastian Frias [this message]
2016-05-21 1:41 ` [U-Boot] Sharing code between Linux and bootloader (U-boot) ? Tom Rini
2016-05-23 13:22 ` Sebastian Frias
2016-05-30 11:35 ` Holger Schurig
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=573F1F07.6040202@laposte.net \
--to=sf84@laposte.net \
--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