From: Tom Rini <trini@konsulko.com>
To: Sebastian Frias <sf84@laposte.net>
Cc: u-boot@lists.denx.de, linux-arm-kernel@lists.infradead.org,
LKML <linux-kernel@vger.kernel.org>, Mason <slash.tmp@free.fr>
Subject: Re: [U-Boot] Sharing code between Linux and bootloader (U-boot) ?
Date: Fri, 20 May 2016 21:41:59 -0400 [thread overview]
Message-ID: <20160521014159.GK7650@bill-the-cat> (raw)
In-Reply-To: <573F1F07.6040202@laposte.net>
[-- Attachment #1: Type: text/plain, Size: 1207 bytes --]
On Fri, May 20, 2016 at 04:28:23PM +0200, Sebastian Frias wrote:
> 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?
So, in all cases, Linux is always the primary. In some cases in U-Boot
we port drivers over (NAND is a good example here). In other cases,
things are similar enough that it's having done it in one place it's
easy enough to do it again in the other.
--
Tom
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-05-21 1:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-20 14:28 Sebastian Frias
2016-05-20 15:08 ` Grant Edwards
2016-05-21 1:41 ` Tom Rini [this message]
2016-05-23 13:22 ` [U-Boot] " 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=20160521014159.GK7650@bill-the-cat \
--to=trini@konsulko.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sf84@laposte.net \
--cc=slash.tmp@free.fr \
--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
all inboxes | Powered by JetHome®