On Sunday, 28 September 2008 at 09:24, Hans de Goede wrote: > Hi All, > > After numerous attempts we (Thorsten, Xavier and I) have failed to get in > touch which Matthias to involve him in making a decision about which > packaging method to use for kernel modules in rpmfusion. > > As we really need to move forward now with rpmfusion to have everything > ready for F-10, I've proposed to Thorsten, Xavier to make a decision now > without Matthias, to which they have agreed. > > So the 3 of us have made the decision that kmods and akmod will be the way > to package kernel modules within rpmfusion. > > Thorsten will begin building all kmod's from livna in rpmfusion today. If > there are any out of tree drivers which you want to see packaged in > rpmfusion now you know what to do :) We sure do: https://bugzilla.rpmfusion.org/show_bug.cgi?id=52 > Note that if you're interested in Free out of tree drivers, it would be > even better to spend time on getting them in to the official upstream > kernel, I can help with that if you want to spend time on that. I probably would, but I'm not sure if I can find the time to maintain it after it gets there.

On 28.09.2008 09:24, Hans de Goede wrote: > > Thorsten will begin building all kmod's from livna in rpmfusion today. Didn't get around to it. Some work for day job, some other stuff for RPM Fusion, a little bit real life and building kmods for livna consumed all the time... I'll start with it tomorrow (hopefully).

CU knurd

Not that it matters much, but I'd prefer if we could keep madwifi for a little while longer if possible without to much hassle. But yeah, if ath5k really does all the major things the users need then it might be time to drop madwifi.

On Mon, 2008-09-29 at 22:18 +0300, Jonathan Dieter wrote: > On Mon, 2008-09-29 at 20:42 +0200, Thorsten Leemhuis wrote: > > Not that it matters much, but I'd prefer if we could keep madwifi for a > > little while longer if possible without to much hassle. > > > > But yeah, if ath5k really does all the major things the users need then > > it might be time to drop madwifi. > > FWIW, does ath5k support the EeePC 701's wifi chip? A version of > madwifi that does is in livna-testing. iirc, that's the same chip that is in the Acer Aspire One (an AR2425), and yes, rawhide ath5k does support it just fine.

On Mon, 2008-09-29 at 15:24 -0400, Jarod Wilson wrote: > On Mon, 2008-09-29 at 22:18 +0300, Jonathan Dieter wrote: > > On Mon, 2008-09-29 at 20:42 +0200, Thorsten Leemhuis wrote: > > > Not that it matters much, but I'd prefer if we could keep madwifi for a > > > little while longer if possible without to much hassle. > > > > > > But yeah, if ath5k really does all the major things the users need then > > > it might be time to drop madwifi. > > > > FWIW, does ath5k support the EeePC 701's wifi chip? A version of > > madwifi that does is in livna-testing. > > iirc, that's the same chip that is in the Acer Aspire One (an AR2425), > and yes, rawhide ath5k does support it just fine. Excellent. Then I'm all for dropping madwifi (for whatever miniscule amount it's worth).