From: James Ketrenos <jketreno@linux.intel.com>
To: dragoran <dragoran@feuerpokemon.de>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: ipw3945?
Date: Tue, 31 Oct 2006 17:40:49 -0800 [thread overview]
Message-ID: <4547FB21.3050509@linux.intel.com> (raw)
In-Reply-To: <45464A2C.5090402@feuerpokemon.de>
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
next prev parent reply other threads:[~2006-11-01 1:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-30 18:53 ipw3945? dragoran
2006-11-01 1:40 ` James Ketrenos [this message]
2006-11-01 7:06 ` ipw3945? dragoran
-- strict thread matches above, loose matches on Subject: below --
2006-10-30 18:54 ipw3945? dragoran
2006-10-30 18:59 ` ipw3945? Arjan van de Ven
2006-10-30 19:32 ` ipw3945? Jiri Slaby
2006-10-31 2:44 ` ipw3945? Zhu Yi
2006-10-31 7:59 ` ipw3945? dragoran
2006-10-31 12:33 ` ipw3945? John W. Linville
2006-10-31 21:58 ` ipw3945? John W. Linville
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4547FB21.3050509@linux.intel.com \
--to=jketreno@linux.intel.com \
--cc=dragoran@feuerpokemon.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).