On Sunday 12 November 2006 21:17, Loïc Minier wrote:
> On Sun, Nov 12, 2006, Daniel Baumann wrote:
> > I don't want to have ipw* build with kernel-headers, but with iee80211
> > extra package.
>
> Argh!
>
> > There are basically two reasons for this:
> > 0. Currently the ieee80211 headers in mai
Jurij Smakov wrote:
> Please either finally do something about it (instead of promising progress
> "real soon now", as you did since August), or stop trying to block others
> from working on it.
uploaded to NEW.
--
Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist
Email:
[Sorry for breaking a thread. CC the responses to me, I'm not on -mentors]
On Sun, 12 Nov 2006, Daniel Baumann wrote:
> Andreas Barth wrote:
>> Eh, that doesn't sound really useful. One never knows for sure what the
>> future brings.
>
> We are speaking only about the time where ipw3945 is not in
On Sun, Nov 12, 2006, Daniel Baumann wrote:
> I don't want to have ipw* build with kernel-headers, but with iee80211
> extra package.
Argh!
> There are basically two reasons for this:
> 0. Currently the ieee80211 headers in mainline are recent enough to
> allow ipw* compiled against it. T
Andreas Barth wrote:
> Eh, that doesn't sound really useful. One never knows for sure what the
> future brings.
We are speaking only about the time where ipw3945 is not in mainline. I
don't see any practical gain in using mainline headers now, dealing with
problems there, and reverting to the extr
On Sunday 12 November 2006 20:46, Daniel Baumann wrote:
> I don't want to have ipw* build with kernel-headers, but with iee80211
> extra package.
>
> There are basically two reasons for this:
>
> 0. Currently the ieee80211 headers in mainline are recent enough to
> allow ipw* compiled agains
* Daniel Baumann ([EMAIL PROTECTED]) [061112 11:46]:
> 0. Currently the ieee80211 headers in mainline are recent enough to
> allow ipw* compiled against it. This may change again in
> future, hence I compile them all the time against ieee80211.
Eh, that doesn't sound really useful. One
Loïc Minier wrote:
> To add my $0.02 to the table, I'm willing to sponsor Kel's packages,
> and even uploading them right now if Daniel sees no objection. I have
> ipw3945 hardware myself, am running the packages prepared by Kel (which
> have a very useful patch to build against vanilla linux-
Hi,
To add my $0.02 to the table, I'm willing to sponsor Kel's packages,
and even uploading them right now if Daniel sees no objection. I have
ipw3945 hardware myself, am running the packages prepared by Kel (which
have a very useful patch to build against vanilla linux-headers), and
Hi,
This is not a request for sponsorship, rather a request for conversation and
action required to support ipw3945 hardware in etch (if that is even possible
now, with deadline imminent). I hope some interested developers may find the
following ipw3945 kernel module source package a nice head
Hi,
I have prepared the ipw3945-daemon package, following the ITP 391686.
The debian subdirectory can be found in kernel team's svn repo at
svn://svn.debian.org/svn/kernel/people/jurij/ipw3945-daemon
The source and binary packages for i386 are available at
http://www.wooyd.org/debian/ipw3945-d
11 matches
Mail list logo
