From: Eric Gaumer <gaumerel@ecs.fullerton.edu>
To: David Gibson <hermes@gibson.dropbear.id.au>
Cc: linux-kernel@vger.kernel.org, proski@gnu.org
Subject: Re: [PATCH] orinoco rfmon
Date: Sun, 27 Feb 2005 16:45:46 -0800 [thread overview]
Message-ID: <422269BA.9070308@ecs.fullerton.edu> (raw)
In-Reply-To: <20050227033944.GA15380@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 2102 bytes --]
David Gibson wrote:
>
> This looks like the ancient version of the monitor patch - which
> includes importing a lot of needless junk from the linux-wlan-ng
> tree. A cleaned up version of monitor has been merged in the orinoco
> CVS tree for ages now, but unfortunately that's long overdue for a
> merge with mainline. I'm trying to get that merge done - I just don't
> have much time or energy for the orinoco driver these days. One stack
> of patches which gets part of the way went to Jeff Garzik last week.
> We'll see how we go.
>
> In the meantime go to http://savannah.nongnu.org/projects/orinoco for
> access to the driver CVS. You probably want to get the "for_linus"
> branch of CVS if you're planning to work with 2.6.
>
Thanks David, the CVS code works great with the small excpetion of the following change to
get it to build.
diff -Nru orinoco-cvs/orinoco_cs.c orinoco-build/orinoco_cs.c
--- orinoco-cvs/orinoco_cs.c 2005-02-26 22:21:55.000000000 -0800
+++ orinoco-build/orinoco_cs.c 2005-02-27 15:00:07.698368136 -0800
@@ -428,7 +428,7 @@
SET_MODULE_OWNER(dev);
card->node.major = card->node.minor = 0;
- SET_NETDEV_DEV(dev, &handle_to_dev(handle));
+ dev->name[0] = '\0';
/* Tell the stack we exist */
if (register_netdev(dev) != 0) {
printk(KERN_ERR PFX "register_netdev() failed\n");
What's the deal with the broken firmware for monitor mode?
* v0.15rc1 -> v0.15rc2 - 28 Jul 2004 - Pavel Roskin & David Gibson
* o orinoco_pci saves PCI registers on suspend (Simon Huggins).
* o Monitor mode disabled on Agere 8.xx firmware - it's broken.
I have 8.4 but things seem fine (used this card in monitor mode for over a year without
problems).
I just disabled the check for broken firmware and things seem fine (better than the original
patch I posted). The iwlist command now works. Could the buggy firmware be generalized a bit
too much? Perhaps only certain versions > 8 are buggy?
--
"Education is what remains after one has forgotten everything he learned in school."
- Albert Einstein
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
next prev parent reply other threads:[~2005-02-28 0:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-26 18:10 Eric Gaumer
2005-02-26 20:59 ` Alexey Dobriyan
2005-02-26 22:45 ` Eric Gaumer
2005-02-28 7:44 ` Greg KH
2005-02-28 7:48 ` Eric Gaumer
2005-02-27 3:39 ` David Gibson
2005-02-28 0:45 ` Eric Gaumer [this message]
2005-02-28 0:54 ` David Gibson
2005-02-28 20:01 ` Pavel Roskin
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=422269BA.9070308@ecs.fullerton.edu \
--to=gaumerel@ecs.fullerton.edu \
--cc=hermes@gibson.dropbear.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=proski@gnu.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
Powered by JetHome