Bug 610070 - RFE: Keep staging driver source in the kernel development package (or as a separate package)
RFE: Keep staging driver source in the kernel development package (or as a se...
Status: CLOSED UPSTREAM
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
rawhide
All Linux
low Severity low
: ---
: ---
Assigned To: Kernel Maintainer List
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-07-01 09:54 EDT by Horst H. von Brand
Modified: 2010-07-02 22:23 EDT (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-07-02 22:23:23 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Horst H. von Brand 2010-07-01 09:54:22 EDT
Description of problem:
I have a machine that uses an out of tree driver (currently rtl8192se_linux_2.6.0017.0507.2010 from Realtek). I believe there is a driver in staging for this WiFi card, but it is just easier for me to get the Realtek driver than to futz around finding the right kernel tree's staging driver and patch it into the kernel-devel package's source.

I'd prefer using the "not so official" driver from the kernel folks if possible. I very much understand Fedora's reluctance to ship staging drivers in binary, but if they are shipped in source (with suitable dire warnings on possible baby-eating, pet molesting and CPU meltdowns) they would presumably be exposed to wider testing/looking at without too much fallout.

Version-Release number of selected component (if applicable):
kernel-devel-2.6.35-0.15.rc3.git3.fc14.x86_64

How reproducible:
Always

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Dave Jones 2010-07-02 22:23:23 EDT
just like everything most things in staging, this driver is a mess, with it's own private ieee80211 layer, and assorted other wrong-doing.

if it ever makes progress to being a real driver upstream, we'll enable it of course, but in its current form, it's not going to happen.

Note You need to log in before you can comment on or make changes to this bug.