Bugzilla Bug 109844

Hi

As the 0.2.0 and 0.2.4 versions of the acx100/111 driver are pretty much out of
date as a lot of very serious bugs have been fixed, and the naming of the
firmware has been changed. The new naming scheme also means that the md5sum for
fw.tar.bz2, that is also wanted by acx100-0.2.4, has changed, preventing that
version being installed straight from portage.

The actual ebuild is nearly identical to the 0.2.4 one, only minor changes and
fixes.

Also, it is kind of funny that the 0.2.0 is marked stable even though it is the
least stable version.

Mki

Created an attachment (id=71033) [edit]
acx100-0.3.14.ebuild

http://dev.gentoo.org/~genstef/files/overlay/acx100-0.3.14.ebuild

Can you please try if my new ebuild works for you?
A friend of mine had problems with firmware loading .. I have no acx100 chip
myself :(

Reports appreciated.

Stefan, your ebuild worked fine for me (had the fw.tar.bz2 already in distfiles
though). Firmware distribution seems to be quite a problem right now.. thanks to TI.

works fine for me, too. also downloading the firmware works. But I don't
understand the naming scheme (0.3.14 vs 20051018) ;-)

I'm not sure about these lines:
creating /proc entry driver/acx_wlan0
creating /proc entry driver/acx_wlan0_diag
creating /proc entry driver/acx_wlan0_eeprom
creating /proc entry driver/acx_wlan0_phy

But since "ls /proc/driver/" gives me:
acx_wlan0  acx_wlan0_diag  acx_wlan0_eeprom  acx_wlan0_phy

it looks fine and seems to work.

(In reply to comment #4)
> works fine for me, too. also downloading the firmware works. But I don't
> understand the naming scheme (0.3.14 vs 20051018) ;-)

The versions that are being used (0.3.14, etc) are internal for us to track what
actual snapshot a person is using.  Any time anything other than a bugfix is
incorporated, it's incremented.  For those that are doing up these ebuilds, it's
safe to add ~amd64 as I've been using this on amd64 with 2-3 week uptimes
(reboots due to me, not it).  Also for those interested, Master mode DOES work,
but wep may be problematic for some due to certain drivers setting the wep bit
too soon, and this driver requires the wep bit to not be set until the
transmissions are encrypted.

yo!

it seems that acx-20051118.tar.bz2  works fine with me and the 2.6.14-gentoo-r2
of kernel. :)
no need anymore to inject the module in the kernel nor the start's script of
acx100-0.2.0pre8_plus_fixes_57 to make run my card...
:)

thanks.

Version bumped, thank you all