At least I have tried to re-open the bug but launchpad won't let me put linux-source-2.6.24 as the affected package and reverts to linux only....
A fix has been released as detailed by me in the bug comments; all that is required is the correct and specific product ID information to be put into the hostap_cs source code.
Quote:
"So from this I added in the kernel source drivers/net/wireless/hostap/hostap_cs.c at line 861 this:
This fixes the original reporter's problem and mine because we both have the same card. The patch above is specific to that card. Unfortunately, if this patch is applied, users of this exact card will need to blacklist orinoco_cs because the orinoco source code contains a generic entry for manf_id: 0x0156 card_id: 0x0002 which is the same for the card in question. It seems that some of the cards identified by these ids may not all be prism2 based cards like mine.
It would be helpful to have this fixed upstream so that users of this card have the advantage of being able to use hostap drivers and the prism2 wireless access point facility.
Do I report to the maintainer of the hostap code directly? Also, should I start a new bug that is specifically titled "Missing device product IDs in hostap driver" like in Bug #97172?
At least I have tried to re-open the bug but launchpad won't let me put linux-source-2.6.24 as the affected package and reverts to linux only....
A fix has been released as detailed by me in the bug comments; all that is required is the correct and specific product ID information to be put into the hostap_cs source code.
Quote: net/wireless/ hostap/ hostap_ cs.c at line 861 this:
"So from this I added in the kernel source drivers/
PCMCIA_ DEVICE_ PROD_ID123(
"Wireless LAN", "11Mbps PC Card", "Version 01.02",
0x4b8870ff, 0x70e946d1, 0x4b74baa0),
in between the other wireless card definitions."
This fixes the original reporter's problem and mine because we both have the same card. The patch above is specific to that card. Unfortunately, if this patch is applied, users of this exact card will need to blacklist orinoco_cs because the orinoco source code contains a generic entry for manf_id: 0x0156 card_id: 0x0002 which is the same for the card in question. It seems that some of the cards identified by these ids may not all be prism2 based cards like mine.
It would be helpful to have this fixed upstream so that users of this card have the advantage of being able to use hostap drivers and the prism2 wireless access point facility.
Do I report to the maintainer of the hostap code directly? Also, should I start a new bug that is specifically titled "Missing device product IDs in hostap driver" like in Bug #97172?