On Thursday 02 February 2006 21:04, John W. Linville wrote:
> On Thu, Feb 02, 2006 at 08:36:26PM +0100, Michael Buesch wrote:
> > Not sure, if I am the first one compiling the domesday branch,
> > but the ieee80211_rx symbol clashes:
> > 
> > net/ieee80211/built-in.o: In function `ieee80211_rx':
> > : multiple definition of `ieee80211_rx'
> > net/d80211/built-in.o:: first defined here
> > 
> > Maybe people always compile the stacks as modules, so this does
> > only appear on insmod time... .
> 
> It shows-up w/ allyesconfig.

Yes.

> Are you saying it shows-up w/ modules 
> as well?

No.

> Soon we will have to pick on stack or the other to pursue.
> (We probably already should have done it...)

Well, I really think we can't stay with either stack.
We must begin to merge both stacks to get a usable one.
And we need to rewrite the userspace ABI. (as discussed in
other threads).
But I would suggest to wait until the Wireless Summit at OSDL
is done. It is still two months from now, but I hope it
is worth waiting for it.
Or do you think we should start merging frunctionatity _now_,
to get more practical experience for the summit?

Anyway. In my opinion best will be to:
Stay with current in-kernel code and begin to merge functionality
from dscape. I think the ieee80211 API has to be cleaned up, too.
There is too much private stuff in the public structures. d80211 is
better at this point.

-- 
Greetings Michael.

Attachment: pgppTZ4IaHFkM.pgp
Description: PGP signature

Reply via email to