Bug 230731

Summary: Request d80211 headers in kernel-headers
Product: [Fedora] Fedora Reporter: Nicolas Chauvet (kwizart) <kwizart>
Component: kernelAssignee: John W. Linville <linville>
Status: CLOSED WONTFIX QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: davej, wtogami
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-07-26 14:09:09 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 Nicolas Chauvet (kwizart) 2007-03-02 15:30:57 UTC
Description of problem:When trying to compile hostapd with enabled d80211 stack
originally developed from devicescape, it need to uses d80211 headers that are
not relative to a kernel varriant...

Version-Release number of selected component (if applicable): 2.6.21rc1
This is applicable to 
How reproducible:


Steps to Reproduce:
1.Build user space tools that need to find headers in
%{_includir}/something_for_d80211 (example hostapd, but that may be applicable
also for wpa_supplicant)
2.BR kernel-headers
3
  
Actual results:
It do not find headers to use d80211 based wireless devices.

Expected results:
It should just compile fine...

Additional info: see Review request to hostapd #230449

Comment 1 Nicolas Chauvet (kwizart) 2007-03-02 15:38:20 UTC
that was %{_includedir}/... sorry for the typo
There is no *80211* files that are relative to devicescape 80211 stack with
kernel-headers bundled with fc7 t2

Comment 2 John W. Linville 2007-03-08 16:01:40 UTC
I think the headers are fine as-is.  If anything, hostapd shouldn't be looking 
at headers that aren't intended for userland applications.

Still, I sympathize w/ your predicament.  Have you tried installing the 
kernel-devel package?  I think that will give you the headers you need until 
hostapd gets its act together.

Comment 3 Nicolas Chauvet (kwizart) 2007-04-01 00:16:14 UTC
Sorry for the late answear...
I was waiting for a new snapshoot to work with the renamed mac80211 stack
Actually i cannot find theses headers neither inside kernel-headers nor inside
kernel-devel

But they are provided by the mac80211 version from intel 
so i'm still using it for now for hostapd. As far as i have tested, only theses
files are needed.
[builder@Kwizatz BUILD]$ find . -name ieee80211_common.h
./hostapd-0.6-2007-03-25/mac80211-6.0.0/origin/net/mac80211/ieee80211_common.h
[builder@Kwizatz BUILD]$ find . -name hostapd_ioctl.h
./hostapd-0.6-2007-03-25/mac80211-6.0.0/origin/net/mac80211/hostapd_ioctl.h

Of course you are the prefered reviewer for the hostapd review:
https://bugzilla.redhat.com/230449

About your last comment, i may have missed something. Since hostapd is a
userland application shouldn't it "BuildRequires" kernel-headers more than
kernel-devel ? 



Comment 4 John W. Linville 2007-07-26 14:09:09 UTC
Per irc conversation...

Those headers are not really intended for userland.  Later versions of hostapd 
will need to use the nl80211 api when it is ready to support AP configuration.

In the meantime, I think the best option for a hostapd package is to snapshot 
the needed headers and either rebuild for every kernel release or make the 
package depend on the fedora release.  I will make an effort to preserve the 
existing hostap api in F-7 kernels through at least F-7's lifespan.