I recently submitted a bug that complained of the missing ipw2200 ebuild, however I learned quickly afterwards that it was not functional as of version 0.2. However, yesterday version 0.3 of this driver was released. This new release is functional. It associates itself with an AP and is able to send and receive unencrypted data. In fact, I'm using it to submit this right now. I am attaching a functional ebuild. It is not very different from the ipw2100 ebuild because they use the same Makefile and structure. Reproducible: Always Steps to Reproduce: 1. 2. 3. Please visit http://ipw2200.sourceforge.net for information on this driver.
Created attachment 37392 [details] Proposed new ebuild for ipw2200
Created attachment 37399 [details] New ebuild Here's the version i worked up yesterday. I'll eventually get to comparing to yours, but first, re-attach yours at plain text, not octet-stream. (: I don't have hardware to test on, but from what i hear, this is still flaky for some, and has no WEP. I'd like to hold off for one more release at least to let this settle, but this bug can be a good reference point from now on.
Created attachment 37400 [details] Ebuild for ipw2200 0.3 (fixed MIME)
I re-attached the ebuild. Sorry, I thought auto MIME would work. Two things I see wrong with your ebuild, is the LICENSE var should be updated for ipw2200-fw, and AC4 crypto is not required to compile the driver, so I removed that block from mine. The DEPEND statement in yours is a good addition though. I've done some testing on this driver and card, and although it does not support WEP, it's fairly robust. I haven't had any issues as of yet. I'll happily volunteer to assist in the maintenance of this package if that helps.
I'm not in the mobile herd, but I will take this one on. I've written an ebuild for this as well, based on the ipw2100 ebuild, but I will take a look at all the ones posted here. Expect it in CVS in a few hours.
Package added to CVS.
