* Re: compat-wireless master-2009-09-28 breakage and suggested fixes
From: Luis R. Rodriguez @ 2009-09-29 2:55 UTC (permalink / raw)
To: Hin-Tak Leung; +Cc: Luis Rodriguez, linux-wireless
In-Reply-To: <3ace41890909281935k284402f3q90b54ae20a636eeb@mail.gmail.com>
On Mon, Sep 28, 2009 at 07:35:22PM -0700, Hin-Tak Leung wrote:
> commit d0cf9c0dadcdc89a755bcb301cfc9c796eb28ccf
> Author: Stephen Hemminger <shemminger@vyatta.com>
> Date: Mon Aug 31 19:50:57 2009 +0000
>
> wireless: convert drivers to netdev_tx_t
>
> and the 2nd change due to this:
>
> commit 384912ed194e43c03ad1cdaa09b0b1e488c34d46
> Author: Marcel Holtmann <marcel@holtmann.org>
> Date: Mon Aug 31 21:08:19 2009 +0000
>
> net: Add DEVTYPE support for Ethernet based devices
>
> Both of these changes are traced back to changes in
> <linux/netdevice.h> , which compat-wireless does not ship. What's your
> policy on these kind of changes to compat-wireless?
> (the 2nd SET_NETDEV_DEVTYPE change probably can be spanned by an
> ifndef SET_NETDEV_DEVTYPE, and roll into
> "compat/patches/01-netdev.patch"? Should the first kind of change also
> go into compat/patches/01-netdev.patch?)
I don't see this yet on wireless-testing but it is on 2.6.32.
I backported this as follows. I'll push this out shortly.
From: Luis R. Rodriguez <lrodriguez@atheros.com>
Subject: [PATCH] Fix compilation against for 2.6.32 changes
2.6.32 added SET_NETDEV_DEVTYPE() and netdev_tx
Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
---
compat/compat-2.6.32.h | 12 ++++++++++++
1 files changed, 12 insertions(+), 0 deletions(-)
diff --git a/compat/compat-2.6.32.h b/compat/compat-2.6.32.h
index f7081f2..418b521 100644
--- a/compat/compat-2.6.32.h
+++ b/compat/compat-2.6.32.h
@@ -31,6 +31,18 @@
#define dev_change_net_namespace(a, b, c) (-EOPNOTSUPP)
+#define SET_NETDEV_DEVTYPE(netdev, type)
+
+#ifdef __KERNEL__
+/* Driver transmit return codes */
+enum netdev_tx {
+ BACKPORT_NETDEV_TX_OK = NETDEV_TX_OK, /* driver took care of packet */
+ BACKPORT_NETDEV_TX_BUSY = NETDEV_TX_BUSY, /* driver tx path was busy*/
+ BACKPORT_NETDEV_TX_LOCKED = NETDEV_TX_LOCKED, /* driver tx lock was already taken */
+};
+typedef enum netdev_tx netdev_tx_t;
+#endif /* __KERNEL__ */
+
#endif /* (LINUX_VERSION_CODE < KERNEL_VERSION(2,6,32)) */
#endif /* LINUX_26_32_COMPAT_H */
--
1.6.3.3
^ permalink raw reply related
* Re: compat-wireless master-2009-09-28 breakage and suggested fixes
From: Hin-Tak Leung @ 2009-09-29 3:33 UTC (permalink / raw)
To: Luis R. Rodriguez; +Cc: Luis Rodriguez, linux-wireless
In-Reply-To: <20090929025509.GB6529@mosca>
On Tue, Sep 29, 2009 at 3:55 AM, Luis R. Rodriguez
<lrodriguez@atheros.com> wrote:
> On Mon, Sep 28, 2009 at 07:35:22PM -0700, Hin-Tak Leung wrote:
>> commit d0cf9c0dadcdc89a755bcb301cfc9c796eb28ccf
>> Author: Stephen Hemminger <shemminger@vyatta.com>
>> Date: Mon Aug 31 19:50:57 2009 +0000
>>
>> wireless: convert drivers to netdev_tx_t
>>
>> and the 2nd change due to this:
>>
>> commit 384912ed194e43c03ad1cdaa09b0b1e488c34d46
>> Author: Marcel Holtmann <marcel@holtmann.org>
>> Date: Mon Aug 31 21:08:19 2009 +0000
>>
>> net: Add DEVTYPE support for Ethernet based devices
>>
>> Both of these changes are traced back to changes in
>> <linux/netdevice.h> , which compat-wireless does not ship. What's your
>> policy on these kind of changes to compat-wireless?
>> (the 2nd SET_NETDEV_DEVTYPE change probably can be spanned by an
>> ifndef SET_NETDEV_DEVTYPE, and roll into
>> "compat/patches/01-netdev.patch"? Should the first kind of change also
>> go into compat/patches/01-netdev.patch?)
>
> I don't see this yet on wireless-testing but it is on 2.6.32.
> I backported this as follows. I'll push this out shortly.
>
> From: Luis R. Rodriguez <lrodriguez@atheros.com>
> Subject: [PATCH] Fix compilation against for 2.6.32 changes
>
> 2.6.32 added SET_NETDEV_DEVTYPE() and netdev_tx
Argh, I see what you are getting at: codes that emulates "API changes
between 2.6.(x-1) and 2.6.(x)" go into file
compat/compat-2.6.(x).{h,c} .
The 'compatibility code for new kernel' wording wasn't too obvious :-).
>
> Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
Acked.
> ---
> compat/compat-2.6.32.h | 12 ++++++++++++
> 1 files changed, 12 insertions(+), 0 deletions(-)
>
> diff --git a/compat/compat-2.6.32.h b/compat/compat-2.6.32.h
> index f7081f2..418b521 100644
> --- a/compat/compat-2.6.32.h
> +++ b/compat/compat-2.6.32.h
> @@ -31,6 +31,18 @@
>
> #define dev_change_net_namespace(a, b, c) (-EOPNOTSUPP)
>
> +#define SET_NETDEV_DEVTYPE(netdev, type)
> +
> +#ifdef __KERNEL__
> +/* Driver transmit return codes */
> +enum netdev_tx {
> + BACKPORT_NETDEV_TX_OK = NETDEV_TX_OK, /* driver took care of packet */
> + BACKPORT_NETDEV_TX_BUSY = NETDEV_TX_BUSY, /* driver tx path was busy*/
> + BACKPORT_NETDEV_TX_LOCKED = NETDEV_TX_LOCKED, /* driver tx lock was already taken */
> +};
> +typedef enum netdev_tx netdev_tx_t;
> +#endif /* __KERNEL__ */
> +
> #endif /* (LINUX_VERSION_CODE < KERNEL_VERSION(2,6,32)) */
>
> #endif /* LINUX_26_32_COMPAT_H */
> --
> 1.6.3.3
>
>
^ permalink raw reply
* Re: Firmware versioning best practices
From: Holger Schurig @ 2009-09-29 6:59 UTC (permalink / raw)
To: Luis R. Rodriguez
Cc: linux-wireless, reinette chatre, Kalle Valo, Johannes Berg,
Christian Lamparter, Bob Copeland
In-Reply-To: <43e72e890909281517k23abaf8dvd3e84837ce307429@mail.gmail.com>
> Or shall we have the same firmware filename and simply query
> the firmware for a map of capabilities? Any other ideas?
Don't put the version into the filename. This is not a common
practice for Linux / BSD / whatever systems. Usually you have
a "kmail" file, not a kmail3.5, kmail4.0 and kmail4.2 file.
Versions or capability maps can be stored inside the firmware and
queried at load time. E.g. the libertas driver does it that way.
If you make your firmware redistributable (which I recommend),
the version will also be stored in the package metadata, e.g.
the rpm or deb file and the infrastructure for rpm/yum deb/apt.
--
http://www.holgerschurig.de
^ permalink raw reply
* Re: [PATCH] libertas: Add auto deep sleep support for SD8385/SD8686/SD8688
From: Holger Schurig @ 2009-09-29 7:04 UTC (permalink / raw)
To: Bing Zhao
Cc: Dan Williams, libertas-dev@lists.infradead.org,
linux-wireless@vger.kernel.org, Amitkumar Karwar
In-Reply-To: <477F20668A386D41ADCC57781B1F704306DDA6C1B6@SC-VEXCH1.marvell.com>
Hi Bing !
Please note that I just sent an experimental patch to enable
cfg80211 for libertas.
Once this is polished, you can immediately start using
nl80211/cfg80211 to configure such things, there's no need to
have the full thingy (e.g. wpa_supplicant via -Dnl80211 working
with WEP/WPA/WPA2) working, those things are not interrelated.
--
http://www.holgerschurig.de
^ permalink raw reply
* Re: [PATCH] libertas: Add auto deep sleep support for SD8385/SD8686/SD8688
From: Holger Schurig @ 2009-09-29 7:24 UTC (permalink / raw)
To: Bing Zhao
Cc: Dan Williams, libertas-dev@lists.infradead.org,
linux-wireless@vger.kernel.org, Amitkumar Karwar
In-Reply-To: <477F20668A386D41ADCC57781B1F704306DDA6C1B6@SC-VEXCH1.marvell.com>
> iwconfig wlan0 power period 0 -> enable deep sleep (enter
> deep sleep immediately)
> iwconfig wlan0 power period 5 -> enable auto deep sleep
> (enter deep sleep automatically after 5s idle time)
> iwconfig wlan0 power period -1 -> disable deep sleep / auto
> deep sleep
ACK from my side (not that I'm the maintainer ...)
--
http://www.holgerschurig.de
^ permalink raw reply
* Re: Question on general wireless testing tree compilation.
From: Balaji Ravindran @ 2009-09-29 7:29 UTC (permalink / raw)
To: Hin-Tak Leung; +Cc: Linux Wireless
In-Reply-To: <3ace41890909281452x3170c8c6g5dc56cff85663099@mail.gmail.com>
Hi,
Thanks for this info, i shall try to keep the old *working* config
option. Though, with the README help file, I was successfully able to
make and *select* my new target kernel, i had a kernel panic, and was
not able to boot to it, also i noticed that my USB keybd and mouse
connected to my monitor's usb port did not come up, so i guess
something bad happened while doing make modules_install install, or
while setting up the configurations before making.
I shall try to re-compile with my known good configuration.
Thanks again for the info.
Thanks
Balaji R
On Sep 28, 2009, at 2:52 PM, Hin-Tak Leung wrote:
>
> Also, compat-wireless (which just replaces the wireless-related kernel
> modules) is sometimes a quicker/easier alternative to the whole
> wireless-testing.
^ permalink raw reply
* bleeding edge ar9170usb: Fritz N USB support?
From: Malte Gell @ 2009-09-29 8:14 UTC (permalink / raw)
To: linux-wireless
Hello!
At
http://linuxwireless.org/en/users/Drivers/ar9170
I read support for the 802.11n Fritz N USB will be until kernel 2.6.32.
So, I wonder is this USB stick already supported in the bleeding edge compat-
wireless-2.6?
Thanx
Malte
^ permalink raw reply
* Re: cannot compile compate-wirless snapshots
From: Malte Gell @ 2009-09-29 8:47 UTC (permalink / raw)
To: Hauke Mehrtens; +Cc: linux-wireless
In-Reply-To: <4ABDE7AC.1090409@hauke-m.de>
Hello, sorry for my late reply....
Hauke Mehrtens <hauke@hauke-m.de> wrote
> Malte Gell wrote:
> > Hello,
> >
> > actually I can build the stable compat-wirless-2.6.30.ta.bz2 just fine.
> >
> > But I get make errors, when I try to build the daily snapshot, see below.
> > I use openSUSE on a 2.6.27 kernel.
> what kernel are you using?
2.6.27.29-0.1 from openSUSE 11.1
> Does this file exists in your installation?
> /lib/modules/`uname -r`/build/include/linux/tracepoint.h ?
Yes ! The kernel tracepoint API is there in openSuSE11.1, but I still cannot
compile compat-wireless-2.6
Besides tracepoint thing, does ar9170us require 2.6.29? As said, tracepoint
does exist in my kernel....
thanx
Malte
^ permalink raw reply
* Re: cannot compile compate-wirless snapshots
From: Malte Gell @ 2009-09-29 8:50 UTC (permalink / raw)
To: Hauke Mehrtens; +Cc: linux-wireless
In-Reply-To: <4ABDE7AC.1090409@hauke-m.de>
Hauke Mehrtens <hauke@hauke-m.de> wrote
> Does this file exists in your installation?
> /lib/modules/`uname -r`/build/include/linux/tracepoint.h ?
Yes, but, look:
cd /usr/src/linux
grep -i tracepoint .config
# CONFIG_TRACEPOINTS is not set
Do I need to set it to yes?
Malte
^ permalink raw reply
* compat-wireless tracepoint error Re: [Ndiswrapper-general] Need help to create driver for Netgear WN111v2
From: Hin-Tak Leung @ 2009-09-29 8:51 UTC (permalink / raw)
To: Malte Gell; +Cc: ndiswrapper-general, linux-wireless
In-Reply-To: <200909290956.49681.malte.gell@gmx.de>
--- On Tue, 29/9/09, Malte Gell <malte.gell@gmx.de> wrote:
> "Hin-Tak Leung" <hintak_leung@yahoo.co.uk>
> wrote
>
> > --- On Tue, 29/9/09, Malte Gell <malte.gell@gmx.de>
> wrote:
> > > I prefer to wait ;-) This way I can stick with
> kernel
> > > 2.6.27 and just install
> > > this package, otherwise I would have to upgrade
> my kernel,
> > > because ar9170
> > > needs kernel >= 2.6.29 as far as I know. And i
> always
> > > fear, a kernel update
> > > could break other things,
>
> > Where did you learn this from? It says bleeding-edge
> compat-wireless
> > (http://linuxwireless.org/en/users/Download#Compat-wireless_release_types)
> > requires Kernel >= 2.6.27 . and it is not a *full*
> kernel update -
>
> Yes, compat-wirless-2.6 needs kernel 2.6.27, but, the
> ar9170 driver requires
> kernel 2.6.29, below you can see the "make" output when
> building compat-
> wireless-2.6 from today on kernel 2.6.27. It is this
> tracepoint issue that
> requires kernel 2.6.29
>
> Regards
> Malte
Hmm, I see you have already posted to linux-wireless and already got your answers. Hauke has already given you the answer - your kernel tree is *not* 2.6.27(.0), and as it is obvious that you have 2.6.27.29-0.1, which is 2.6.27.29 + suse-patches. Even 2.6.27.29 is not 2.6.27(.0), but somewhat closer to 2.6.28. And you really have already had your answer - your tree is somewhat between 2.6.27 and 2.6.28, and *neither*.
My suggestion would be simply to delete all the 'error: redefinition' parts from net/compat-2.6.28.h , because you already have them in the suse tree.
You may also need to delete something from net/compat-2.6.28.c, but that will happen during the linking stage (much later).
>
>
> ./scripts/driver-select ar9170
>
> make
>
> ./scripts/gen-compat-autoconf.sh config.mk >
> include/linux/compat_autoconf.h
> make -C /lib/modules/2.6.27.29-0.1-k7/build
> M=/home/malte_gell/download/src/wifi/compat-wireless-2009-09-29
> modules
> make[1]: Entering directory `/usr/src/linux-2.6.27.29-0.1'
> LD
> /home/malte_gell/download/src/wifi/compat-
> wireless-2009-09-29/drivers/net/wireless/ath/built-in.o
> CC [M]
> /home/malte_gell/download/src/wifi/compat-
> wireless-2009-09-29/drivers/net/wireless/ath/main.o
> In file included from
> /home/malte_gell/download/src/wifi/compat-
> wireless-2009-09-29/include/net/compat.h:19,
>
> from <command-line>:0:
> /home/malte_gell/download/src/wifi/compat-
> wireless-2009-09-29/include/net/compat-2.6.28.h:152: error:
> redefinition of
> ‘struct tracepoint’
> In file included from
> /home/malte_gell/download/src/wifi/compat-
> wireless-2009-09-29/include/net/compat.h:19,
>
> from <command-line>:0:
> /home/malte_gell/download/src/wifi/compat-
> wireless-2009-09-29/include/net/compat-2.6.28.h:182:1:
> warning: "DEFINE_TRACE"
> redefined
> In file included from include/linux/module.h:19,
>
> from include/linux/textsearch.h:7,
>
> from include/linux/skbuff.h:26,
>
> from
> /home/malte_gell/download/src/wifi/compat-
> wireless-2009-09-29/include/net/compat-2.6.28.h:10,
>
> from
> /home/malte_gell/download/src/wifi/compat-
> wireless-2009-09-29/include/net/compat.h:19,
>
> from <command-line>:0:
> include/linux/tracepoint.h:86:1: warning: this is the
> location of the previous
> definition
> /home/malte_gell/download/src/wifi/compat-
> wireless-2009-09-29/include/net/compat-2.6.28.h:186: error:
> redefinition of
> ‘tracepoint_update_probe_range’
> include/linux/tracepoint.h:100: error: previous definition
> of
> ‘tracepoint_update_probe_range’ was here
> make[4]: *** [/home/malte_gell/download/src/wifi/compat-
> wireless-2009-09-29/drivers/net/wireless/ath/main.o] Fehler
> 1
> make[3]: *** [/home/malte_gell/download/src/wifi/compat-
> wireless-2009-09-29/drivers/net/wireless/ath] Fehler 2
> make[2]: *** [/home/malte_gell/download/src/wifi/compat-
> wireless-2009-09-29/drivers/net/wireless] Fehler 2
> make[1]: ***
> [_module_/home/malte_gell/download/src/wifi/compat-
> wireless-2009-09-29] Fehler 2
> make[1]: Leaving directory `/usr/src/linux-2.6.27.29-0.1'
> make: *** [modules] Fehler 2
>
>
^ permalink raw reply
* Re: compat-wireless tracepoint error Re: [Ndiswrapper-general] Need help to create driver for Netgear WN111v2
From: Malte Gell @ 2009-09-29 8:58 UTC (permalink / raw)
To: Hin-Tak Leung; +Cc: ndiswrapper-general, linux-wireless
In-Reply-To: <999306.93095.qm@web23102.mail.ird.yahoo.com>
"Hin-Tak Leung" <hintak_leung@yahoo.co.uk> wrote
> Hmm, I see you have already posted to linux-wireless and already got your
> answers. Hauke has already given you the answer - your kernel tree is
> *not* 2.6.27(.0), and as it is obvious that you have 2.6.27.29-0.1, which
> is 2.6.27.29 + suse-patches. Even 2.6.27.29 is not 2.6.27(.0), but
> somewhat closer to 2.6.28. And you really have already had your answer -
> your tree is somewhat between 2.6.27 and 2.6.28, and *neither*.
>
> My suggestion would be simply to delete all the 'error: redefinition' parts
> from net/compat-2.6.28.h , because you already have them in the suse tree.
Thanx for your efforts. By the way, do I need to set CONFIG_TRACEPOINTS in the
kernel? I just see it is _not_ set in openSUSE 11.1.
> You may also need to delete something from net/compat-2.6.28.c, but that
> will happen during the linking stage (much later).
So, no need to modify compat-2.6.28.c? Does it automatically happen?
Regards
Malte
^ permalink raw reply
* Re: cannot compile compate-wirless snapshots
From: Hin-Tak Leung @ 2009-09-29 9:00 UTC (permalink / raw)
To: Malte Gell; +Cc: Hauke Mehrtens, linux-wireless
In-Reply-To: <200909291050.54388.malte.gell@gmx.de>
On Tue, Sep 29, 2009 at 9:50 AM, Malte Gell <malte.gell@gmx.de> wrote:
>
> Hauke Mehrtens <hauke@hauke-m.de> wrote
>
>
>> Does this file exists in your installation?
>> /lib/modules/`uname -r`/build/include/linux/tracepoint.h ?
>
> Yes, but, look:
>
> cd /usr/src/linux
>
> grep -i tracepoint .config
>
> # CONFIG_TRACEPOINTS is not set
>
> Do I need to set it to yes?
>
> Malte
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
No. You should not manually edit any kernel config file (the
compat-wireless module should be built against a config matching your
running kernel, not a massaged version of it) and what is in
/usr/src/linux is irrelevant , because that is not your running
kernel.
The relevant config is probably /boot/config-`uname -r`, but, please
do *not* modify it.
I already wrote - your best bet is simply deleting all the 'error
redefintion' parts from net/compat-2.6.28.h, since your kernel tree is
somewhere between 2.6.27 and 2.6.28 . (and also delete some part of
net/compat-2.6.28.c when possible later linker error arises).
^ permalink raw reply
* Re: compat-wireless tracepoint error Re: [Ndiswrapper-general] Need help to create driver for Netgear WN111v2
From: Hin-Tak Leung @ 2009-09-29 9:06 UTC (permalink / raw)
To: Malte Gell; +Cc: Hin-Tak Leung, ndiswrapper-general, linux-wireless
In-Reply-To: <200909291058.43765.malte.gell@gmx.de>
On Tue, Sep 29, 2009 at 9:58 AM, Malte Gell <malte.gell@gmx.de> wrote:
>
> "Hin-Tak Leung" <hintak_leung@yahoo.co.uk> wrote
>
>> Hmm, I see you have already posted to linux-wireless and already got your
>> answers. Hauke has already given you the answer - your kernel tree is
>> *not* 2.6.27(.0), and as it is obvious that you have 2.6.27.29-0.1, which
>> is 2.6.27.29 + suse-patches. Even 2.6.27.29 is not 2.6.27(.0), but
>> somewhat closer to 2.6.28. And you really have already had your answer -
>> your tree is somewhat between 2.6.27 and 2.6.28, and *neither*.
>>
>> My suggestion would be simply to delete all the 'error: redefinition' parts
>> from net/compat-2.6.28.h , because you already have them in the suse tree.
>
> Thanx for your efforts. By the way, do I need to set CONFIG_TRACEPOINTS in the
> kernel? I just see it is _not_ set in openSUSE 11.1.
No, do *not* modify any kernel config files. You should not do that,
as the compat modules should be compiled against a correct config, as
in a config that corresponds to how your kernel was built.
>> You may also need to delete something from net/compat-2.6.28.c, but that
>> will happen during the linking stage (much later).
>
> So, no need to modify compat-2.6.28.c? Does it automatically happen?
You may or may not see any errors at the linker stage (the LD part in
stage 2). If you get to that point without further error, then, well,
count yourself lucky and just give "make install ; make unload;
modprobe -v ar9170" a go.
^ permalink raw reply
* Re: Disassociating atheros wlan with 2.6.31
From: Kristoffer Ericson @ 2009-09-29 9:16 UTC (permalink / raw)
To: Justin P. Mattock
Cc: Stefan Lippers-Hollmann, linux-wireless,
linux-kernel@vger.kernel.org
In-Reply-To: <4ABBD170.6060702@gmail.com>
On Thu, 24 Sep 2009 13:07:12 -0700
"Justin P. Mattock" <justinmattock@gmail.com> wrote:
> Stefan Lippers-Hollmann wrote:
> > Hi
> >
> > CCing linux-wireless@vger.kernel.org, as it's not very likely to get
> > noticed here by wireless developers.
> >
> > On Thursday 24 September 2009, Justin P. Mattock wrote:
> >
> >> Kristoffer Ericson wrote:
> >>
> >>> Greetings,
> >>>
> >>> When moving from vanilla 2.6.30->2.6.31 I noticed that I get dissasociated from
> >>> my wlan hub with regular intervalls. This did not happen on 2.6.30.
> >>> I cant see any pattern aside from that it happens at regular intervalls
> >>> (around 10-15mins). It works again when I re-identifies myself.
> >>>
> >>> Got an Asus 1000HE with Atheros chipset.
> >>> Havent had time to bisect it, just wanted to check
> >>> if this is an known issue. Ive ruled out faulty wlan hub
> >>> since everything works fine when going back to 2.6.30.
> >>>
> >>> nothing much on dmesg:
> >>> uhci_hcd 0000:00:1d.1: UHCI Host Controller
> >>> uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
> >>> uhci_hcd 0000:00:1d.1: irq 19, io base 0x0000d480
> >>> usb usb3: configuration #1 chosen from 1 choice
> >>> hub 3-0:1.0: USB hub found
> >>> hub 3-0:1.0: 2 ports detected
> >>> uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
> >>> uhci_hcd 0000:00:1d.2: setting latency timer to 64
> >>> uhci_hcd 0000:00:1d.2: UHCI Host Controller
> >>> uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
> >>> uhci_hcd 0000:00:1d.2: irq 18, io base 0x0000d800
> >>> usb usb4: configuration #1 chosen from 1 choice
> >>> hub 4-0:1.0: USB hub found
> >>> hub 4-0:1.0: 2 ports detected
> >>> uhci_hcd 0000:00:1d.3: PCI INT D -> GSI 16 (level, low) -> IRQ 16
> >>> uhci_hcd 0000:00:1d.3: setting latency timer to 64
> >>> uhci_hcd 0000:00:1d.3: UHCI Host Controller
> >>> uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5
> >>> uhci_hcd 0000:00:1d.3: irq 16, io base 0x0000d880
> >>> usb usb5: configuration #1 chosen from 1 choice
> >>> hub 5-0:1.0: USB hub found
> >>> hub 5-0:1.0: 2 ports detected
> >>> input: ETPS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input7
> >>> usb 1-4: new high speed USB device using ehci_hcd and address 3
> >>> usb 1-4: configuration #1 chosen from 1 choice
> >>> hub 1-4:1.0: USB hub found
> >>> hub 1-4:1.0: 4 ports detected
> >>> usb 1-5: new high speed USB device using ehci_hcd and address 4
> >>> usb 1-5: configuration #1 chosen from 1 choice
> >>> usb 1-8: new high speed USB device using ehci_hcd and address 6
> >>> usb 1-8: configuration #1 chosen from 1 choice
> >>> Initializing USB Mass Storage driver...
> >>> scsi4 : SCSI emulation for USB Mass Storage devices
> >>> usbcore: registered new interface driver usb-storage
> >>> USB Mass Storage support registered.
> >>> usb-storage: device found at 4
> >>> usb-storage: waiting for device to settle before scanning
> >>> HDA Intel 0000:00:1b.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
> >>> HDA Intel 0000:00:1b.0: setting latency timer to 64
> >>> usb 2-2: new full speed USB device using uhci_hcd and address 2
> >>> ath9k 0000:01:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
> >>> ath9k 0000:01:00.0: setting latency timer to 64
> >>> usb 2-2: configuration #1 chosen from 1 choice
> >>> input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/input/input8
> >>> usbcore: registered new interface driver usbserial
> >>> USB Serial support registered for generic
> >>> usb 5-1: new full speed USB device using uhci_hcd and address 2
> >>> usb 5-1: configuration #1 chosen from 1 choice
> >>> usb 1-4.1: new full speed USB device using ehci_hcd and address 7
> >>> ath: EEPROM regdomain: 0x60
> >>> ath: EEPROM indicates we should expect a direct regpair map
> >>> ath: Country alpha2 being used: 00
> >>> ath: Regpair used: 0x60
> >>> Bluetooth: Core ver 2.15
> >>> NET: Registered protocol family 31
> >>> Bluetooth: HCI device and connection manager initialized
> >>> Bluetooth: HCI socket layer initialized
> >>> Bluetooth: Generic Bluetooth USB driver ver 0.5
> >>> usb 1-4.1: configuration #1 chosen from 1 choice
> >>> usb 1-4.2: new low speed USB device using ehci_hcd and address 8
> >>> usb 1-4.2: configuration #1 chosen from 1 choice
> >>> usb 1-4.4: new low speed USB device using ehci_hcd and address 9
> >>> usbcore: registered new interface driver hiddev
> >>> input: HID 04d9:1203 as /devices/pci0000:00/0000:00:1d.7/usb1/1-4/1-4.2/1-4.2:1.0/input/input9
> >>> generic-usb 0003:04D9:1203.0001: input,hidraw0: USB HID v1.11 Keyboard [HID 04d9:1203] on usb-0000:00:1d.7-4.2/input0
> >>> input: HID 04d9:1203 as /devices/pci0000:00/0000:00:1d.7/usb1/1-4/1-4.2/1-4.2:1.1/input/input10
> >>> generic-usb 0003:04D9:1203.0002: input,hidraw1: USB HID v1.11 Device [HID 04d9:1203] on usb-0000:00:1d.7-4.2/input1
> >>> usbcore: registered new interface driver usbhid
> >>> usbhid: v2.6:USB HID core driver
> >>> usb 1-4.4: configuration #1 chosen from 1 choice
> >>> input: B16_b_02 USB-PS/2 Optical Mouse as /devices/pci0000:00/0000:00:1d.7/usb1/1-4/1-4.4/1-4.4:1.0/input/input11
> >>> generic-usb 0003:046D:C025.0003: input,hidraw2: USB HID v1.10 Mouse [B16_b_02 USB-PS/2 Optical Mouse] on usb-0000:00:1d.7-4.4/input0
> >>> usbcore: registered new interface driver btusb
> >>> usbcore: registered new interface driver usbserial_generic
> >>> usbserial: USB Serial Driver core
> >>> USB Serial support registered for GSM modem (1-port)
> >>> option 2-2:1.0: GSM modem (1-port) converter detected
> >>> usb 2-2: GSM modem (1-port) converter now attached to ttyUSB0
> >>> option 2-2:1.1: GSM modem (1-port) converter detected
> >>> usb 2-2: GSM modem (1-port) converter now attached to ttyUSB1
> >>> usbcore: registered new interface driver option
> >>> option: v0.7.2:USB Driver for GSM modems
> >>> USB Serial support registered for pl2303
> >>> pl2303 1-4.1:1.0: pl2303 converter detected
> >>> usb 1-4.1: pl2303 converter now attached to ttyUSB2
> >>> usbcore: registered new interface driver pl2303
> >>> pl2303: Prolific PL2303 USB to serial adaptor driver
> >>> phy0: Selected rate control algorithm 'ath9k_rate_control'
> >>> Registered led device: ath9k-phy0::radio
> >>> Registered led device: ath9k-phy0::assoc
> >>> Registered led device: ath9k-phy0::tx
> >>> Registered led device: ath9k-phy0::rx
> >>> phy0: Atheros AR9280 MAC/BB Rev:2 AR5133 RF Rev:d0: mem=0xf8880000, irq=19
> >>> scsi 4:0:0:0: Direct-Access Single Flash Reader 1.00 PQ: 0 ANSI: 0
> >>> sd 4:0:0:0: Attached scsi generic sg1 type 0
> >>> sd 4:0:0:0: [sdb] 15954944 512-byte logical blocks: (8.16 GB/7.60 GiB)
> >>> usb-storage: device scan complete
> >>> sd 4:0:0:0: [sdb] Write Protect is off
> >>> sd 4:0:0:0: [sdb] Mode Sense: 03 00 00 00
> >>> sd 4:0:0:0: [sdb] Assuming drive cache: write through
> >>> sd 4:0:0:0: [sdb] Assuming drive cache: write through
> >>> sdb: sdb1
> >>> sd 4:0:0:0: [sdb] Assuming drive cache: write through
> >>> sd 4:0:0:0: [sdb] Attached SCSI removable disk
> >>> EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
> >>> EXT3 FS on sda1, internal journal
> >>> Bluetooth: L2CAP ver 2.13
> >>> Bluetooth: L2CAP socket layer initialized
> >>> Bluetooth: SCO (Voice Link) ver 0.6
> >>> Bluetooth: SCO socket layer initialized
> >>> Bluetooth: BNEP (Ethernet Emulation) ver 1.3
> >>> Bridge firewalling registered
> >>> Bluetooth: RFCOMM TTY layer initialized
> >>> Bluetooth: RFCOMM socket layer initialized
> >>> Bluetooth: RFCOMM ver 1.11
> >>> ATL1E 0000:03:00.0: irq 27 for MSI/MSI-X
> >>> fuse init (API version 7.12)
> >>> ip_tables: (C) 2000-2006 Netfilter Core Team
> >>> nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
> >>> CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use
> >>> nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module option or
> >>> sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
> >>> wlan0: authenticate with AP 00:14:7c:ae:d1:90
> >>> wlan0: authenticated
> >>> wlan0: associate with AP 00:14:7c:ae:d1:90
> >>> wlan0: RX AssocResp from 00:14:7c:ae:d1:90 (capab=0x431 status=0 aid=5)
> >>> wlan0: associated
> >>> PPP generic driver version 2.4.2
> >>> NET: Registered protocol family 10
> >>> lo: Disabled Privacy Extensions
> >>> ADDRCONF(NETDEV_UP): eth0: link is not ready
> >>> PPP BSD Compression module registered
> >>> PPP Deflate Compression module registered
> >>> wlan0: no IPv6 routers present
> >>> CE: hpet increasing min_delta_ns to 15000 nsec
> >>> wlan0: no probe response from AP 00:14:7c:ae:d1:90 - disassociating
> >>> wlan0: authenticate with AP 00:14:7c:ae:d1:90
> >>> wlan0: authenticated
> >>> wlan0: associate with AP 00:14:7c:ae:d1:90
> >>> wlan0: RX AssocResp from 00:14:7c:ae:d1:90 (capab=0x431 status=0 aid=5)
> >>> wlan0: associated
> >>> wlan0: authenticate with AP 00:14:7c:ae:d1:90
> >>> wlan0: authenticated
> >>> wlan0: associate with AP 00:14:7c:ae:d1:90
> >>> wlan0: RX AssocResp from 00:14:7c:ae:d1:90 (capab=0x431 status=0 aid=5)
> >>> wlan0: associated
> >>> [kristoffer@boggieman wine.git]$
> >>>
> >>>
> >>>
> >>>
> >> yeah I'm seeing this with my macbook pro(ath9k)
> >> while streaming music, all of a sudden things just crap out.
> >> (not sure if this is why, or something else).
> >>
> >> Justin P. Mattock
> >>
> >
> > I'm getting similar reports for iwl3945 and 2.6.31.[01], but can't confirm
> > this on my own (non-iwl{3945,agn}, non-ath9k) hardware yet.
> >
> > Regards
> > Stefan Lippers-Hollmann
> >
> >
> I don't mind doing a bisect from 30 - present, but first I need to
> do some other stuff.
Got any updates on this? Im stuck in doing other kernel stuff and has
left 2.6.31 currently since I need it for internet sharing (through wlan0).
Its a real pain having it drop every 15mins.
>
> Justin P. Mattock
--
Kristoffer Ericson <kristoffer.ericson@gmail.com>
^ permalink raw reply
* Re: bleeding edge ar9170usb: Fritz N USB support?
From: Hin-Tak Leung @ 2009-09-29 9:14 UTC (permalink / raw)
To: Malte Gell; +Cc: linux-wireless
In-Reply-To: <200909291014.57777.malte.gell@gmx.de>
On Tue, Sep 29, 2009 at 9:14 AM, Malte Gell <malte.gell@gmx.de> wrote:
> Hello!
>
> At
>
> http://linuxwireless.org/en/users/Drivers/ar9170
>
> I read support for the 802.11n Fritz N USB will be until kernel 2.6.32.
>
> So, I wonder is this USB stick already supported in the bleeding edge compat-
> wireless-2.6?
sigh. bleeding edge compat-wireless is ahead of Linus' tree (I already
told you, and probably more than once).
^ permalink raw reply
* Re: [PATCH 2/3] iwmc3200wifi: select IWMC3200TOP in Kconfig
From: Zhu Yi @ 2009-09-29 9:22 UTC (permalink / raw)
To: Winkler, Tomas
Cc: davem@davemloft.net, linville@tuxdriver.com,
netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
linux-mmc@vger.kernel.org, Perez-Gonzalez, Inaky, Kao, Cindy H,
Cohen, Guy, Rindjunsky, Ron
In-Reply-To: <1253662724-16497-3-git-send-email-tomas.winkler@intel.com>
On Wed, 2009-09-23 at 07:38 +0800, Winkler, Tomas wrote:
> iwmc3200wifi requires iwmc3200top for its operation
>
> Signed-off-by: Tomas Winkler <tomas.winkler@intel.com>
Acked-by: Zhu Yi <yi.zhu@intel.com>
Thanks,
-yi
> ---
> drivers/net/wireless/iwmc3200wifi/Kconfig | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/net/wireless/iwmc3200wifi/Kconfig b/drivers/net/wireless/iwmc3200wifi/Kconfig
> index c62da43..69faaf1 100644
> --- a/drivers/net/wireless/iwmc3200wifi/Kconfig
> +++ b/drivers/net/wireless/iwmc3200wifi/Kconfig
> @@ -3,6 +3,7 @@ config IWM
> depends on MMC && WLAN_80211 && EXPERIMENTAL
> depends on CFG80211
> select FW_LOADER
> + select IWMC3200TOP
> help
> The Intel Wireless Multicomm 3200 hardware is a combo
> card with GPS, Bluetooth, WiMax and 802.11 radios. It
^ permalink raw reply
* Re: compat-wireless tracepoint error Re: [Ndiswrapper-general] Need help to create driver for Netgear WN111v2
From: Malte Gell @ 2009-09-29 9:45 UTC (permalink / raw)
To: Hin-Tak Leung, ndiswrapper-general; +Cc: linux-wireless
In-Reply-To: <3ace41890909290206g3019a9cbv29048837804f830@mail.gmail.com>
"Hin-Tak Leung" <hintak.leung@gmail.com> wrote
> > So, no need to modify compat-2.6.28.c? Does it automatically happen?
>
> You may or may not see any errors at the linker stage (the LD part in
> stage 2). If you get to that point without further error, then, well,
> count yourself lucky and just give "make install ; make unload;
> modprobe -v ar9170" a go.
Ho ho ;-) I got a lot of warnings like this:
include/linux/tracepoint.h:86:1: warning: this is the location of the
previous definition
But, it DID compile! Thanx a lot.
To be sure I did a find . -name "*.ko" and got these modules:
./drivers/net/wireless/ath/ath.ko
./net/rfkill/rfkill_backport.ko
./net/wireless/cfg80211.ko
./net/mac80211/mac80211.ko
I just wonder, where is ar9170usb !? I did ./scripts/driver-select ar9170
Malte
^ permalink raw reply
* Re: compat-wireless tracepoint error Re: [Ndiswrapper-general] Need help to create driver for Netgear WN111v2
From: Hin-Tak Leung @ 2009-09-29 10:28 UTC (permalink / raw)
To: Malte Gell; +Cc: linux-wireless
In-Reply-To: <200909291145.35972.malte.gell@gmx.de>
On Tue, Sep 29, 2009 at 10:45 AM, Malte Gell <malte.gell@gmx.de> wrote:
>
> "Hin-Tak Leung" <hintak.leung@gmail.com> wrote
>
>> > So, no need to modify compat-2.6.28.c? Does it automatically happen?
>>
>> You may or may not see any errors at the linker stage (the LD part in
>> stage 2). If you get to that point without further error, then, well,
>> count yourself lucky and just give "make install ; make unload;
>> modprobe -v ar9170" a go.
>
> Ho ho ;-) I got a lot of warnings like this:
>
> include/linux/tracepoint.h:86:1: warning: this is the location of the
> previous definition
>
> But, it DID compile! Thanx a lot.
>
> To be sure I did a find . -name "*.ko" and got these modules:
>
> ./drivers/net/wireless/ath/ath.ko
> ./net/rfkill/rfkill_backport.ko
> ./net/wireless/cfg80211.ko
> ./net/mac80211/mac80211.ko
>
> I just wonder, where is ar9170usb !? I did ./scripts/driver-select ar9170
>
> Malte
>
Argh... try changing this line in config.mk
ifndef CONFIG_COMPAT_WIRELESS_28
to ...27.
apparently it is disabled below 2.6.28. but then, yours is somewhere between.
------------
commit 13e9384e59b2cadaef7468f1417b9a1327419c89
Author: Luis R. Rodriguez <lrodriguez@atheros.com>
Date: Tue Jul 21 14:43:15 2009 -0700
ar9170 works needs more compat work for 2.6.27
We leave it only enabled for >= 2.6.28,
usb_hcd_unlink_urb() is used within usb_poison_urb()
and although it is available on 2.6.27 its not exported
and cannot be re-implemented. If we figure out a way
to drop the urb from the hardware queue as usb_hcd_unlink_urb()
does then we can backport this.
Also I think we need to backport usb_kill_urb_queue().
Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
------------
^ permalink raw reply
* Re: Firmware versioning best practices
From: Tomas Winkler @ 2009-09-29 10:45 UTC (permalink / raw)
To: Holger Schurig
Cc: Luis R. Rodriguez, linux-wireless, reinette chatre, Kalle Valo,
Johannes Berg, Christian Lamparter, Bob Copeland
In-Reply-To: <200909290859.25075.hs4233@mail.mn-solutions.de>
On Tue, Sep 29, 2009 at 8:59 AM, Holger Schurig
<hs4233@mail.mn-solutions.de> wrote:
>> Or shall we have the same firmware filename and simply query
>> the firmware for a map of capabilities? Any other ideas?
>
> Don't put the version into the filename. This is not a common
> practice for Linux / BSD / whatever systems. Usually you have
> a "kmail" file, not a kmail3.5, kmail4.0 and kmail4.2 file.
I think in this context libyyy.so.x.y.z is better analogy. firmware is
not an executable
What is the reasoning behind this common practice?
> Versions or capability maps can be stored inside the firmware and
> queried at load time. E.g. the libertas driver does it that way.
It's only check if it fits but cannot fall back to an older version.
.
>
> If you make your firmware redistributable (which I recommend),
> the version will also be stored in the package metadata, e.g.
> the rpm or deb file and the infrastructure for rpm/yum deb/apt.
>
> --
> http://www.holgerschurig.de
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
Thanks
Tomas
^ permalink raw reply
* Re: Firmware versioning best practices
From: Holger Schurig @ 2009-09-29 11:01 UTC (permalink / raw)
To: Tomas Winkler; +Cc: Luis R. Rodriguez, linux-wireless
In-Reply-To: <1ba2fa240909290345k776826a6jc692d9d8dfe7577@mail.gmail.com>
> > Don't put the version into the filename. This is not a common
> > practice for Linux / BSD / whatever systems. Usually you have
> > a "kmail" file, not a kmail3.5, kmail4.0 and kmail4.2 file.
>
> I think in this context libyyy.so.x.y.z is better analogy.
> firmware is not an executable What is the reasoning behind this
> common practice?
There's no version of the library in the file-name, but the
version of the API. So if the API changes, and might break users
of the API, you increase the filename.
But you won't have a libc-2.3.6.so file. Instead you have a
package "libc6_2.3.6.ds1-13etch9_i386.deb" which contains the
file libc.so.6.
--
http://www.holgerschurig.de
^ permalink raw reply
* Re: compat-wireless tracepoint error Re: [Ndiswrapper-general] Need help to create driver for Netgear WN111v2
From: Malte Gell @ 2009-09-29 11:07 UTC (permalink / raw)
To: Hin-Tak Leung; +Cc: linux-wireless
In-Reply-To: <3ace41890909290328l14620ed6o4939488e268d76a3@mail.gmail.com>
"Hin-Tak Leung" <hintak.leung@gmail.com> wrote
> CONFIG_COMPAT_WIRELESS_28
>
Jep, changed to 27, but, did not compile......:
/home/malte_gell/download/src/wifi/compat-
wireless-2009-09-29/drivers/net/wireless/ath/ar9170/usb.c: In function
‘ar9170_usb_cancel_urbs’:
/home/malte_gell/download/src/wifi/compat-
wireless-2009-09-29/drivers/net/wireless/ath/ar9170/usb.c:380: error: implicit
declaration of function ‘usb_poison_anchored_urbs’
make[5]: *** [/home/malte_gell/download/src/wifi/compat-
wireless-2009-09-29/drivers/net/wireless/ath/ar9170/usb.o] Fehler 1
make[4]: *** [/home/malte_gell/download/src/wifi/compat-
wireless-2009-09-29/drivers/net/wireless/ath/ar9170] Fehler 2
make[3]: *** [/home/malte_gell/download/src/wifi/compat-
wireless-2009-09-29/drivers/net/wireless/ath] Fehler 2
make[2]: *** [/home/malte_gell/download/src/wifi/compat-
wireless-2009-09-29/drivers/net/wireless] Fehler 2
make[1]: *** [_module_/home/malte_gell/download/src/wifi/compat-
wireless-2009-09-29] Fehler 2
make[1]: Leaving directory `/usr/src/linux-2.6.27.29-0.1'
make: *** [modules] Fehler 2
^ permalink raw reply
* scan_request->nr_ssids never 0 ?
From: Holger Schurig @ 2009-09-29 13:18 UTC (permalink / raw)
To: linux-wireless
Even when I do an "iw xxx scan trigger", scan_request->nr_ssids
is always 1 in my driver.
Is this a bug or a feature?
However, scan_request->ssids[0].ssid_len is 0.
So to ask my firmware for an SSID scan, I need to do
if (req->n_ssids && req->ssid[0].ssid_len)
instead of simply
if (req->n_ssids)
--
http://www.holgerschurig.de
^ permalink raw reply
* [PATCH] rt2x00: Thrustmaster FunAccess WIFI USB and rt73usb
From: Ivo van Doorn @ 2009-09-29 13:37 UTC (permalink / raw)
To: John Linville, linux-wireless@vger.kernel.org, szalat, users
From: Michal Szalata <szalat@gmail.com>
Thrustmaster FunAccess WIFI USB works with rt73usb with little
modification of rt73usb.c.
Tested with version 2.3.0 of driver.
Signed-off-by: Michal Szalata <szalat@gmail.com>
Signed-off-by: Ivo van Doorn <IvDoorn@gmail.com>
---
diff --git a/drivers/net/wireless/rt2x00/rt73usb.c b/drivers/net/wireless/rt2x00/rt73usb.c
index 1cbd9b4..b8f5ee3 100644
--- a/drivers/net/wireless/rt2x00/rt73usb.c
+++ b/drivers/net/wireless/rt2x00/rt73usb.c
@@ -2381,6 +2381,7 @@ static struct usb_device_id rt73usb_device_table[] = {
/* Huawei-3Com */
{ USB_DEVICE(0x1472, 0x0009), USB_DEVICE_DATA(&rt73usb_ops) },
/* Hercules */
+ { USB_DEVICE(0x06f8, 0xe002), USB_DEVICE_DATA(&rt73usb_ops) },
{ USB_DEVICE(0x06f8, 0xe010), USB_DEVICE_DATA(&rt73usb_ops) },
{ USB_DEVICE(0x06f8, 0xe020), USB_DEVICE_DATA(&rt73usb_ops) },
/* Linksys */
^ permalink raw reply related
* Re: scan_request->nr_ssids never 0 ?
From: Johannes Berg @ 2009-09-29 14:04 UTC (permalink / raw)
To: Holger Schurig; +Cc: linux-wireless
In-Reply-To: <200909291518.46655.hs4233@mail.mn-solutions.de>
[-- Attachment #1: Type: text/plain, Size: 536 bytes --]
On Tue, 2009-09-29 at 15:18 +0200, Holger Schurig wrote:
> Even when I do an "iw xxx scan trigger", scan_request->nr_ssids
> is always 1 in my driver.
>
> Is this a bug or a feature?
# iw wlan0 scan trigger passive
> However, scan_request->ssids[0].ssid_len is 0.
>
> So to ask my firmware for an SSID scan, I need to do
>
> if (req->n_ssids && req->ssid[0].ssid_len)
>
> instead of simply
>
> if (req->n_ssids)
No. You need to ask it to probe for the wildcard SSID, which is 0 bytes
long.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
^ permalink raw reply
* RE: [rt2x00-users] [PATCH] rt2x00: Thrustmaster FunAccess WIFI USB and rt73usb
From: Genar Codina @ 2009-09-29 15:21 UTC (permalink / raw)
To: rt2x00 Users List, John Linville, linux-wireless@vger.kernel.org,
szalat
In-Reply-To: <200909291537.54334.IvDoorn@gmail.com>
Hello,
I have also tested the rt73usb which is included in the new 2.6.31 kernel (modinfo rt73usb gives the version "2.3.0"), in mode Master, using hostapd (version 0.6.9) and it works OK.
Regards,
-----Mensaje original-----
De: users-bounces@rt2x00.serialmonkey.com [mailto:users-bounces@rt2x00.serialmonkey.com] En nombre de Ivo van Doorn
Enviado el: martes, 29 de septiembre de 2009 15:38
Para: John Linville; linux-wireless@vger.kernel.org; szalat; users@rt2x00.serialmonkey.com
Asunto: [rt2x00-users] [PATCH] rt2x00: Thrustmaster FunAccess WIFI USB and rt73usb
From: Michal Szalata <szalat@gmail.com>
Thrustmaster FunAccess WIFI USB works with rt73usb with little
modification of rt73usb.c.
Tested with version 2.3.0 of driver.
Signed-off-by: Michal Szalata <szalat@gmail.com>
Signed-off-by: Ivo van Doorn <IvDoorn@gmail.com>
---
diff --git a/drivers/net/wireless/rt2x00/rt73usb.c b/drivers/net/wireless/rt2x00/rt73usb.c
index 1cbd9b4..b8f5ee3 100644
--- a/drivers/net/wireless/rt2x00/rt73usb.c
+++ b/drivers/net/wireless/rt2x00/rt73usb.c
@@ -2381,6 +2381,7 @@ static struct usb_device_id rt73usb_device_table[] = {
/* Huawei-3Com */
{ USB_DEVICE(0x1472, 0x0009), USB_DEVICE_DATA(&rt73usb_ops) },
/* Hercules */
+ { USB_DEVICE(0x06f8, 0xe002), USB_DEVICE_DATA(&rt73usb_ops) },
{ USB_DEVICE(0x06f8, 0xe010), USB_DEVICE_DATA(&rt73usb_ops) },
{ USB_DEVICE(0x06f8, 0xe020), USB_DEVICE_DATA(&rt73usb_ops) },
/* Linksys */
_______________________________________________
users mailing list
users@rt2x00.serialmonkey.com
http://rt2x00.serialmonkey.com/mailman/listinfo/users_rt2x00.serialmonkey.com
^ permalink raw reply related
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox