Attached is an updated ebuild for rt2x00 CVS (-9999). Changes: - Added rt61pci and rt73usb modules - Added check for FW_LOADER which appears to be required to load the modules
Created attachment 86133 [details] rt2x00-9999.ebuild
Created attachment 86134 [details] rt2x00-9999 emerge log Not sure whether to file this seperately or not, but there's a bug in the rt2x00-9999 ebuild (it does also occur with the attached ebuild) that's already in portage where to get the ebuild to succeed, you need to run: emerge rt2x00 FEATURES="keepwork keeptemp noclean" emerge rt2x00 Otherwise it fails with the error: cp: cannot stat `ieee80211/.tmp_versions/*.mod': No such file or directory (see attached build log for full output) It looks to me like it's trying to do that copy too early, but I haven't any experiance with the CVS and Kernel module eclasses, and I'm in the middle of exams atm so don't have much free time to try and trace it myself right now.
Also, I'm not sure what the keywording policy is for CVS ebuilds, but this appears to work fine (it compiles and loads atleast) on amd64.
A small note. For some models these drivers don't work "out of the box". They need firmware, which can be downloaded from http://www.ralinktech.com/supp-1.htm and should be placed in /lib/firmware. If it isn't present, they silently output an error to dmesg. IMO it might be a good idea to mention something about this during post-install. Probably the best thing to do would be to point the users to read the README file installed into /usr/share/doc/rt2x00-9999/README.gz which will hopefully always be up to date
Created attachment 86166 [details] Updated rt2x00-9999.ebuild This updated ebuild solves the problem that occurs on systems running 2 or more makes at once. It simply changes: BUILD_PARAMS="KERNDIR=${KV_DIR} KERNOUT=${KV_OUT_DIR}" to: BUILD_PARAMS="-j1 KERNDIR=${KV_DIR} KERNOUT=${KV_OUT_DIR}" I also took the opportunity to blank the CVS header line.
Created attachment 86167 [details] rt2x00-cvs-9999.ebuild I suspect this one will never see portage, but for anyone who wants it, this ebuild uses the daily CVS snapshot tarball. It's useful when they're not sync'ing with the SF repository for whatever reason. I does include a slightly dirty hack to resolve the problem that the name of the directory inside the tarball changes. I also wasn't sure what to name it so created it as a seperate package.
The cvs ebuild has been updated for rt63, rt71 and the fwloader kernel config option. Upstream CVS has been patched for parallel makes, so there's no need to force -j1.
Created attachment 86556 [details] Updated rt2x00-cvs-9999.ebuild Changes: o Removed the -j1 build param, as the projects Makefiles have been fixed. o Forced the debug build target because this is experimental stuff: if you try this, you'll need the debug info. :)
