lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <nhn9a8$52b$1@ger.gmane.org>
Date:	Fri, 20 May 2016 15:08:56 +0000 (UTC)
From:	Grant Edwards <grant.b.edwards@...il.com>
To:	linux-kernel@...r.kernel.org
Cc:	u-boot@...ts.denx.de, linux-arm-kernel@...ts.infradead.org
Subject: Re: Sharing code between Linux and bootloader (U-boot) ?

On 2016-05-20, Sebastian Frias <sf84@...oste.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            

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ