public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Chris Moore <moore@free.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] Fwd: Debian platform firmware strategy?
Date: Wed, 02 Jul 2014 19:33:58 +0200	[thread overview]
Message-ID: <53B44286.7080805@free.fr> (raw)

Hi Paul,

I hope you don't mind my forwarding your message below to the U-Boot ML.
I think U-Boot ML subscribers may be interested in this discussion.
My apologies in advance if I am wrong.

Cheers,
Chris

-------- Message original --------
Sujet: 	Debian platform firmware strategy?
Date de renvoi : 	Wed, 2 Jul 2014 02:24:53 +0000 (UTC)
De (renvoi) : 	debian-arm at lists.debian.org
Date : 	Wed, 2 Jul 2014 10:24:31 +0800
De : 	Paul Wise <pabs@debian.org>
Pour : 	debian-arm at lists.debian.org



Hi all,

Platform firmware is an odd beast in the world of software. It is
mostly different per device. It is mostly proprietary and binary only.
When it isn't proprietary, the code is probably not merged upstream.
Sometimes it is very hard or impossible to update. It is very easy to
brick a device with a firmware update. Some devices are unbrickable
due to read-only secondary platform firmware chosen at boot time with
a button or via USB. Updating/replacing the platform firmware could
have unforeseen consequences (not being able to boot other OSes for
eg).

On x86 we ignore the platform firmware, don't package any libre
firmware (i.e. coreboot) and chainload our own bootloaders before
starting an OS.

On ARM the platform firmware is way less standardised but is often
u-boot. u-boot mainline is packaged and apparently has support for 6
armel devices and 13 armhf devices. Other devices ship with either a
locked proprietary bootloader (Android devices mostly), a forked
u-boot or some other FOSS bootloader. Sometimes the device ships with
older less capable versions of u-boot which complicate installation
(extra boot partitions required etc).

What should Debian's strategy/policy wrt platform firmware be?

Currently it seems to be just leave the platform firmware alone and
leave it up to the user to research if they can install libre
firmware.

I'm thinking we should promote using Free Software where possible and
packaged versions of that Free Software where possible. Due to the
possibility of unforeseeable circumstances, that promotion should
probably only consist of a default-to-no suggestion to replace
existing platform firmware if only intending to use Debian on the
device.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


-- 
To UNSUBSCRIBE, email to debian-arm-REQUEST at lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster at lists.debian.org
Archive: https://lists.debian.org/CAKTje6FuZbmzO1=p5+f4QP9yVNJh6DgGOBDCvf-Ecc5T2ZBedA at mail.gmail.com

             reply	other threads:[~2014-07-02 17:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-02 17:33 Chris Moore [this message]
2014-07-02 17:56 ` [U-Boot] Fwd: Debian platform firmware strategy? Stephen Warren

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=53B44286.7080805@free.fr \
    --to=moore@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