From: Pablo Sanchez <pablo@blueoakdb.com>
To: Mike Kershaw <dragorn@kismetwireless.net>
Cc: Jens Axboe <jens.axboe@oracle.com>,
Ismail D?nmez <ismail@pardus.org.tr>,
Dan Williams <dcbw@redhat.com>,
Stephen.Clark@seclark.us, linux-wireless@vger.kernel.org,
ipw3945-devel@lists.sourceforge.net,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [ipw3945-devel] iwl3945 doesn't work
Date: Thu, 15 Nov 2007 13:36:16 -0500 [thread overview]
Message-ID: <200711151336.16589.pablo@blueoakdb.com> (raw)
In-Reply-To: <20071115150519.GA27231@drd1813.lan>
On Thursday 15 November 2007 at 10:05 am, Mike Kershaw penned
about "Re: [ipw3945-devel] iwl3945 doesn't work:
> On Thu, Nov 15, 2007 at 05:30:14AM -0500, Pablo Sanchez wrote:
> > On Thursday 15 November 2007 at 5:26 am, Jens Axboe penned
> >
> > about "Re: [ipw3945-devel] iwl3945 doesn't work:
> > > I'll revert to using ipw3945, it worked flawlessly for me.
> > > Hopefully the iwl3945 driver will work sometime in the future,
> > > but as you note, not a lot of progress appears to be happening.
> > > So I wont hold my breath.
> >
> > Hmmm, will that driver work on my Intel PRO 4965 card?
>
> No, but iwl4965 from the same driver tree will.
I think you jumped into the thread. The iwl4965 driver is covered by
iwlwifi and that's the driver which I've reported a couple of issues.
So far, no word from Intel. Hence why I'm using 'blinky'
blinky - a 3COM card which blinks once a second.
Cheers,
--
Pablo
next prev parent reply other threads:[~2007-11-15 18:36 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-17 13:54 iwl3945 doesn't work Jens Axboe
2007-10-17 13:59 ` Jens Axboe
2007-10-17 14:07 ` John W. Linville
2007-10-17 14:08 ` Ismail Dönmez
2007-10-17 14:11 ` Jens Axboe
2007-10-17 14:15 ` Ismail Dönmez
2007-10-17 14:17 ` Jens Axboe
2007-10-17 14:18 ` Dan Williams
2007-10-17 14:22 ` Jens Axboe
2007-10-17 15:16 ` Dan Williams
2007-10-17 16:35 ` Jens Axboe
2007-10-17 20:06 ` [ipw3945-devel] " Stephen Clark
2007-10-18 6:57 ` Jens Axboe
2007-10-18 12:23 ` Stephen Clark
2007-10-18 12:33 ` Johannes Berg
2007-10-18 13:02 ` Tomas Winkler
2007-11-10 2:18 ` Ian Schram
2007-11-15 0:53 ` Ismail Dönmez
2007-11-15 9:39 ` Jens Axboe
2007-11-15 10:23 ` Pablo Sanchez
2007-11-15 10:26 ` Jens Axboe
2007-11-15 10:30 ` Pablo Sanchez
2007-11-15 11:08 ` Jens Axboe
2007-11-15 15:05 ` Mike Kershaw
2007-11-15 15:09 ` Jens Axboe
2007-11-15 18:36 ` Pablo Sanchez [this message]
2007-11-15 15:10 ` John W. Linville
2007-11-15 15:14 ` Jens Axboe
2007-11-15 17:36 ` Ian Schram
2007-10-18 12:34 ` Jens Axboe
2007-10-17 14:11 ` Dan Williams
2007-10-17 14:16 ` Jens Axboe
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=200711151336.16589.pablo@blueoakdb.com \
--to=pablo@blueoakdb.com \
--cc=Stephen.Clark@seclark.us \
--cc=dcbw@redhat.com \
--cc=dragorn@kismetwireless.net \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=ismail@pardus.org.tr \
--cc=jens.axboe@oracle.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@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).