From: David Craven <david@craven.ch>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH 7/7] gnu: Enable CONFIG_HOTPLUG_PCI.
Date: Thu, 2 Feb 2017 21:18:06 +0100 [thread overview]
Message-ID: <CAL1_imn4hky6JqNkmg_HOjZe8Bt+dfh67M2-JcTrPPE+7yBtpQ@mail.gmail.com> (raw)
In-Reply-To: <20170202202006.03597708@scratchpost.org>
> I don't think the firmware needs to be uploaded at all to the AR9285 device.
I don't understand:
1. free firmware - anyone can update the firmware
2. binary blob - the vendor can update the firmware
3. fixed at manufacturing time - no one can update the firmware
Option 1 is obviously superior to the other two. But how is option 3
better than option 2?
next prev parent reply other threads:[~2017-02-02 20:18 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-01 23:35 [PATCH 1/7] gnu: mutter: Update to HEAD David Craven
2017-02-01 23:35 ` [PATCH 2/7] gnu: Add git-crypt David Craven
2017-02-09 16:52 ` Ludovic Courtès
2017-02-01 23:35 ` [PATCH 3/7] gnu: Add replace-input procedure David Craven
2017-02-09 16:54 ` Ludovic Courtès
2017-02-10 11:31 ` David Craven
2017-02-01 23:35 ` [PATCH 4/7] gnu: Add appstream-glib David Craven
2017-02-09 16:55 ` Ludovic Courtès
2017-02-01 23:35 ` [PATCH 5/7] gnu: Add gnome-disk-utility David Craven
2017-02-05 5:53 ` Maxim Cournoyer
2017-02-09 16:57 ` Ludovic Courtès
2017-02-01 23:35 ` [PATCH 6/7] system: install: Add gptfdisk to installation os David Craven
2017-02-09 16:58 ` Ludovic Courtès
2017-02-01 23:35 ` [PATCH 7/7] gnu: Enable CONFIG_HOTPLUG_PCI David Craven
2017-02-02 0:39 ` David Craven
2017-02-02 15:53 ` David Craven
2017-02-02 17:07 ` David Craven
2017-02-02 19:20 ` Danny Milosavljevic
2017-02-02 20:18 ` David Craven [this message]
2017-02-02 20:41 ` Danny Milosavljevic
2017-02-02 21:50 ` David Craven
2017-02-03 2:54 ` David Craven
2017-02-03 17:45 ` Danny Milosavljevic
2017-02-09 17:02 ` Ludovic Courtès
2017-02-10 11:58 ` David Craven
2017-02-02 0:38 ` [PATCH 1/7] gnu: mutter: Update to HEAD David Craven
2017-02-09 17:00 ` Ludovic Courtès
2017-02-10 14:56 ` David Craven
2017-02-09 16:52 ` Ludovic Courtès
2017-02-09 16:57 ` David Craven
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAL1_imn4hky6JqNkmg_HOjZe8Bt+dfh67M2-JcTrPPE+7yBtpQ@mail.gmail.com \
--to=david@craven.ch \
--cc=dannym@scratchpost.org \
--cc=guix-devel@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).