Bug 426186
Summary: | MadWifi doesn't work with AR5418 on Fedora kernel | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jeff Cook <cookiecaper> |
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
Status: | CLOSED CANTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | low | ||
Version: | 8 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-12-19 14:45:41 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jeff Cook
2007-12-19 02:46:46 UTC
Sorry, can't support madwifi in Fedora... It's really not being able to support MadWifi? Wouldn't this kind of issue expose something a little deeper that may impair other projects? No one's asking you to distribute MadWifi, but fixing a kernel build error manifested in an incompatibly licensed program surely doesn't amount to supporting or endorsing the thing, right? I hate to patronize, but that response seems like a copout to me. I really do what I can to love Fedora, it has a lot of appeal to me ... but if this is how Red Hat chooses to conduct business, I won't bother with it anymore and I feel that that'd be a shame. I'm not really sure what you expect me to do. Perhaps if you could point to a specific problem (or a specific patch that fixed a non-descript problem) we could evaluate it -- of course if there was a specific problem with the kernel it should be handled upstream anyway. That way it would filter down to Fedora, Ubuntu, and all the other distros. But, I digress... All I see is that there was a lot of talk about which SVN version of madwifi worked or didn't, then someone updated their Ubuntu kernel and things magically worked. It also seemed that the older madwifi versions were working with the older Ubuntu kernel, so that doesn't really identify which one really had a problem. Anyway, we do our best to support ath5k here. I hope their reverse engineering folks (also part of the overal madwifi team BTW) get to your device soon -- really, I do. In the meantime, I just don't have the bandwidth to chase down problems in madwifi. I'm sorry. No problem. Thank you for the prompt and polite response. I'll see if I can find something more specific. : ) |