From: reinette chatre <reinette.chatre@intel.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Kalle Valo <kalle.valo@iki.fi>, Darren Blaber <dmbtech@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: iwl3945 not working after recent commits
Date: Mon, 22 Jun 2009 10:03:02 -0700 [thread overview]
Message-ID: <1245690182.24303.488.camel@rc-desk> (raw)
In-Reply-To: <43e72e890906192221p5cc67d28gb14b214bbf252ad@mail.gmail.com>
On Fri, 2009-06-19 at 22:21 -0700, Luis R. Rodriguez wrote:
> On Fri, Jun 19, 2009 at 9:33 PM, Kalle Valo<kalle.valo@iki.fi> wrote:
> > "Luis R. Rodriguez" <mcgrof@gmail.com> writes:
> >
> >>> I'm using 2.6.30 with the KMS radeon patches, don't know if that is
> >>> interfering. I'll try wireless-testing directly.
> >>
> >> Yeah this is odd, 2.6.30 shouldn't have an issue with backport unless
> >> I'm missing something. Let us know how it goes with wireless-testing.
> >
> > I'm using latest wireles-testing and I have iwl3945 on my X60s. iwl3945
> > is working fine for me.
>
> Yeah the user tried a vanilla 2.6.30 and it seems to be working fine
> now, it seems related to kms somehow.
Darren also submitted a kernel.org (#13585) bug which was closed by
himself with reason "Turns out it was a bad development kernel from
ubuntu.".
Reinette
next prev parent reply other threads:[~2009-06-22 16:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-19 23:33 iwl3945 not working after recent commits Darren Blaber
2009-06-19 23:42 ` Luis R. Rodriguez
2009-06-20 2:12 ` Darren Blaber
2009-06-20 2:15 ` Luis R. Rodriguez
2009-06-20 2:19 ` Darren Blaber
2009-06-20 2:24 ` Luis R. Rodriguez
2009-06-20 4:33 ` Kalle Valo
2009-06-20 5:21 ` Luis R. Rodriguez
2009-06-22 17:03 ` reinette chatre [this message]
2009-06-22 20:18 ` Darren Blaber
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=1245690182.24303.488.camel@rc-desk \
--to=reinette.chatre@intel.com \
--cc=dmbtech@gmail.com \
--cc=kalle.valo@iki.fi \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
/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).