public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sergei Trofimovich <slyfox@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: ssuominen@gentoo.org
Subject: RFC: install linux-firmware with kernel sources (was Re: [gentoo-dev] Lastrite: Firmware cleanup, part #1)
Date: Sun, 10 Feb 2013 17:46:34 +0300	[thread overview]
Message-ID: <20130210174634.77631769@sf> (raw)
In-Reply-To: <5117560B.3090709@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1206 bytes --]

On Sun, 10 Feb 2013 10:10:51 +0200
Samuli Suominen <ssuominen@gentoo.org> wrote:

> # Samuli Suominen <ssuominen@gentoo.org> (10 Feb 2013)
> # The firmware cleanup, part #1. Can be unmasked after
> # cleaning up the package if it's still needed.
> # Some of these install to wrong directory, /lib64/firmware
> # as opposed to correct /lib/firmware
> # Some of these don't have maintainer
> # Some of these are replaced by the firmware from the
> # linux-firmware package:
> # emerge -av linux-firmware
> # If you still have a reason to keep the package, please
> # let us know by filing a bug report.
> net-wireless/ar9271-firmware

I didn't know linux-firmware exists at all when added that
to the tree (SRC_URI=http://linuxwireless.org).
Fine by me.

The source of confusion was non-working device by default.
Maybe 'IUSE=+firmware; RDEPEND="firmware? ( sys-kernel/linux-firmware )"'
for virtual/linux-sources would help user experience a bit.

Sometimes firmware loader does not even write fw file
it expects to be present on FS in dmesg (like certain broadcom drivers)
thus it's nontrivial for user to figure out needed package to be installed.

Thanks!

-- 

  Sergei

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2013-02-10 14:47 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-10  8:10 [gentoo-dev] Lastrite: Firmware cleanup, part #1 Samuli Suominen
2013-02-10 12:59 ` Samuli Suominen
2013-02-10 14:46 ` Sergei Trofimovich [this message]
2013-02-10 15:05   ` RFC: install linux-firmware with kernel sources (was Re: [gentoo-dev] Lastrite: Firmware cleanup, part #1) Pacho Ramos
2013-02-10 16:41     ` Maxim Kammerer
2013-02-10 21:06       ` Bruno
2013-02-10 22:49         ` Alec Warner
2013-02-12 19:39           ` Christopher Head
2013-02-12 20:43             ` [gentoo-dev] Re: RFC: install linux-firmware with kernel sources (was " Duncan
2013-02-12 23:03               ` Michael Weber
2013-02-13 10:31             ` RFC: install linux-firmware with kernel sources (was Re: [gentoo-dev] " Chí-Thanh Christopher Nguyễn
2013-02-10 16:49     ` Dirkjan Ochtman
2013-02-10 16:53       ` Maxim Kammerer
2013-02-10 16:54       ` Fabio Erculiani
2013-02-10 19:43         ` Dirkjan Ochtman
2013-02-12 19:38           ` Christopher Head
2013-02-12 19:43             ` Fabio Erculiani
2013-02-12 19:47               ` Pacho Ramos
2013-02-12 20:00                 ` Fabio Erculiani
2013-02-12 20:51             ` [gentoo-dev] Re: RFC: install linux-firmware with kernel sources (was " Duncan
2013-02-12 22:30               ` Christopher Head
2013-02-16  6:14                 ` Rick "Zero_Chaos" Farina
2013-02-16 15:29                   ` Maxim Kammerer
2013-02-17  5:08                     ` Rick "Zero_Chaos" Farina
2013-02-17 10:26                       ` Pacho Ramos
2013-02-17 16:39                       ` Maxim Kammerer
2013-02-17 16:54                     ` Chí-Thanh Christopher Nguyễn
2013-02-17 16:55                   ` Chí-Thanh Christopher Nguyễn
2013-02-10 20:44         ` RFC: install linux-firmware with kernel sources (was Re: [gentoo-dev] " Rick "Zero_Chaos" Farina
2013-02-13 13:38   ` Chí-Thanh Christopher Nguyễn
2013-02-13 14:45     ` Diego Elio Pettenò
2013-02-13 14:50       ` Chí-Thanh Christopher Nguyễn
2013-02-13 14:53         ` Diego Elio Pettenò
2013-02-13 17:33           ` Peter Stuge
2013-02-13 17:35             ` Diego Elio Pettenò
2013-02-13 17:50               ` Peter Stuge
2013-02-13 19:12                 ` Chí-Thanh Christopher Nguyễn
2013-02-14  6:37                 ` Graham Murray
2013-02-14  7:26                   ` Michael Weber
2013-02-14  9:32                     ` Samuli Suominen
2013-02-10 15:55 ` [gentoo-dev] Lastrite: Firmware cleanup, part #1 Maxim Kammerer
2013-02-10 20:41   ` Rick "Zero_Chaos" Farina
2013-02-10 21:45     ` Maxim Kammerer
2013-02-10 23:12       ` Douglas Freed
2013-02-11  0:15         ` Maxim Kammerer
2013-02-10 23:52       ` Rick "Zero_Chaos" Farina
2013-02-11  0:18         ` Maxim Kammerer
2013-02-11  0:42           ` Rick "Zero_Chaos" Farina
2013-02-13 13:39       ` Chí-Thanh Christopher Nguyễn
2013-02-13 13:39     ` Chí-Thanh Christopher Nguyễn
2013-02-13 13:51       ` Diego Elio Pettenò
2013-02-13 14:54       ` Alec Warner
2013-02-14 22:29       ` Rick "Zero_Chaos" Farina
2013-02-10 16:20 ` Rick "Zero_Chaos" Farina
2013-02-13 13:08   ` Chí-Thanh Christopher Nguyễn
2013-02-14 22:27     ` Rick "Zero_Chaos" Farina
2013-02-14 22:39       ` Samuli Suominen
2013-02-16  6:08         ` Rick "Zero_Chaos" Farina
2013-02-16 13:52           ` Diego Elio Pettenò
2013-02-16 19:18             ` Alec Warner
2013-02-16 19:28               ` Diego Elio Pettenò
2013-02-16 19:31                 ` Peter Stuge
2013-02-16 21:01                   ` Markos Chandras

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=20130210174634.77631769@sf \
    --to=slyfox@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=ssuominen@gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox