I have tested the at76c503a and thus atmel-firmware packages on a variety of x86 and x86_64 platforms, as I used it to install Gentoo on nearly a half-dozen machines. It works just fine. The only need for change is that there needs to be a message added to the end of the at76c503a package, stating that upon boot, you might need to unplug the USB wifi adapter from USB cable, then plug it in again. This is because the firmware is loaded by the driver, and thus something like: # rc-update add net.wlan0 default will not work, because (i'd have to assume) udev or whatever manages this has to be active/listening for it to be plugged in so it can load-in the firmware. It's important to mark this stable so support for it can be added into the LiveCDs -- because a Stage1/Stage2 install with these wifi adapters is currently impossible due to lack of drivers.
Made this bug block 109414 (request for support of at76c503a in liveCDs)
The reporter seems to be asking for this on both x86 and amd64. Reassigning to reflect this.
Going stable with this has a couple of issues: 1. upstream considers it beta 2. external kernel modules are likely to break with new kernel releases So in order to go stable we need to have someone actively taking care of take package so that person needs to report here. I know having this on the livecds would be nice so let's see what we can do. The best course of action is of course to get this included in the official kernel but that is an upstream issue.
Ehh... the main thing with a kernel module is to be sure to add kernel@gentoo.org to the CC of any bug regarding incompatibilities with newer kernels. This ensures that the kernel team is ware of any issues with the newer kernel before it goes stable. As for the original point of this bug, I could honestly care about stage1/stage2 installations, as they will be going away in the future. I do care, however, in having this support on the LiveCD.
> So in order to go stable we need to have someone actively taking care of take > package so that person needs to report here. I know having this on the livecds > would be nice so let's see what we can do. The best course of action is of > course to get this included in the official kernel but that is an upstream issue. I'm pretty well seasoned in using Gentoo -- but I'm hardcore newb on the development end. What all is involved in maintaining, say, the at76c503a / atmel-firmware packages? I'm willing to give it a shot if nobody else will step to the plate and bat.
(In reply to comment #4) > Ehh... the main thing with a kernel module is to be sure to add > kernel@gentoo.org to the CC of any bug regarding incompatibilities with newer > kernels. This ensures that the kernel team is ware of any issues with the newer > kernel before it goes stable. > I was thinking that it would be best if there was someone testing the module against the rc versions of vanilla-sources so the bugs are found as early as possible.
Well yes, that should happen, but that isn't our responsibility (unless asked) but instead the package maintainer's. An arch team is reponsible for KEYWORDS, the package maintainer is responsible for functionality.
x86 team: If any of you have the hardware to test this, please let us know on the bug, otherwise the mobile team will have to handle testing this for us.
I have access to one of these (Netgear MA101) - I would have to disagree with the original poster that they are fine. While I *would* like to see them included on a LiveCD, I cannot agree that they should be marked stable.
Ehh...
Perhaps when a more stable version has shipped frmo upstream...
Developers of this driver at berlios stopped their work. So you won't see any future releases from upstream. I have this card and I interested in maintaining this driver. I just apllied patch for this package to support gcc4 so I think if you have some problems with it feel free to email me I'll try to help. And I also think that this driver should be included into LiveCD maybe with some start script displaying warning that this dirver is experemental.
