From: Grant Edwards <grant.b.edwards@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: u-boot@lists.denx.de, linux-arm-kernel@lists.infradead.org
Subject: Re: Sharing code between Linux and bootloader (U-boot) ?
Date: Fri, 20 May 2016 15:08:56 +0000 (UTC) [thread overview]
Message-ID: <nhn9a8$52b$1@ger.gmane.org> (raw)
In-Reply-To: 573F1F07.6040202@laposte.net
On 2016-05-20, Sebastian Frias <sf84@laposte.net> wrote:
> 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?
A little bit -- sort of. I've seen chunks of code that have been
copied from Linux to U-Boot, and chunks of code in Linux and U-Boot
that appear to have come from the same place at some silicon vendor or
other. And there are bits of code I've written that ended up in both
places.
But Linux and U-Boot don't share actual files, and any changes to the
"common" code has to be done twice.
--
Grant Edwards grant.b.edwards Yow! Are we THERE yet?
at
gmail.com
next prev parent reply other threads:[~2016-05-20 15:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-20 14:28 Sharing code between Linux and bootloader (U-boot) ? Sebastian Frias
2016-05-20 14:28 ` [U-Boot] " Sebastian Frias
2016-05-20 14:28 ` Sebastian Frias
2016-05-20 15:08 ` Grant Edwards [this message]
2016-05-21 1:41 ` [U-Boot] " Tom Rini
2016-05-21 1:41 ` Tom Rini
2016-05-21 1:41 ` Tom Rini
2016-05-23 13:22 ` Sebastian Frias
2016-05-23 13:22 ` Sebastian Frias
2016-05-23 13:22 ` Sebastian Frias
2016-05-30 11:35 ` Holger Schurig
2016-05-30 11:35 ` [U-Boot] " Holger Schurig
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='nhn9a8$52b$1@ger.gmane.org' \
--to=grant.b.edwards@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.