ipw3945?

ipw3945?

[dragoran]

The ipw3945 driver has been out for a while and is not yet upstream.
It requires a binary only daemon to work, but I still see no reason not 
to merge it.
Many wlan drivers require binary firmware anyway, so I don't see a 
reason not to merge it.
I also have read this: http://lwn.net/Articles/205988/ (and the old 
thread on lkml/netdev)
Can this be used to make the driver work without the daemon?
It seems that the development of the driver has stopped since july, 
maybe because it never will get merged and intel decided to stop working 
on it?
If this is true it could mean that feature intel wlan chips will end up 
with no linux drivers :(

ipw3945?

[dragoran]

The ipw3945 driver has been out for a while and is not yet upstream.
It requires a binary only daemon to work, but I still see no reason not
to merge it.
Many wlan drivers require binary firmware anyway, so I don't see a
reason not to merge it.
I also have read this: http://lwn.net/Articles/205988/ (and the old
thread on lkml/netdev)
Can this be used to make the driver work without the daemon?
It seems that the development of the driver has stopped since july,
maybe because it never will get merged and intel decided to stop working
on it?
If this is true it could mean that feature intel wlan chips will end up
with no linux drivers :(

please CC me ...

Re: ipw3945?

[Arjan van de Ven]

On Mon, 2006-10-30 at 19:54 +0100, dragoran wrote:
> The ipw3945 driver has been out for a while and is not yet upstream.
> It requires a binary only daemon to work, but I still see no reason not
> to merge it.
> Many wlan drivers require binary firmware anyway, so I don't see a
> reason not to merge it.

has Intel submitted it for inclusion?

No.

> It seems that the development of the driver has stopped since july,
> maybe because it never will get merged and intel decided to stop working
> on it?

No this is not correct. I'll let James comment on what we are doing
though, he can explain that a lot better than I can.


-- 
if you want to mail me at work (you don't), use arjan (at) linux.intel.com
Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org

Re: ipw3945?

[Jiri Slaby]

Arjan van de Ven wrote:
> On Mon, 2006-10-30 at 19:54 +0100, dragoran wrote:
>> The ipw3945 driver has been out for a while and is not yet upstream.
>> It requires a binary only daemon to work, but I still see no reason not
>> to merge it.
>> Many wlan drivers require binary firmware anyway, so I don't see a
>> reason not to merge it.
> 
> has Intel submitted it for inclusion?
> 
> No.

It seems to be still in a devel phase -- it doesn't work for me (and other people):
http://bughost.org/bugzilla/show_bug.cgi?id=1152

regards,
-- 
http://www.fi.muni.cz/~xslaby/            Jiri Slaby
faculty of informatics, masaryk university, brno, cz
e-mail: jirislaby gmail com, gpg pubkey fingerprint:
B674 9967 0407 CE62 ACC8  22A0 32CC 55C3 39D4 7A7E

Re: ipw3945?

[Zhu Yi]

On Mon, 2006-10-30 at 19:54 +0100, dragoran wrote:
> Can this be used to make the driver work without the daemon?

Yup. And we have already successfully put the daemon's work into the
firmware/ucode. The new firmware will be released soon. Stay tuned.

Thanks,
-yi

Re: ipw3945?

[dragoran]

Zhu Yi wrote:
> On Mon, 2006-10-30 at 19:54 +0100, dragoran wrote:
>   
>> Can this be used to make the driver work without the daemon?
>>     
>
> Yup. And we have already successfully put the daemon's work into the
> firmware/ucode. The new firmware will be released soon. Stay tuned.
>
>   
ok thx fro the info
does this mean that after the daemon is no longer required this driver 
can be included in the upstream kernel?
> Thanks,
> -yi
>
>   

Re: ipw3945?

[John W. Linville]

On Tue, Oct 31, 2006 at 10:44:21AM +0800, Zhu Yi wrote:
> On Mon, 2006-10-30 at 19:54 +0100, dragoran wrote:
> > Can this be used to make the driver work without the daemon?
> 
> Yup. And we have already successfully put the daemon's work into the
> firmware/ucode. The new firmware will be released soon. Stay tuned.

Please define "soon".  I am a bit tired of hearing about how this is
just around the corner, only to find-out that it is months away.

John
-- 
John W. Linville
linville@tuxdriver.com

Re: ipw3945?

[John W. Linville]

On Tue, Oct 31, 2006 at 07:33:43AM -0500, John W. Linville wrote:
> On Tue, Oct 31, 2006 at 10:44:21AM +0800, Zhu Yi wrote:
> > On Mon, 2006-10-30 at 19:54 +0100, dragoran wrote:
> > > Can this be used to make the driver work without the daemon?
> > 
> > Yup. And we have already successfully put the daemon's work into the
> > firmware/ucode. The new firmware will be released soon. Stay tuned.
> 
> Please define "soon".  I am a bit tired of hearing about how this is
> just around the corner, only to find-out that it is months away.

For the record, my "months away" comment seems to have been based
on a misunderstanding of some prior postings.  I apologize for any
confusion or embarassment which I might have caused.

John
-- 
John W. Linville
linville@tuxdriver.com

Re: ipw3945?

[James Ketrenos]

dragoran wrote:
...
> It seems that the development of the driver has stopped since july,
> maybe because it never will get merged and intel decided to stop working
> on it?

Development hasn't stopped, I'm just a slacker ;).  I was away from work
for a while, and on return I was sucked into various issues that have
now (hopefully) all been resolved (or routed to /dev/null).

We have several patches that have backed up in our bug database
(http://bughost.org/cover/ and click on 'tested patches') that I'll be
pushing to our GIT tree as well as releasing a new snapshot to SF.

We've also been working on some new code internally we're putting
through some testing before we push out.  Expect some good things in the
coming weeks.

> If this is true it could mean that feature intel wlan chips will end up
> with no linux drivers :(

We do what we can internally to ensure that is never the case.

James

Re: ipw3945?

[dragoran]

James Ketrenos wrote:
> dragoran wrote:
> ...
>   
>> It seems that the development of the driver has stopped since july,
>> maybe because it never will get merged and intel decided to stop working
>> on it?
>>     
>
> Development hasn't stopped, I'm just a slacker ;).  I was away from work
> for a while, and on return I was sucked into various issues that have
> now (hopefully) all been resolved (or routed to /dev/null).
>
> We have several patches that have backed up in our bug database
> (http://bughost.org/cover/ and click on 'tested patches') that I'll be
> pushing to our GIT tree as well as releasing a new snapshot to SF.
>
> We've also been working on some new code internally we're putting
> through some testing before we push out.  Expect some good things in the
> coming weeks.
>
>   
ok thx for the info :)
>> If this is true it could mean that feature intel wlan chips will end up
>> with no linux drivers :(
>>     
>
> We do what we can internally to ensure that is never the case.
>
>   
:)
> James
>
>