Re: ipw2200 on 2.6.16: redefinition of 'struct semaphore'

fabio adelardi <[email protected]>
Newsgroups gmane.linux.drivers.ipw2100.devel
Message-ID <[email protected]>
Axel Thimm <Axel.Thimm <at> ATrpms.net> writes:

> 
> On Tue, Feb 28, 2006 at 10:19:23AM +0100, Axel Thimm wrote:
> > On Tue, Feb 28, 2006 at 10:26:26AM +0800, Zhu Yi wrote:
> > > On Mon, 2006-02-27 at 17:48 +0100, Axel Thimm wrote:
> > > > Since I found no definition of struct semaphore in
> > > > ipw2200 it looks like the error happens by just including some broken
> > > > kernel headers. Am I right? 
> > > 
> > > It should not define mutex_init for kernels > 2.6.15. Do you have below
> > > code snippet in your ipw2200.h?
> > 
> > I see, the issue is that Red Hat uses an internal versioning of 2.6.15
> > for the 2.6.16rcX kernels, so the conditional triggered wrongly (the
> > rationale is that when 2.6.16 is released, rpm could consider 2.6.16
> > older than 2.6.16rcX).
> > 
> > This is a Red Hat rpm kernel specific bug then, and should be easily
> > fixed by a patch in the package. Thanks for the hint, I'll retry later
> > to build ipw2200 for FC5 and report back.
> 
> That was indeed the issue, thanks for pointing this out!
> 
> > > #if LINUX_VERSION_CODE > KERNEL_VERSION(2,6,15)
> > > #include <linux/mutex.h>
> > > #else
> > > # define mutex semaphore
> > > # define mutex_init init_MUTEX
> > > # define mutex_lock down
> > > # define mutex_unlock up
> > > #endif
> 


hi all and hi you, axel

my name is fabio and i'm an italian FC5 user with the default
2.6.15-1.2054_FC5 kernel in an asus notebook with the intel pro wireless
2200bg device.

I've had your same problem compiling the ipw2200 driver; could you please tell
me how did you solve the issue in object, eventually posting the link of the
patch (and some hint to help me)?

and do you think that i could not meet the problem compiling the last
kernel version as 2.6.16-1.2122_FC5?

thanks!! 

fabio
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.