Home | Docs | Forums | Lists | Bugs | Planet | Store | GMN | Get Gentoo!
Not eligible to see or edit group visibility for this bug.
View Bug Activity | Format For Printing | XML | Clone This Bug
I found a good (gentoo friendly) source for the AVM firmware files for the active ISDN controllers B1 ISA/PCI, C2, C4 and T1 ISA/PCI. You need them together with net-dialup/capi4k-utils to use the mentioned cards. So I made 4 ebuilds, one for every card. Reproducible: Always Steps to Reproduce:
Created an attachment (id=42805) [edit] capi-firmware-avm-b1-3.11.03.4.ebuild AVM B1 ISA/PCI firmware files for CAPI 2.0 prefered location: net-dialup/capi-firmware-avm-b1
Created an attachment (id=42806) [edit] capi-firmware-avm-c2-3.11.04.4.ebuild AVM C2 firmware files for CAPI 2.0 prefered location: net-dialup/capi-firmware-avm-c2
Created an attachment (id=42807) [edit] capi-firmware-avm-c4-3.11.04.4.ebuild AVM C4 firmware files for CAPI 2.0 prefered location: net-dialup/capi-firmware-avm-c4
Created an attachment (id=42808) [edit] capi-firmware-avm-t1-3.09.07.4.ebuild AVM T1 ISA/PCI firmware files for CAPI 2.0 prefered location: net-dialup/capi-firmware-avm-t1
They all only add a single file?
> They all only add a single file? yes. one or two files (depends on the card). This are FIRMWARE files, which are loaded into the active ISDN cards via 'capiinit' (see net-dialup/capi4k-tools). I have a AVM B1 PCI V3.0 and so I need the "b1.t4" firmware for Euro-ISDN (DSS1) which is included in 'capi-firmware-avm-b1-3.11.03.4'. You have to configure this in /etc/capi.conf.
I will include all firmware files in capi4k-utils.
ehhh, ok. If you think, this is the best... but be aware of the firmware versions somehow. If AVM releases new ones, they should be distinguishable and updated in time.
inserted in capi4k-utils-20041006-r1
right now it doubles the size of the sources for the benefit of some (i expect most people have a passive card where no firmware is needed.). And everyone must download all 4 firmware files for cards they don't own. other way: one (e.g firmware) or four (e.g t1, c2, c4, b1) useflags can avoid this.
issue moved to #71022