prism54-firmware was moved and has a newer version Changes: -newer version -new src_uri -new homepage -check kernel version to install right version (see http://wireless.kernel.org/en/users/Drivers/p54)
Created attachment 182316 [details] ebuild for prism54-firmware-2.7.0.0 is valid for <=linux-kernel-2.6.27
Created attachment 182317 [details] ebuild for prism54-firmware-2.13.1.0 is valid for =linux-kernel-2.6.28
Created attachment 182319 [details] ebuild for prism54-firmware-2.13.12.0 is valid for >=linux-kernel-2.6.29
just tested version 2.7.0.0 and my card requested for firmware "ils3886" I think the src_install() should modified this way: src_install() { insinto /lib/firmware/ newins ${DISTDIR}/${MY_PV} isl3886 newins ${DISTDIR}/${MY_PV} isl3890 } card is: 03:00.0 Network controller: Intersil Corporation ISL3890 [Prism GT/Prism Duette]/ISL3886 [Prism Javelin/Prism Xbow] (rev 01) Subsystem: Tekram Technology Co.,Ltd. ALLNET ALL0271 Wireless PCI Adapter Flags: bus master, medium devsel, latency 80, IRQ 11 Memory at 58000000 (32-bit, non-prefetchable) [size=8K] Capabilities: [dc] Power Management version 1
Created attachment 186775 [details] ebuild for prism54-firmware-2.7.0.0 I guess your are right! According to the p54 website http://wireless.kernel.org/en/users/Drivers/p54 this firmware should also work for ISL3877, ISL3880, ISL3890 and ISL3886. -> added these lines to the ebuild
My card (pcmcia) was: 02:00.0 Network controller: Intersil Corporation ISL3890 [Prism GT/Prism Duette]/ISL3886 [Prism Javelin/Prism Xbow] (rev 01) Subsystem: Tekram Technology Co.,Ltd. ALLNET ALL0271 Wireless PCI Adapter Flags: bus master, medium devsel, latency 80, IRQ 11 Memory at 44000000 (32-bit, non-prefetchable) [size=8K] Capabilities: <access denied> Kernel driver in use: prism54 Kernel modules: prism54 and it wants isl3890 !
ping @ mobile: How do you usually handle the install of the same file under different name? Symlinks? Btw, prism54/p54 are a lot more chips: In the ebuild, right now: -ISL3877, ISL3880, ISL3890 and ISL3886 (miniPCI) Not in the ebuild: -ISL3886 + net2280 (USB, 1st generation with net2280 usb<->pci bridge) -ISL3887 (USB, 2nd generation, native USB interface) -( STMicroelectronics' STLC4560 (SPI) - available in wireless-testing ) But all have different firmware versions! So how to make the ebuild version consistent? Split the ebuild? (into prism54, prism54usb, prism54usb2)
(In reply to comment #7) > > Split the ebuild? (into prism54, prism54usb, prism54usb2) > maybe adding one or more use flags (usb/pci) can keep the ebuild compact without the need of splitting.
(In reply to comment #8) > maybe adding one or more use flags (usb/pci) can keep the ebuild compact > without the need of splitting. That sounds good, but how to handle the different version in one ebuild? example for <linux-2.6.28: pci 2.7.0.0 usb 2.5.6.0 usb2 2.5.8.0 Versioning the ebuild with the kernel version is also not a good choice, one of the firmware version maybe change in the meanwhile.
I brought a new wireless stick, because wpa2 was not working with my prim54 card anyway. Reopen the bug at anytime... PS: When 2.6.29 is stable, we will again need only one ebuild.
New unified prism54-firmware in now in tree. Contains all the upstream suggested firmware versions for >=2.6.29 kernels
(In reply to comment #11) > New unified prism54-firmware in now in tree. Contains all the upstream > suggested firmware versions for >=2.6.29 kernels > just installed the latest version (2.13), plugged in my pcmcia card and still doesn't work, since it tries to load isl3890 prism54: request_firmware() failed for 'isl3890' and # qlist prism54 /lib/firmware/3826.arm /lib/firmware/isl3887usb /lib/firmware/isl3886usb /lib/firmware/isl3886pci am I missing something???
