Linux wireless drivers development
 help / color / mirror / Atom feed
From: Filippo Zangheri <filippo.zangheri@yahoo.it>
To: Chris Hallinan <challinan@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Bug 1623
Date: Tue, 11 Mar 2008 16:13:56 +0100	[thread overview]
Message-ID: <47D6A1B4.8060603@yahoo.it> (raw)
In-Reply-To: <43e72e890803110803k5dae7300i94ff883c4dd5e9e9@mail.gmail.com>

Luis R. Rodriguez ha scritto:
> On Tue, Mar 11, 2008 at 2:17 AM, Tomas Winkler <tomasw@gmail.com> wro=
te:
>> On Tue, Mar 11, 2008 at 1:50 AM, Chris Hallinan <challinan@gmail.com=
> wrote:
>>  > On Mon, Mar 10, 2008 at 11:05 AM, Tomas Winkler <tomasw@gmail.com=
> wrote:
>>  >
>>  > > On Mon, Mar 10, 2008 at 4:02 PM, Chris Hallinan <challinan@gmai=
l.com> wrote:
>>  >  >  > http://bughost.org/bugzilla/show_bug.cgi?id=3D1623
>>  >  >  >
>>  >  >  >  Anything else I can do to help move this along?  I'd love =
to dive into
>>  >  >  >  the code, I just need a little guidance!  I've written and=
 debugged a
>>  >  >  >  few Linux drivers in my day...
>>  >  >  >
>>  >  >  >  Any other testing you need, I'd be happy to assist.
>>  >  >  >
>>  >  >  >  Thanks,
>>  >  >  >
>>  >  >  >  Chris
>>  >  >
>>  >  >  We've recently committed fixes to 4965 rate scaling can you t=
ry the
>>  >  >  latest version of wireless-testing kernel?
>>  >  >
>>  >  I was unable to get either 1.2.25 nor top-of-tree from git (iwlw=
ifi)
>>  >  to compile with wireless-testing kernel.
>>
>>  I see, the point is that wireless-testing already contains latest
>>  iwlwifi driver much newer then 1.2.25. so no need for patching just
>>  compile the kernel.
>=20
> Or if you don't want to compile your kernel and just compile the
> modules externally you can grab the compat-wireless-package that pull=
s
> daily from wireless-testing:
>=20
> http://linuxwireless.org/en/users/Download

I can confirm that. Building wireless drivers modules and subsystem
was never so easy and time-efficient.

Maybe this is useless, but if you want to avoid bulding all modules
and subsystems you just need to edit config.mk.

Great project!

Just my =E2=82=AC0.02.

--=20
=46ilippo Zangheri

GPG key ID: 0xE1D879FA
Key fingerprint: 816B CE57 D43C 0A47 EF35 3378 EA5F A72A E1D8 79FA
Key server: pgp.mit.edu

-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GE d- s+:- a-- C++ UL+++ P+ L+++ E-- W+ N* o-- K- w--- O-- M--
V- PS++ PE+ Y+ PGP++ t 5-- X++ R* tv b+ DI-- D---- G-- e++ h--
r++ z*
------END GEEK CODE BLOCK------

--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2008-03-11 15:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-10 14:02 Bug 1623 Chris Hallinan
2008-03-10 15:05 ` Tomas Winkler
2008-03-10 16:24   ` Chris Hallinan
2008-03-10 23:50   ` Chris Hallinan
2008-03-11  6:17     ` Tomas Winkler
2008-03-11 15:03       ` Luis R. Rodriguez
2008-03-11 15:13         ` Filippo Zangheri [this message]
2008-03-11 15:31           ` Tomas Winkler
2008-03-11 16:34       ` Chris Hallinan

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=47D6A1B4.8060603@yahoo.it \
    --to=filippo.zangheri@yahoo.it \
    --cc=challinan@gmail.com \
    --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