Re: [arch-general] [arch-dev-public] New core package: linux-firmware
On 05/19/2010 05:39 PM, Thomas Bächler wrote:
As a followup to a discussion on [arch-general] in the Linux 2.6.34 thread ([1] and others), I think we should do the following:
- Create a linux-firmware package from the linux-firmware.git tree. - Make that package conflict and replace all other firmware that it obsoletes: replaces=('kernel26-firmware' 'ar9170-fw' 'iwlwifi-1000-ucode' 'iwlwifi-3945-ucode' 'iwlwifi-4965-ucode' 'iwlwifi-5000-ucode' 'iwlwifi-5150-ucode' 'iwlwifi-6000-ucode' 'rt2870usb-fw' 'rt2x00-rt61-fw' 'rt2x00-rt71w-fw') All other firmware packages contain only files that are not part of linux-firmware. - Remove the firmware from the kernel26 PKGBUILD, only use the linux-firmware package instead
I'm putting a package with the according conflicts/replaces to testing. Please comment, test it thoroughly and give feedback.
[1] http://mailman.archlinux.org/pipermail/arch-general/2010-May/013329.html
Maybe this is a little premature, or altogether irrelevant, but now that we're reorganizing all of the firmware what can we expect in terms of its inclusion in the initcpio? Is there a direct relationship between modules and firmware so that just what's needed can be loaded automatically? Is it too much to just take it all with a 'firmware' hook?
Am 20.05.2010 00:30, schrieb Matthew Monaco:
Maybe this is a little premature, or altogether irrelevant, but now that we're reorganizing all of the firmware what can we expect in terms of its inclusion in the initcpio?
Is there a direct relationship between modules and firmware so that just what's needed can be loaded automatically? Is it too much to just take it all with a 'firmware' hook?
Required firmware is added to the initramfs automatically - at least the firmware files that are listed in 'modinfo' of the module in question. Beyond that, there is nothing we can do.
On 05/19/2010 06:40 PM, Thomas Bächler wrote:
Am 20.05.2010 00:30, schrieb Matthew Monaco:
Maybe this is a little premature, or altogether irrelevant, but now that we're reorganizing all of the firmware what can we expect in terms of its inclusion in the initcpio?
Is there a direct relationship between modules and firmware so that just what's needed can be loaded automatically? Is it too much to just take it all with a 'firmware' hook?
Required firmware is added to the initramfs automatically - at least the firmware files that are listed in 'modinfo' of the module in question. Beyond that, there is nothing we can do.
Does anyone know what the point of that radeon hook in the AUR is then? All it does is add the radeon module and include the "radeon" firmware files - which I see are listed by 'modinfo radeon' anyway.
Am 20.05.2010 00:49, schrieb Matthew Monaco:
Does anyone know what the point of that radeon hook in the AUR is then? All it does is add the radeon module and include the "radeon" firmware files - which I see are listed by 'modinfo radeon' anyway.
It has no point at all.
On 05/19/2010 07:38 PM, Thomas Bächler wrote:
Am 20.05.2010 00:49, schrieb Matthew Monaco:
Does anyone know what the point of that radeon hook in the AUR is then? All it does is add the radeon module and include the "radeon" firmware files - which I see are listed by 'modinfo radeon' anyway.
It has no point at all.
In any event, my system is running fine with linux-firmware. Thanks.
participants (2)
-
Matthew Monaco
-
Thomas Bächler