Re: [zd1211-devs] Vendor driver v2.16.0.0
Testing 3CRUSB10075 (6891:a727) with firmware 2.16.0.0 from Uli's git tree, kernel 2.6.19.1, and zd1211rw.git, the following are working for me: cold boot with device plugged in cold plugin warm rmmod/insmod warm reboot un/plugging device without rmmod/insmod. The warm rmmod/insmod and un/plugging cause some confusion for wpa_supplicant, but I think this is more on the supplicant side than the driver side. Killing and restarting wpa_supplicant works fine. I am sometimes seeing errors related to the LED control, but cannot reproduce them reliably and don't have the exact error message handy at the moment. Thanks for the great work! Will On 12/25/06, Ulrich Kunitz <[EMAIL PROTECTED]> wrote: On 06-12-25 11:40 Ulrich Kunitz wrote: > probe function. It works here with 2.6.19.2 + unrelated > softmac-patches. The interesting part is it works also with the Sorry, there has been a type. I meant the kernel version 2.6.19.1. -- Uli Kunitz - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Zd1211-devs mailing list - http://zd1211.ath.cx/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV___ Zd1211-devs mailing list - http://zd1211.ath.cx/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] Vendor driver v2.16.0.0
On 06-12-25 11:40 Ulrich Kunitz wrote: > probe function. It works here with 2.6.19.2 + unrelated > softmac-patches. The interesting part is it works also with the Sorry, there has been a type. I meant the kernel version 2.6.19.1. -- Uli Kunitz - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Zd1211-devs mailing list - http://zd1211.ath.cx/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] Vendor driver v2.16.0.0
Hi,
> > Matthieu CASTET wrote:
> >> BTW doing the reset in probe seems to work with new firmware :
> >> http://castet.matthieu.free.fr/tmp/zd_reset.diff
I made my own research here and added usb_reset_device to the
probe function. It works here with 2.6.19.2 + unrelated
softmac-patches. The interesting part is it works also with the
old 2_13_0_0 firmware.
I would like everybody, who had the reboot/reset problems to test
it, so that we are sure, we have nailed the problem.
Cheers,
Uli
[PATCH] zd1211rw: Reset device in the probe call
This resets the device in the probe call. It does work with
2.6.19.2 including the softmac patches. It might fix the
reboot/reset problems a lot of people reported.
Signed-off-by: Ulrich Kunitz <[EMAIL PROTECTED]>
---
zd_usb.c |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/zd_usb.c b/zd_usb.c
index 1b8ea88..7ec2dd3 100644
--- a/zd_usb.c
+++ b/zd_usb.c
@@ -922,6 +922,8 @@ static int probe(struct usb_interface *i
goto error;
}
+ usb_reset_device(interface_to_usbdev(intf));
+
netdev = zd_netdev_alloc(intf);
if (netdev == NULL) {
r = -ENOMEM;
--
Uli Kunitz
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
Zd1211-devs mailing list - http://zd1211.ath.cx/
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] Vendor driver v2.16.0.0
On Sat, 23 Dec 2006 09:23:47 -0500, Daniel Drake wrote: > Matthieu CASTET wrote: >> BTW doing the reset in probe seems to work with new firmware : >> http://castet.matthieu.free.fr/tmp/zd_reset.diff > > What do you mean by 'new firmware'? Firmware for 2.16.0.0 > Does this work on all of: > cold plugin yes > warm rmmod/insmod yes > warm reboot I don't try it yet. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Zd1211-devs mailing list - http://zd1211.ath.cx/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] Vendor driver v2.16.0.0
Matthieu CASTET wrote: > BTW doing the reset in probe seems to work with new firmware : > http://castet.matthieu.free.fr/tmp/zd_reset.diff What do you mean by 'new firmware'? Does this work on all of: cold plugin warm rmmod/insmod warm reboot Daniel - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Zd1211-devs mailing list - http://zd1211.ath.cx/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] Vendor driver v2.16.0.0
BTW doing the reset in probe seems to work with new firmware : http://castet.matthieu.free.fr/tmp/zd_reset.diff Matthieu - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Zd1211-devs mailing list - http://zd1211.ath.cx/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] Vendor driver v2.16.0.0
On Sat, 23 Dec 2006 10:10:56 +0100, Hans Dingemans wrote: > I'm not the expert here, but wouldn't it be a good idea to make sure > disconnect() is called on both reset and reboot (by root), and all other > "exit" scenario's possible. That then would be a "clean" exit, not relying > on how other components in the environment are acting? The problem is that we can't rely in all case in a clean exit solution. For example if you kernel panic and reboot, the kernel will reboot without notifying the drivers. Same problem if you use the hardware reset. I am not even certain that Linux call driver disconnect on normal reboot. All sane device has a way (often reset) to go from an unknow state to a know state. The best solution should be to find a way to do the "black magic" for reseting the device in probe and not in disconnect. Matthieu - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Zd1211-devs mailing list - http://zd1211.ath.cx/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] Vendor driver v2.16.0.0
Uli, it seems we are going in circles here. As I pointed out three months ago, it is simply _not_ true that you can rely on host controllers to cycle the power of their USB devices during reboot. Lots of machines do not do this, and the machines that do can have USB-Hub's connected which in my experience most of the time just keep the power on all USB-devices connected. For instance, I currently have a (not really down-end priced, excellent performing) Gigabyte K8NS Ultra 939 board that keeps all its on-board USB ports powered, _even_ after a shutdown. You really have to pull out the mains cord to get the USB ports powerless... So, regardless whether it is against any standard or not, if the zd1211rw driver is not dealing with this fact of life, a lot of users will keep these reboot/reset/reload problems, and that would be a shame for a driver that apart from this works beautifully. I'm not the expert here, but wouldn't it be a good idea to make sure disconnect() is called on both reset and reboot (by root), and all other "exit" scenario's possible. That then would be a "clean" exit, not relying on how other components in the environment are acting? You nor Daniel would need extensive bug logs for that, which then are so voluminous they cannot be handled, nor would you need to be able to reproduce the bug on your own machines. Not sure what the consequences of my suggestion are, just trying to contribute... Best regards to all! > -Oorspronkelijk bericht- > Van: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Namens Uli Kunitz > Verzonden: zaterdag 23 december 2006 0:38 > Aan: Matthieu CASTET > CC: zd1211-devs@lists.sourceforge.net > Onderwerp: Re: [zd1211-devs] Vendor driver v2.16.0.0 > > > > Am 22.12.2006 um 23:59 schrieb Matthieu CASTET: > > > On Fri, 22 Dec 2006 14:10:08 -0500, Daniel Drake wrote: > > > >> Matthieu CASTET wrote: > >>> BTW if I remove usb_reset_device in zd1211rw disconnect, the > >>> firmware > >>> upload fails. This doesn't seem woorking :( > >> > >> That's why the reset is there. The vendor driver does it the same > >> way. > >> > > Yes but in case of reset/reboot disconnect is not called. So I > > failed to > > see how the firmware will recover from these cases if it is not > > able to > > recover a missing reset in disconnect. > > Do you mean reset or reboot? In the reset case disconnect() will not > be called. In the reboot case, defined by calling reboot as root, I > would expect it to happen. However it shouldn't matter because the > host controller should cycle the power during reboot. > > My current assumption is, that the bug appears, if disconnect() is > not called and during system start the power for the device is not > cycled. I would like to see that proven, however I have never seen > the bug, because all my systems are cycling the USB power during boot. > > Regards, > > Uli > > -- > Uli Kunitz > > > > > -- > --- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the > chance to share your opinions on IT & business topics through > brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge &CID=DEVDEV ___ Zd1211-devs mailing list - http://zd1211.ath.cx/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Zd1211-devs mailing list - http://zd1211.ath.cx/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] Vendor driver v2.16.0.0
Am 22.12.2006 um 23:59 schrieb Matthieu CASTET: > On Fri, 22 Dec 2006 14:10:08 -0500, Daniel Drake wrote: > >> Matthieu CASTET wrote: >>> BTW if I remove usb_reset_device in zd1211rw disconnect, the >>> firmware >>> upload fails. This doesn't seem woorking :( >> >> That's why the reset is there. The vendor driver does it the same >> way. >> > Yes but in case of reset/reboot disconnect is not called. So I > failed to > see how the firmware will recover from these cases if it is not > able to > recover a missing reset in disconnect. Do you mean reset or reboot? In the reset case disconnect() will not be called. In the reboot case, defined by calling reboot as root, I would expect it to happen. However it shouldn't matter because the host controller should cycle the power during reboot. My current assumption is, that the bug appears, if disconnect() is not called and during system start the power for the device is not cycled. I would like to see that proven, however I have never seen the bug, because all my systems are cycling the USB power during boot. Regards, Uli -- Uli Kunitz - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Zd1211-devs mailing list - http://zd1211.ath.cx/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] Vendor driver v2.16.0.0
On Fri, 22 Dec 2006 14:10:08 -0500, Daniel Drake wrote: > Matthieu CASTET wrote: >> BTW if I remove usb_reset_device in zd1211rw disconnect, the firmware >> upload fails. This doesn't seem woorking :( > > That's why the reset is there. The vendor driver does it the same way. > Yes but in case of reset/reboot disconnect is not called. So I failed to see how the firmware will recover from these cases if it is not able to recover a missing reset in disconnect. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Zd1211-devs mailing list - http://zd1211.ath.cx/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] Vendor driver v2.16.0.0
Matthieu CASTET wrote: > BTW if I remove usb_reset_device in zd1211rw disconnect, the firmware > upload fails. This doesn't seem woorking :( That's why the reset is there. The vendor driver does it the same way. Daniel - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Zd1211-devs mailing list - http://zd1211.ath.cx/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] Vendor driver v2.16.0.0
On Thu, 21 Dec 2006 10:43:11 -0500, Daniel Drake wrote: > Hi, Hi, > > The ZD1211 download page has been removed from Atheros.com, but ZyDAS > sent me a new driver release. > > You can download it from: > > http://dsd.object4.net/zd1211-vendor/releases/ > > Large packet support is now disabled by default due to the reboot/module > reload problems that the large packet firmware introduces. There are > some other small changes as well. > Great, I will try it. BTW if I remove usb_reset_device in zd1211rw disconnect, the firmware upload fails. This doesn't seem woorking :( Matthieu - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Zd1211-devs mailing list - http://zd1211.ath.cx/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] Vendor driver v2.16.0.0
William Keaney wrote: > This tries to include linux/config.h, which no longer exists in 2.6.19. Sorry, should have mentioned: I'm not supporting this in any way, if it's broken it is your problem not mine :) Daniel - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Zd1211-devs mailing list - http://zd1211.ath.cx/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] Vendor driver v2.16.0.0
http://dsd.object4.net/zd1211-vendor/releases/ Large packet support is now disabled by default due to the reboot/module reload problems that the large packet firmware introduces. There are some other small changes as well. Daniel This tries to include linux/config.h, which no longer exists in 2.6.19. I got around this by changing the '#include ' to '#include ' in src/zd1205.c, src/zd1205_proc.c and src/zd1211.c. However, make still fails with: [EMAIL PROTECTED] ~/build/ZD1211LnxDrv_2_16_0_0 $ make make both make[1]: Entering directory `/home/ubrpngn/build/ZD1211LnxDrv_2_16_0_0' make clean make[2]: Entering directory `/home/ubrpngn/build/ZD1211LnxDrv_2_16_0_0' rm -rf .tmp_versions .*.cmd *.ko *.mod.c *.mod.o *.o src/*.o src/.*.o.cmd menudbg apdbg winevl_iface make[2]: Leaving directory `/home/ubrpngn/build/ZD1211LnxDrv_2_16_0_0' make ZD1211REV_B=0 make[2]: Entering directory `/home/ubrpngn/build/ZD1211LnxDrv_2_16_0_0' /lib/modules/2.6.19-emission1/build /home/ubrpngn/build/ZD1211LnxDrv_2_16_0_0 -I/home/ubrpngn/build/ZD1211LnxDrv_2_16_0_0/src/include -fomit-frame-pointer -O2 -Wall -Wstrict-prototypes -pipe -Wno-unused -DZDCONF_WE_STAT_SUPPORT=1 -DHOST_IF_USB -DAMAC -DGCCK -DOFDM -DHOSTAPD_SUPPORT -DUSE_EP4_SET_REG -DDOWNLOADFIRMWARE -DfTX_GAIN_OFDM=0 -DfNEW_CODE_MAP=1 -DfWRITE_WORD_REG=1 -DfREAD_MUL_REG=1 -DENHANCE_RX=1 -DZDCONF_MENUDBG -DZDCONF_APDBG -DPRODUCTION -DZDCONF_BANDEDGE_ADJUST -DZDCONF_SES_SUPPORT=1 -D03_FIX=1 -DZD1211 -DZDCONF_LP_SUPPORT=0 src/zd1205.o src/zdreq.o src/zdasocsvc.o src/zdauthreq.o src/zdauthrsp.o src/zdmmrx.o src/zdshared.o src/zdhci.o src/zdglobal.o src/zdencrypt.o src/zdpmfilter.o src/zdpsmon.o src/zdsynch.o src/zdbuf.o src/zd1205_proc.o src/zdhw.o src/zddebug.o src/zdtkipseed.o src/zdmic.o src/zddebug2.o src/zdlpmgt.o src/zdturbo_burst.o src/zdusb.o src/zdmisc.o src/zd1211.o make -C /lib/modules/2.6.19-emission1/build SUBDIRS=/home/ubrpngn/build/ZD1211LnxDrv_2_16_0_0 modules make[3]: Entering directory `/usr/src/linux-2.6.19-emission1' CC [M] /home/ubrpngn/build/ZD1211LnxDrv_2_16_0_0/src/zd1205.o /home/ubrpngn/build/ZD1211LnxDrv_2_16_0_0/src/zd1205.c:451: warning: initialization from incompatible pointer type /home/ubrpngn/build/ZD1211LnxDrv_2_16_0_0/src/zd1205.c: In function 'zd1205_xmit_frame': /home/ubrpngn/build/ZD1211LnxDrv_2_16_0_0/src/zd1205.c:5025: warning: ISO C90 forbids mixed declarations and code /home/ubrpngn/build/ZD1211LnxDrv_2_16_0_0/src/zd1205.c:5026: warning: assignment from incompatible pointer type /home/ubrpngn/build/ZD1211LnxDrv_2_16_0_0/src/zd1205.c:5029: warning: assignment from incompatible pointer type /home/ubrpngn/build/ZD1211LnxDrv_2_16_0_0/src/zd1205.c: In function 'zd1205_set_zd_cbs': /home/ubrpngn/build/ZD1211LnxDrv_2_16_0_0/src/zd1205.c:10344: warning: assignment from incompatible pointer type /home/ubrpngn/build/ZD1211LnxDrv_2_16_0_0/src/zdinlinef.h: In function 'Cfg_CtrlSetting': /home/ubrpngn/build/ZD1211LnxDrv_2_16_0_0/src/zdinlinef.h:357: warning: 'LenInUs' may be used uninitialized in this function /home/ubrpngn/build/ZD1211LnxDrv_2_16_0_0/src/zdinlinef.h:358: warning: 'NextLenInUs' may be used uninitialized in this function /home/ubrpngn/build/ZD1211LnxDrv_2_16_0_0/src/zd1205.c: In function 'zdcb_setup_next_send': /home/ubrpngn/build/ZD1211LnxDrv_2_16_0_0/src/zdinlinef.h:357: warning: 'LenInUs' may be used uninitialized in this function /home/ubrpngn/build/ZD1211LnxDrv_2_16_0_0/src/zdinlinef.h:358: warning: 'NextLenInUs' may be used uninitialized in this function CC [M] /home/ubrpngn/build/ZD1211LnxDrv_2_16_0_0/src/zdreq.o CC [M] /home/ubrpngn/build/ZD1211LnxDrv_2_16_0_0/src/zdasocsvc.o CC [M] /home/ubrpngn/build/ZD1211LnxDrv_2_16_0_0/src/zdauthreq.o CC [M] /home/ubrpngn/build/ZD1211LnxDrv_2_16_0_0/src/zdauthrsp.o CC [M] /home/ubrpngn/build/ZD1211LnxDrv_2_16_0_0/src/zdmmrx.o CC [M] /home/ubrpngn/build/ZD1211LnxDrv_2_16_0_0/src/zdshared.o CC [M] /home/ubrpngn/build/ZD1211LnxDrv_2_16_0_0/src/zdhci.o /home/ubrpngn/build/ZD1211LnxDrv_2_16_0_0/src/zdhci.c: In function 'zd_IbssConnect': /home/ubrpngn/build/ZD1211LnxDrv_2_16_0_0/src/zdhci.c:1320: warning: implicit declaration of function 'zd1205_SetRatesInfo' /home/ubrpngn/build/ZD1211LnxDrv_2_16_0_0/src/zdhci.c:1389: warning: ISO C90 forbids mixed declarations and code CC [M] /home/ubrpngn/build/ZD1211LnxDrv_2_16_0_0/src/zdglobal.o CC [M] /home/ubrpngn/build/ZD1211LnxDrv_2_16_0_0/src/zdencrypt.o CC [M] /home/ubrpngn/build/ZD1211LnxDrv_2_16_0_0/src/zdpmfilter.o CC [M] /home/ubrpngn/build/ZD1211LnxDrv_2_16_0_0/src/zdpsmon.o /home/ubrpngn/build/ZD1211LnxDrv_2_16_0_0/src/zdpsmon.c: In function 'RxInfoIndicate': /home/ubrpngn/build/ZD1211LnxDrv_2_16_0_0/src/zdpsmon.c:397: warning: 'asoc' may be used uninitialized in this function /home/ubrpngn/build/ZD1211LnxDrv_2_16_0_0/src/zdpsmon.c:396: warning: 'oldPsm' may be used uninitialized in this function CC [M] /home/ubrpngn/build/ZD1211LnxDrv_2_16_0_0/src/zdsynch.o CC [M] /home/ubrpngn/build/ZD1211LnxDrv_2_16_0_0/s
[zd1211-devs] Vendor driver v2.16.0.0
Hi, The ZD1211 download page has been removed from Atheros.com, but ZyDAS sent me a new driver release. You can download it from: http://dsd.object4.net/zd1211-vendor/releases/ Large packet support is now disabled by default due to the reboot/module reload problems that the large packet firmware introduces. There are some other small changes as well. Daniel - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Zd1211-devs mailing list - http://zd1211.ath.cx/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
