The ipw2200 driver (close relative of the ipw2100), has reached a point where it is relatively usable, and it would be advantageous if users could install Gentoo seamlessly using this hardware. Please look into including the driver on the next LiveCD.
This would require the driver be added, also... This driver is incompatable with the ipw2100 driver, so they block each other. Unfortunately, the bugzilla "blocking" really sets a dependency and it won't let me make a circular dependency... so just know that the both of these cannot be resolved unless something changes upstream to make them compatable.
Created attachment 40437 [details] hotplug generic path These solutions are all suboptimal. Why not simply reading the FIRMWARE_DIR from the hotplug-agent and installing the ipw-fw there? Hardcoded paths are crap any. I think the best solution to satisfy everyone and the whole discussion is to replace insinto /usr/lib/hotplug/firmware with insinto `egrep "FIRMWARE_DIR=" /etc/hotplug/firmware.agent|sed -e 's/FIRMWARE_DIR=//'` Or simply getting the attached ebuild.
Your proposed solution for placing the firmware does not work in an important case -- when users install ipw2200 and then upgrade hotplug. There are also issues when a package is being built. In any case, I would say it is more of a hack to examine the firmware.agent file for a line setting the FIRMWARE_DIR variable; although this works for the default configuration of the currently-used hotplug versions (for which the currently-implemented solution also works), if the structure of firmware.agent is changed either in a future version or by the user, the ebuild will no longer work. (For example, the user could define FIRMWARE_DIR in a separate file which is sourced, or firmware.agent could be replaced with a binary, etc.)
Technically it should be possible for net-wireless/ipw2100-1.0.2 to co-exist with net-wireless/ipw2200-0.18 since the shared ieee sub-system (the clashing modules) used in those two drivers are identical.
Couldn't the two drivers be combined, then?
My statement only goes for those specific versions of the two drivers. It was meant as a hint to a work-around to allow 2005.0 to include both drivers.
Other versions of the ipw2100/ipw2200 which will happily co-exists: ipw2100-1.0.5 and ipw2200-1.0.1
Neither of those versions are marked stable for x86 in the snapshot. Are they ready to go stable? If so, I will update the snapshot with those versions and include them both on the LiveCD.
Well, all I am waiting for is the 30 day ~ARCH period to be over...
The 30 days are over. What's the status? ipw2100-1.0.5: x86 -- that means, it is stable on x86 in the portage-snapshot for the 2005.0 LiveCD. And it is included on the LiveCD. ipw2200-1.0.1: ~amd64 x86 -- this is also stable in the portage-snapshot and included on the LiveCD, too.
This should be fixed in 2005.0
