Skip to contentSkip to conversation

RFC: i386: kill !4KSTACKS

DISCUSSION Ian Kumlien 2 participants 2 messages Jun 8, 2005

lore
Share & tools
lore
#0 lore raw
Quoted 3 lines

Number of folks using ndiswrapper for acx100/acx111 while acx team needs help on native driver debugging worries me.

two things:
1, Broadcom chipsets lack any kind of driver.
2, acx100/111 claim that the firm ware is 'easy to find this is a ...
lie... F.ex. d-links drivers come with the drivers embedded in some file, i was unable to extract it for my neighbur and ended up using ndiswrapper. There was no choise.

Thus your statement is premature.

Signature · 1 line
Ian Kumlien <pomac () vapor ! com> -- http://pomac.netswarm.net
#1 lore raw
Quoted 4 lines · Ian Kumlien
Quoted 3 lines

Number of folks using ndiswrapper for acx100/acx111 while acx team needs help on native driver debugging worries me.

Quoted 8 lines

two things:
1, Broadcom chipsets lack any kind of driver.
2, acx100/111 claim that the firm ware is 'easy to find this is a ...
lie... F.ex. d-links drivers come with the drivers embedded in some file, i was unable to extract it for my neighbur and ended up using ndiswrapper. There was no choise.

Thus your statement is premature.

acx driver would not improve if few people will use it.

Caring for ndiswrapper needs helps closed source binary drivers, thus harms open source driver development.

Re firmware files: I've collected many at
http://195.66.192.167/linux/acx100/acx1xx.htm
--
vda