Re: [zd1211-devs] Pluscom WU-ZD1211B working (sort of) with zd1211rw and 2.6.23
The call trace indicates a problem with softmac and not the
driver. Sorry, cannot help here.
Got one of these the other day. USB ID is 0ace:1215, but sadly it contains
the UW2453 RF device. So yet another device with the same USB ID but
different RF!
Started using it on Gentoo with Kernel 2.6.22-r9
Tried using the supplied linux drivers - couldn't get them to compile.
Tried the Vendor Drivers 2.21 and 2.22 - got them to compile but I'm using
the device through a USB1.1 port and while it would successfully upload the
firmware it stalled on rebooting the device (intr_urb: failed with error
-5). Tried to poke around the code but no luck
So bit the bullet and installed 2.6.23-r3 and used the updated zd1211rw
driver with the UW2453 RF support and seem to have a degree of success.
But I'm getting fairly regular crashes, here's the log:
[ cut here ]
kernel BUG at kernel/workqueue.c:220!
invalid opcode: [#1]
Modules linked in: zd1211rw
CPU:0
EIP:0060:[c01249cb]Not tainted VLI
EFLAGS: 00010002 (2.6.23-gentoo-r3 #3)
EIP is at queue_delayed_work_on+0x1b/0x80
eax: ebx: ee20f544 ecx: ee20f534 edx: ef7ee8a0
esi: edi: ee20f534 ebp: ee20f520 esp: c16e9f50
ds: 007b es: 007b fs: gs: ss: 0068
Process events/0 (pid: 5, ti=c16e8000 task=ef7d3570 task.ti=c16e8000)
Stack: 0296 ee6e5200 c0124a6c 0bb8 c036ab81
c050ec00 c036cb50 ed414b60 ef7ee880 ee20f534
c036ab30 c012447b c16e9fb4 0046 ef7d3570 ef7ee880 ef7ee880
Call Trace:
[c0124a6c] queue_delayed_work+0x1c/0x20
[c036ab81] ieee80211softmac_auth_queue+0x51/0x130
[c036cb50] ieee80211softmac_assoc_notify_auth+0x0/0x30
[c036ab30] ieee80211softmac_auth_queue+0x0/0x130
[c012447b] run_workqueue+0x6b/0xe0
[c0124ae0] worker_thread+0x0/0xc0
[c0124b92] worker_thread+0xb2/0xc0
[c0127080] autoremove_wake_function+0x0/0x40
[c0126ef8] kthread+0x38/0x60
[c0126ec0] kthread+0x0/0x60
[c01040c7] kernel_thread_helper+0x7/0x10
===
If the device is plugged in on boot up then it's ok,unless I stop and
restart it a few times. But it seems to cause most problems if I plug it in
after I've booted.
If I can be of any more help then let me know.
So thanks, keep up the good work,
Rob
--
View this message in context:
http://www.nabble.com/Pluscom-WU-ZD1211B-working-%28sort-of%29-with-zd1211rw-and-2.6.23-tf4910280.html#a14058824
Sent from the zd1211-devs mailing list archive at Nabble.com.
-
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
___
Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
--
Uli Kunitz
-
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
___
Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] Where do I get the firmware for ZD1211 device id 0x4802
Nazim Khan wrote: Hi All, I am using USB based TrendNet Wireless Card. I downloaded the firmware and while uploading the firmware it gave the following error. Where can I get the correct firmware for my device? usb 1-1: firmware device id 0x4330 and actual device id 0x4802 differ, continuing anyway musb_h_ep0_irq 1109: no URB for end 0 musb_h_ep0_irq 1109: no URB for end 0 musb_h_ep0_irq 1109: no URB for end 0 musb_h_ep0_irq 1109: no URB for end 0 musb_h_ep0_irq 1109: no URB for end 0 usb 1-1: USB control request for firmware upload failed. Error number -32 usb 1-1: Could not upload firmware code uph. Error number -32 zd1211rw 1-1:1.0: couldn't load firmware. Error number -32 usb 1-1: reset high speed USB device using musb_hdrc and address 2 musb_h_ep0_irq 1109: no URB for end 0 usb 1-1: device descriptor read/64, error -110 musb_h_ep0_irq 1109: no URB for end 0 usb 1-1: device descriptor read/64, error -110 usb 1-1: reset high speed USB device using musb_hdrc and address 2 musb_h_ep0_irq 1109: no URB for end 0 usb 1-1: device descriptor read/64, error -110 regards, Nazim Could you please give us a hint, which kernel you have and what USB id your device has? -- Uli Kunitz - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] coldplugging zd1211rw results in firefox segfault
Paul Albrecht wrote: Hi, I'm trying to use a hawking hwu54g with the zd1211rw driver in the 2.6.20 linux kernel. It works ok when I hotplug the device, but causes firefox to segfault when I coldplug the device. I compiled the device driver as a module so I don't see why there should be any difference. Any ideas? Could you pleas explain, what's the difference between a hotplug and a coldplug is? BTW a userspace process shouldn't segfault, if a network device does dis- and reappear. -- Uli Kunitz - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] Shuttle PN18G; re-used USB device ID
Vendor: Shuttle
Model: PN18G (although it doesn't seem to be marked as such)
USB Device ID: 07b8:6001
Chip: ZD1211B
RF: AL2230S
The chip description from dmesg:
[ 1378.268000] zd1211rw 5-6:1.0: zd1211b chip 07b8:6001 v4810 high 00-12-0e
AL2230S_RF pa0 -
It is a USB device designed to be connected directly to a pin header or other
internal connector. It has the large coax antenna mount, and also provides an
alternative U.FL connector that a pigtail may be attached to.
I know it, I have the older product in my Shuttle. (Actually this
was the device that started me to go into this.)
Anyway, it looks like this is a re-use of a previously existing device ID. I
had to modify the driver to get it working (patch attached).
We have seen this now several times. Zydas/Atheros told us that
this shouldn't happen, because this was the only method, we have
been aware to distinguish between both products.
I hope this is enough info to get this working in mainline.
Not really, we need to find another way to identify the chip.
BTW, it would be nice if the driver printed an error message if a ZD1211 is
assumed but the chip is actually a ZD1211B, or vice-versa. It currently fails
silently. I'm not sure if there is a good way to determine at runtime what
kind
of chip you are actually talking to ... ?
That's exactly the problem. The problem is also that resetting the
device doesn't work reliably. We need to work on it.
static struct usb_device_id usb_ids[] = {
/* ZD1211 */
{ USB_DEVICE(0x0ace, 0x1211), .driver_info = DEVICE_ZD1211 },
- { USB_DEVICE(0x07b8, 0x6001), .driver_info = DEVICE_ZD1211 },
+/* Work-around for Shuttle PN18G, which re-uses this device ID: */
+ { USB_DEVICE(0x07b8, 0x6001), .driver_info = DEVICE_ZD1211B },
{ USB_DEVICE(0x126f, 0xa006), .driver_info = DEVICE_ZD1211 },
{ USB_DEVICE(0x6891, 0xa727), .driver_info = DEVICE_ZD1211 },
{ USB_DEVICE(0x0df6, 0x9071), .driver_info = DEVICE_ZD1211 },
--
Uli Kunitz
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now http://get.splunk.com/
___
Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] New device ID for zd1211rw driver: Telegent TG54USB
Reinhard Speyerer wrote:
I have checked that the Telegent TG54USB WLAN adapter works with the zd1211rw
driver by adding the following to zd_usb.c and using it in managed mode with
WEP:
$ diff -u linux-2.6.22.1/drivers/net/wireless/zd1211rw/zd_usb.c{.orig,}
--- linux-2.6.22.1/drivers/net/wireless/zd1211rw/zd_usb.c.orig
2007-08-09 16:09:52.0 +0200
+++ linux-2.6.22.1/drivers/net/wireless/zd1211rw/zd_usb.c 2007-08-09
16:31:34.0 +0200
@@ -54,6 +54,7 @@
{ USB_DEVICE(0x0586, 0x3401), .driver_info = DEVICE_ZD1211 },
{ USB_DEVICE(0x14ea, 0xab13), .driver_info = DEVICE_ZD1211 },
{ USB_DEVICE(0x13b1, 0x001e), .driver_info = DEVICE_ZD1211 },
+ { USB_DEVICE(0x129b, 0x1666), .driver_info = DEVICE_ZD1211 },
/* ZD1211B */
{ USB_DEVICE(0x0ace, 0x1215), .driver_info = DEVICE_ZD1211B },
{ USB_DEVICE(0x157e, 0x300d), .driver_info = DEVICE_ZD1211B },
Product: Telegent TG54USB WLAN Adapter
USB ID: 129b:1666
Chip ID: zd1211 chip 129b:1666 v4330 high 00-01-36 RF2959_RF pa0 -
FCC ID: N89-UW620Z
Regards,
Reinhard
Reinhard,
thank you. I have added the USB id to the zd1211rw and the
zd1211rw-mac80211 driver in my git tree.
--
Uli Kunitz
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now http://get.splunk.com/
___
Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] zd1211rw 2.6.23-rc2 (git)
Steven wrote: I've noticed this behavior in the zd1211rw driver for a few months now and haven't seen anyone else mention it. I think it's odd. The system is Debian Sid with a git kernel, usually daily. When I first boot and plug in the wireless usb stick Debian properly identifies it and hotplugs it. However, the usb stick will not actually associate with any given AP until I use `iwconfig eth0 essid off` at which point it will pick the first AP with which it can negotiate a connection with. Subsequent `iwconfig eth0 essid off` will toggle the essid (and related AP) between off/any and the target essid. This is where things become hazy. If, instead of `iwconfig eth0 essid off` I used `iwconfig eth0 essid ap_essid` the `iwconfig` output will change to reflect the desired essid (and related AP) but the wireless connection will still not be negotiated until `iwconfig eth0 essid off`. Well, sometimes it will--about one in ten tries. This leads me to, most often, need to do the following: On one tty (or screen), `ifdown eth0 ifup eth0` and then, while dhclient is trying to find a connection, `iwconfig eth0 essid off` on another tty (or screen). This is using an AirLink 101, firmware version 4605, zd1211 chip 0ace:1211 v4330 full 00-11-a3 AL2230_RF pa0 Steven, I have seen the later mail and starting now to see your problem. It seems that you can get associated if you are not giving the essidi (off), but you have trouble with the initial setup. I have not a lot of experience with Debians init scripts and WLAN installation, but there have been reports that they doesn't work well with WLAN adapters. I know this a poor situation, but currently we cannot do a lot about it. For the softmac driver I'm always recommending to set all the necessary parameters before you call ifconfig eth0 up and I believe this is the problem with the default debian configuration. ifconfig eth0 up means in the WLAN code that the device should start to associate and this requires the parameters to be set beforehand. Kind regards, Ulrich -- Uli Kunitz - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] ACKs on zd1211rw-mac80211
Luis Carlos Cobo wrote: Hi, I'm playing with the driver and mac80211 stack to get some ad-hoc-like functionality. I am able to do a ping among two non-associated nodes, but I get about 9 ping replys (i.e. 8 duplicates) for each ping request. I found out the problem is that the frames are not being acked, so they are retransmitted. I haven't found the code for retransmission nor for ack generation, so I am not sure what do I need to do to make the device generate acks. We have not implemented ad-hoc before. The ACKs should be generated if the MAC address is set in the device. There is a function in zd_chip.c to do it. At http://wireless.sipsolutions.net/en/users/Drivers/zd1211rw/mac80211Issues I found: Johannes writes: In zd1211, we start with hwaddr = dev-wiphy-perm_addr which isn't correct either, for a pure monitor mode we want to start with a zero mac addr to avoid acking packets. Also, zd1211rw will end up having a NULL hwaddr when a monitor interface is added, most likely segfaulting in zd_write_mac_addr then. which leads me to think by default the node would issue acks... Any help or explanation of how ack generation works for the device would be greatly appreciated. Thanks! -- Luis Carlos Cobo Rus GnuPG ID: 44019B60 cozybit Inc. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs -- Uli Kunitz - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] zd1211rw timed out on ep4out
Mayne wrote: Hi! On kernel 2.6.19.2, zd1211rw, VT82x UHCI USB 1.1 Controller (rev 0e) 1106:3038, Longshine G2 07b8:6001, the driver hangs pretty often with the following error messages: usb 1-2: zd1211rw timed out on ep4out len=0/6 zd1211rw 1-2:1.0: zd_usb_ioread16v() error in usb_bulk_msg(). Error number -110 zd1211rw 1-2:1.0: zd_chip_control_leds error -110 (repeated indefinitely) Unplugging and plugging in the device TWO times helps (for a short time). Seems this or similar things happen quite often on VIA-based USB 1.1 controllers - on another machine using VIA USB 1.1, I saw similar effects, but there for some reason the USB layer dealt with the problem after some time (to the driver, a disconnect and reconnect event was shown - without manually interfering). The error -110 is a timeout. It simply means that the USB subsystem couldn't execute the USB transfer. We had comparable issues witht the mac80211 stack and I implemented here some controls to limit the number of USB packets to be queued for transmission. At least in my experience this limited the -110s for zd_chip_control_leds(). The device hangs might result from an unsuccessful reassociation, which is sometimes requested from the AP. It could very well be that the support for VIA USB host controllers is pretty weak in the kernel. I have a VIA-based USB 2.0 card in my oldest PC and it is consuming 10% of computation time on Linux box. Beside this the systems works well. But notify that I'm currently only developing the mac80211 driver. Regards, Uli -- Uli Kunitz - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] ad-hoc / master mode support
Fernando Toledo wrote: hi! is possible to get a ad-hoc or master mode in the zd1211rw? ...on the mac80211 tree? i also have a bcm43xx and i need to get a peer to peer link i have the old community driver and work as master mode (some system lookups), but i like to get this behavior with the new drivers thanks all! Fernando, yes it is not implemented right now and it's definitely on the list todo. But before we can work on this, we have to fix the multiple interface issues we currently have. Kind regards, Uli -- Uli Kunitz - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] Super huge ping with zd1211rw_mac80211
On 07-04-18 23:54 Richard Hughes wrote: On Tue, 2007-04-03 at 18:49 -0400, Daniel Drake wrote: Are the ping times really high all the time, or is it just some/most of the time? Well, they were fairly random, i.e. sometimes it worked well, and sometimes look 10 seconds - and then after a few minutes was okay. You'll be pleased to know that with the latest wireless-dev snapshot (and latest linus) everything is going much better. I can't tell you what fixed it, but it now just works. Thanks. Richard. This sounds good. However notice that wireless performance differs a lot depending on the actual interference. In my home it varies a lot, probably caused by WLANs of my neighbours. I have implemented a change for the mac80211-based driver, which should remove one source for higher latency. However I still can observe latencies between 300 and 400 ms once in a while. -- Uli Kunitz - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Zd1211-devs mailing list - http://zd1211.ath.cx/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] dhclient stopped working
On 07-04-17 09:45 Mayne wrote: I wonder why this worked with the zd1211rw at all. The new driver doesn't like the ifconfig down/up circle dhclient initiates before trying to get an IP, see http://www.nabble.com/zd1211rw-WPA1-dhclient-failure-tf3230778.html . This is not dhclient, this is a Debian script in etc. The issue is that most of this stuff isn't working, because the scripts were written for Ethernet cards. For WPA you have to use wpa_supplicant, but calling dhclient directly after the association has been established, doesn't create any problems here. -- Uli Kunitz - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Zd1211-devs mailing list - http://zd1211.ath.cx/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] dhclient stopped working
On 07-04-16 23:56 Lucio Crusca wrote: Lucio please add to the script the following. #!/bin/bash -x killall dhclient # Might not be what you want if you have several # dhclients running in parallel. modprobe zd1211rw # Shouldn't be needed if udev is configured # the right way. ifconfig wlan0 down ifconfig wlan0 up iwconfig wlan0 rate 2Mb iwconfig wlan0 essid MyAP key xx ap 00:18:F3:93:2D:33 iwconfig wlan0 mode managed dhclient wlan If it doesn't work, forward the output of iwconfig and ifconfig. If encryption parameters change, do rmmod zd1211rw, followed by a modprobe. -- Uli Kunitz - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Zd1211-devs mailing list - http://zd1211.ath.cx/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] zd1211rw firmware redistribution
On 07-04-10 17:58 eric magaoay wrote: Fedora maintainers are currently reviewing zd1211rw firmware for possible inclusion into the repository provided that the established requirements [1] are met. Anyone have comments on the requirements? If I remember correctly, Zydas gave permission for redistribution of its zd1211 firmware; if so is it still valid under the new ownership (Atheros)? The vendor driver has been distributed alternatively under the GPL version 2 in source code, which contains header files with the firmware in large C arrays. I have created a derived work of the vendor driver published also under the GPL version 2. The source code contains the headers of the vendor driver. The program itself creates the firmware files. Look for zd1211rw_fw_*.tar.bz2 under http://deine-taler.de/zd1211/snapshots/. Look at the file README. IANAL, so I cannot answer the question under which conditions the distribution of the firmware files would be covered under the GPL. [1] Requirements: 1. The files are non-executable (note: this means that the files cannot run on their own, not that they are just chmod -x) 2. The files are not libraries. 3. The files are standalone, not embedded in executable or library code. 4. Explicit permission is given by the owner to freely redistribute without restrictions (this permission must be included, in writing, with the files in the packaging) 5. The files must be necessary for the functionality of open source code being included in Fedora. Requirements 1, 2, 3, and 5 are fulfilled by the binary files. Daniel Drake (dsd-at-gentoo-dot-org) handled the relationship to the vendor, so he might be able to help with requirement 4. The License tag for any firmware that disallows modification should be set to: Redistributable, no modification permitted Firmware packages should be named foo-firmware, where foo is the driver or other hardware component that the firmware is for. -- 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.phpp=sourceforgeCID=DEVDEV ___ Zd1211-devs mailing list - http://zd1211.ath.cx/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] Moving zd1211rw content to linuxwireless.org
On 07-03-28 19:25 Daniel Drake wrote: Hi, How do people feel about me moving the zd1211rw info from zd1211.ath.cx onto http://www.linuxwireless.org? The main advantage here is that this site is becoming the central source for in-kernel linux wireless info. Also, by listing supported devices on that wiki, they get automatically aggregated onto a larger page which lists all linux-supported USB-WLAN hardware: http://www.linuxwireless.org/en/users/Devices/USB Another advantage is that this wiki is editable by the public. I would leave the ID's and entries for devices which are not supported by zd1211rw on the front page of http://zd1211.ath.cx but remove the rest. Thoughts? I think we should put the information at the new website and should put a link at zd1211.ath.cx. Whether we should remove data from zd1211.ath.cx I'm not so sure. -- 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.phpp=sourceforgeCID=DEVDEV ___ Zd1211-devs mailing list - http://zd1211.ath.cx/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] ! Patch for sources (83) for Kernel from 2.6.18
On 07-02-05 08:23 Waldemar Wetzel wrote: This patch is only for the Sources. Also zd1211 and ZD1211B. The RW Driver supports only zd1201 Chipset? I dont know. The zd1211rw driver support ZD1211 and ZD1211B. -- Uli Kunitz - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Zd1211-devs mailing list - http://zd1211.ath.cx/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] Working on the dscape driver
On 07-01-27 22:26 Jon Smirl wrote:
In order to learn more about how the zd1211 works I though I could try
implementing a few missing functions in the dscape zd1211 driver. The
easiest ones looked to be the statistics functions.
get_stats needs this filled:
struct ieee80211_low_level_stats {
unsigned int dot11ACKFailureCount;
unsigned int dot11RTSFailureCount;
unsigned int dot11FCSErrorCount;
unsigned int dot11RTSSuccessCount;
}
get_tx_stats needs this filled, one per queue:
struct ieee80211_tx_queue_stats_data {
unsigned int len; /* num packets in queue */
unsigned int limit; /* queue len (soft) limit */
unsigned int count; /* total num frames sent */
};
I've been poking around in the vendor driver amd zd1211rw and don't
see an obvious way to collect this data. For example I didn't see
where RTS success/failure is tracked. I also haven't located the exact
spot to separate FCS (CRC errors) from other classes of errors.
We do/emulate ACK confirmation for packet tx in d80211, so it
should be possible to estimate the error count. However it is not
obvious to me, what the semantics is here. Are ACK failures for
retransmissions also counted here?
There is no simple way to count the RTS failures and successes. You could
however get all the RTS packets and work from that. However I
would regard this as waste of device-to-host bandwidth, which is
shared of all USB devices on the same host adapter.
FCS errors are in struct rx_status (ZD_RX_CRC32_ERROR) if ZD_RX_ERROR is set.
Queue stats might be possible, if we start to understand how
queuing does work for the ZD1211B. I guess that the high byte of packet
length in zd_ctrlset is used for this. But we don't know how
exactly. Notify there is no support for queuing in ZD1211 devices.
--
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.phpp=sourceforgeCID=DEVDEV
___
Zd1211-devs mailing list - http://zd1211.ath.cx/
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] Working on the dscape driver
On 07-01-28 12:52 Jon Smirl wrote: On 1/28/07, Ulrich Kunitz [EMAIL PROTECTED] wrote: There is no simple way to count the RTS failures and successes. You could however get all the RTS packets and work from that. However I would regard this as waste of device-to-host bandwidth, which is shared of all USB devices on the same host adapter. Couldn't this be tracked easily in the firmware? Is it possible to get firmware changes? Yes, firmware would probably able to do that. I don't explicitly whether firmware changes would be possible. But I would not be to optimistic. Atheros bought ZyDAS last year and doesn't publicly market or support the product anymore. Daniel started last year an assembler/disassembler for the firmware, but I haven't seen any activity for this recently. -- 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.phpp=sourceforgeCID=DEVDEV ___ Zd1211-devs mailing list - http://zd1211.ath.cx/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] Random register corruption bug in reset_mode()?
On 07-01-11 19:34 Andy Green wrote:
There doesn't seem to be an equivalent function in the vendor tree.
Attached is my guess at what was intended.
Andy, thank you for finding this. Based on the current logic this
is the right fix:
Subject: [PATCH] zd1211rw: Fixed array size issue in reset_mode
Andy Green found this issue.
---
zd_mac.c |5 ++---
1 files changed, 2 insertions(+), 3 deletions(-)
diff --git a/zd_mac.c b/zd_mac.c
index 10339f5..7f0c3bc 100644
--- a/zd_mac.c
+++ b/zd_mac.c
@@ -157,7 +157,7 @@ void zd_mac_clear(struct zd_mac *mac)
static int reset_mode(struct zd_mac *mac)
{
struct ieee80211_device *ieee = zd_mac_to_ieee80211(mac);
- struct zd_ioreq32 ioreqs[3] = {
+ struct zd_ioreq32 ioreqs[] = {
{ CR_RX_FILTER, STA_RX_FILTER },
{ CR_SNIFFER_ON, 0U },
};
@@ -165,10 +165,9 @@ static int reset_mode(struct zd_mac *mac
if (ieee-iw_mode == IW_MODE_MONITOR) {
ioreqs[0].value = 0x;
ioreqs[1].value = 0x1;
- ioreqs[2].value = ENC_SNIFFER;
}
- return zd_iowrite32a(mac-chip, ioreqs, 3);
+ return zd_iowrite32a(mac-chip, ioreqs, ARRAY_SIZE(ioreqs));
}
int zd_mac_open(struct net_device *netdev)
--
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.phpp=sourceforgeCID=DEVDEV
___
Zd1211-devs mailing list - http://zd1211.ath.cx/
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] Copy seems to be working, speed is the next issue
On 07-01-04 20:04 Jon Smirl wrote: You should also now retest the vendor driver and see if you can reproduce the vendor-driver-is-2x-faster thing. Linux version of the vendor driver is running about the same speed as zd1211rw. It it the Windows version of the vendor driver that is faster for the copies. About 50% right now. Unless we start to reengineer the Windows driver, there is nothing we can do about this. It might even be that the Windows driver is using a different firmware. As Daniel proposed it is worthwhile to check against the Linux vendor driver. If our driver has a lower performance, than there is something we can do about it. I'll try adding some more hints to the debug output. I wouldn't expect to retransmit enough times to cause a frame transmission error. If it is noise there would normally be only a single retransmission. Multiple retransmissions and then frame transmit failure implies a bug somewhere. I have trouble to follow the logic here. There are several retransmissions until the device gets the ACK. There is nothing which guarantees, that the second transmission must succeed. When I was using kismet the traces looked more to me like the ACK was being transmitted by the AP and the zd1211rw wasn't listening. Please recognize that the fact that you see the ACK elsewhere, doesn't mean, that the packet can be seen at another point. There are interferences. The other fact is that the ZD1211 devices are cheap devices, the RF transceivers have low quality. BTW per packet low level synchronous ACKs is a terrible design for a MAC layer. I don't see that they needed any acks at all. UDP is unreliable and TCP will recover. TCP also piggybacks acks on return traffic which is much more efficient. Those acks waste a huge chunk of bandwidth. This is the way the 802.11 standard has been designed. As far as I know there is discussion about doing a single ACK for several packets in 802.11n. There are some vendor based optimizations to merge several packets into a single packet and so on, but they are not interoperable. Kind regards, Ulrich -- 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.phpp=sourceforgeCID=DEVDEV ___ Zd1211-devs mailing list - http://zd1211.ath.cx/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] Airoha AL2230S_RF it is supported? shared key work?
On 06-12-28 13:23 athoslnx wrote: Daniel Drake wrote: Then I'd imagine you don't have an AL2230S, you have an AL2230, but who knows since you didn't post any info :) Daniel As I have said, I have also Longshine 8131G3, but it uses an AL2230. So the vendor might have switched the RF chips. Where did you buy it? Cheers, 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.phpp=sourceforgeCID=DEVDEV ___ Zd1211-devs mailing list - http://zd1211.ath.cx/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] question and a possible bug
On 06-12-29 14:35 Giulio Bottazzi wrote: Hi all, I've a question: how can I add a SuccessReport to the wiki? This is my configuration card manufacturer: Shuttle PN-15g release version: (didn't find in /var/log/messages) platform: Athlon 64 3200+ kernel: 2.6.18 (but I use the svn driver, of course) mode: managed USB: 2.0 driver version: 84 working: yes with occasional disconnection reliable: almost kernel panic: never the driver seems to work BUT if I try a #lsusb -v then the interface stops to work and I have to manually disconnect/reconnect the card (which, in my case, means to open the box and uplug/plug the cable connected to the internal USB port). Any clue? Best, Giulio. Guilio, could you do an lspci of your machine. The bug is known and depends on the USB host adapter. On newer machines with USB 2.0, this bug cannot be seen. Regards, Uli - 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.phpp=sourceforgeCID=DEVDEV ___ Zd1211-devs mailing list - http://zd1211.ath.cx/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] Patch to make zd1211rw git build with current kernel
On 06-12-28 00:48 Jon Smirl wrote: This patch fixes up the zd1211rw git tree to account for the work queue changes in 2.6.20+. Probably would be best to attach the version of the patch that works. -- Jon Smirl [EMAIL PROTECTED] I have merged your patch with a patch from Jeff Garzik from the wireless-2.6 tree. It can be found in the branch wireless-2.6 in my git tree. The master branch will continue to compile against 2.6.19. 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.phpp=sourceforgeCID=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.phpp=sourceforgeCID=DEVDEV
___
Zd1211-devs mailing list - http://zd1211.ath.cx/
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] Kernel OOPS in 2.6.20-rc1 with zd1211rw (possibly ieee80211softmac?)
On 06-12-15 16:39 Chris wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
I'll apologise now, this is the first kernel-related issue i've ever
experienced, so I may be doing this wrong or missing something :).
I recently downloaded and compiled 2.6.20-rc1 and set it up nicely with
my zd1211 card (Addon ADD-GWU180) and now the kernel oops's on boot in
normal mode, or when issuing iwconfig eth1 essid essid_name in
recovery mode. From the information it spews out at the time, it looks
like possibly a ieee80211softmac issue, but it doesn't happen with an
rt2570 card, and I thought it best to check with you first.
Hopefully all the information you need is included below, if not, i'll
be happy to provide anything else you need.
Thanks in advance.
This is a bug resulting from the changes in the API. I have fixed
that last Sunday.
Here is the patch:
[PATCH] ieee80211softmac: Fix direct calls to ieee80211softmac_assoc_work
The signature of work functions changed recently from a context
pointer to the work structure pointer. This caused a problem in
the ieee80211softmac code, because the work function has been
called directly with a parameter explicitly casted to (void*).
This compiled correctly but resulted in a softlock, because the
mutex_lock has been executed at the wrong memory address. The
patch fixes the problem. Softmac works again.
Signed-off-by: Ulrich Kunitz [EMAIL PROTECTED]
---
net/ieee80211/softmac/ieee80211softmac_assoc.c |6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/net/ieee80211/softmac/ieee80211softmac_assoc.c
b/net/ieee80211/softmac/ieee80211softmac_assoc.c
index eec1a1d..a824852 100644
--- a/net/ieee80211/softmac/ieee80211softmac_assoc.c
+++ b/net/ieee80211/softmac/ieee80211softmac_assoc.c
@@ -167,7 +167,7 @@ static void
ieee80211softmac_assoc_notify_scan(struct net_device *dev, int event_type,
void *context)
{
struct ieee80211softmac_device *mac = ieee80211_priv(dev);
- ieee80211softmac_assoc_work((void*)mac);
+ ieee80211softmac_assoc_work(mac-associnfo.work.work);
}
static void
@@ -177,7 +177,7 @@ ieee80211softmac_assoc_notify_auth(struc
switch (event_type) {
case IEEE80211SOFTMAC_EVENT_AUTHENTICATED:
- ieee80211softmac_assoc_work((void*)mac);
+ ieee80211softmac_assoc_work(mac-associnfo.work.work);
break;
case IEEE80211SOFTMAC_EVENT_AUTH_FAILED:
case IEEE80211SOFTMAC_EVENT_AUTH_TIMEOUT:
@@ -438,7 +438,7 @@ ieee80211softmac_try_reassoc(struct ieee
spin_lock_irqsave(mac-lock, flags);
mac-associnfo.associating = 1;
- schedule_work(mac-associnfo.work);
+ schedule_delayed_work(mac-associnfo.work, 0);
spin_unlock_irqrestore(mac-lock, flags);
}
--
1.4.1
-
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.phpp=sourceforgeCID=DEVDEV
___
Zd1211-devs mailing list - http://zd1211.ath.cx/
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] wireless-dev dont connect
On 06-12-16 00:57 Fernando Toledo wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, i play with wireless-dev and wireless-2.6 git's (to make to work my onboard bcm43xx) in these kernels i cant connect with my zd1211 to the ap's i can scan and see the ap, the log say associted but i do not get the ip from my dhcp (also i test to put a fixed address) i dont have this problem on 2.6.19 (vanilla) from kernel.org when iwlist scann or ifconfig up : zd1211rw 2-6:1.0: zd_chip_unlock_phy_regs() CR_REG1: 0x20 - 0xa0 SoftMAC: sent association request! SoftMAC: associated! zd1211rw 2-6:1.0: housekeeping_disable() zd1211rw 2-6:1.0: zd_chip_lock_phy_regs() CR_REG1: 0xa0 - 0x20 zd1211rw 2-6:1.0: zd_chip_unlock_phy_regs() CR_REG1: 0x20 - 0xa0 Something shuts the interface down after being associated. No wonder that you get no IP over DHCP. This is certainly a configuration problem. 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.phpp=sourceforgeCID=DEVDEV ___ Zd1211-devs mailing list - http://zd1211.ath.cx/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] ioread32 error
Ralf, could you please enable the debug messages and send a complete kernel log starting with the plugin of the device. There are several places in the driver, which could cause an -EWOULDBLOCK for an ioread32. 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.phpp=sourceforgeCID=DEVDEV ___ Zd1211-devs mailing list - http://zd1211.ath.cx/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] Newest git: Compile problems on Ubuntu edgy
On 06-12-02 09:36 Jan Schiefer wrote: Hi all, newest zd1211rw won't compile on my ubuntu edgy box anymore. uname -a: Linux jan-laptop 2.6.17-10-generic #2 SMP Fri Oct 13 18:45:35 UTC 2006 i686 GNU/Linux This is no surprise. I don't think, Daniel and me had a formal decision, but recently we had the practice to support the latest stable kernel in the master branch and the wireless-2.6 tree in wireless-dev. I planned to switch today to 2.6.19 with the master tree. Supporting all the different kernel versions, is simply to much effort. Daniel and I have both day jobs. You are always free to support the driver on your own. Kind regards, Ulrich -- 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.phpp=sourceforgeCID=DEVDEV ___ Zd1211-devs mailing list - http://zd1211.ath.cx/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] Latest version doesn't build on 2.6.19-rc6
On 06-11-26 13:50 Elimar Riesebieter wrote: Hi all, the current rw version gives: ... LD /source/zd1211/zd1211rw_2006-11-26/built-in.o CC [M] /source/zd1211/zd1211rw_2006-11-26/zd_netdev.o CC [M] /source/zd1211/zd1211rw_2006-11-26/zd_mac.o /source/zd1211/zd1211rw_2006-11-26/zd_mac.c: In function 'link_led_handler': /source/zd1211/zd1211rw_2006-11-26/zd_mac.c:1184: error: 'struct ieee80211softmac_device' has no member named 'associated' Elimar Elimar, the snapshots are from the master branch of the git tree, which compiles almost always against the latest stable kernel. The wireless-dev branch from my git-tree compiles against 2.6.19-rc*. Cheers, 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.phpp=sourceforgeCID=DEVDEV ___ Zd1211-devs mailing list - http://zd1211.ath.cx/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] multicast support and ipv6
On 06-11-23 22:52 Benoit PAPILLAULT wrote:
Patch (replacing the previous) is attached.
Best regards,
Benoit
Benoit,
Thank's again for demonstrating how to solve the issue. I've
reworked your patch. You can find the new patch below. Please
check it with IPv6. I don't have here a running AP with IPv6
enabled.
The patch is also include in my git tree.
http://www.deine-taler.de/zd1211/zd1211.git/
Please consider that the master branch compiles against 2.6.18 and
not 2.6.19. For 2.6.19 use the branch wireless-dev.
Regards,
Uli
Support for multicast adresses is implemented by supporting the
set_multicast_list() function of the network device. Address
filtering is supported by a group hash table in the device. Should
fix bugzilla.kernel.org bug 7424.
Signed-off-by: Ulrich Kunitz [EMAIL PROTECTED]
---
zd_chip.c | 13 +
zd_chip.h | 43 ++-
zd_mac.c| 44 +++-
zd_mac.h|3 +++
zd_netdev.c |2 +-
5 files changed, 102 insertions(+), 3 deletions(-)
diff --git a/zd_chip.c b/zd_chip.c
index bfff84c..4624379 100644
--- a/zd_chip.c
+++ b/zd_chip.c
@@ -1672,3 +1672,16 @@ int zd_rfwritev_cr_locked(struct zd_chip
return 0;
}
+
+int zd_chip_set_multicast_hash(struct zd_chip *chip,
+ struct zd_mc_hash *hash)
+{
+ struct zd_ioreq32 ioreqs[] = {
+ { CR_GROUP_HASH_P1, hash-low },
+ { CR_GROUP_HASH_P2, hash-high },
+ };
+
+ dev_dbg_f(zd_chip_dev(chip), hash l 0x%08x h 0x%08x\n,
+ ioreqs[0].value, ioreqs[1].value);
+ return zd_iowrite32a(chip, ioreqs, ARRAY_SIZE(ioreqs));
+}
diff --git a/zd_chip.h b/zd_chip.h
index 0df9d5b..6ed3fb6 100644
--- a/zd_chip.h
+++ b/zd_chip.h
@@ -395,10 +395,19 @@ #define CR_MAC_ADDR_P2CTL_REG(0x0614)
#define CR_BSSID_P1CTL_REG(0x0618)
#define CR_BSSID_P2CTL_REG(0x061C)
#define CR_BCN_PLCP_CFGCTL_REG(0x0620)
+
+/* Group hash table for filtering incoming packets.
+ *
+ * The group hash table is 64 bit large and split over two parts. The first
+ * part is the lower part. The upper 6 bits of the last byte of the target
+ * address are used as index. Packets are received if the hash table bit is
+ * set. This is used for multicast handling, but for broadcasts (address
+ * ff:ff:ff:ff:ff:ff) the highest bit in the second table must also be set.
+ */
#define CR_GROUP_HASH_P1 CTL_REG(0x0624)
#define CR_GROUP_HASH_P2 CTL_REG(0x0628)
-#define CR_RX_TIMEOUT CTL_REG(0x062C)
+#define CR_RX_TIMEOUT CTL_REG(0x062C)
/* Basic rates supported by the BSS. When producing ACK or CTS messages, the
* device will use a rate in this table that is less than or equal to the rate
* of the incoming frame which prompted the response */
@@ -850,4 +859,36 @@ int zd_chip_handle_signal_strength(struc
u16 zd_rx_rate(const void *rx_frame, const struct rx_status *status);
+struct zd_mc_hash {
+ u32 low;
+ u32 high;
+};
+
+static inline void zd_mc_clear(struct zd_mc_hash *hash)
+{
+ hash-low = 0;
+ /* The interfaces must always received broadcasts.
+* The hash of the broadcast address ff:ff:ff:ff:ff:ff is 63.
+*/
+ hash-high = 0x8000;
+}
+
+static inline void zd_mc_add_all(struct zd_mc_hash *hash)
+{
+ hash-low = hash-high = 0x;
+}
+
+static inline void zd_mc_add_addr(struct zd_mc_hash *hash, u8 *addr)
+{
+ unsigned int i = addr[5] 2;
+ if (i 32) {
+ hash-low |= 1 i;
+ } else {
+ hash-high |= 1 (i-32);
+ }
+}
+
+int zd_chip_set_multicast_hash(struct zd_chip *chip,
+ struct zd_mc_hash *hash);
+
#endif /* _ZD_CHIP_H */
diff --git a/zd_mac.c b/zd_mac.c
index 30ae0c2..5b100a3 100644
--- a/zd_mac.c
+++ b/zd_mac.c
@@ -37,6 +37,8 @@ static void housekeeping_init(struct zd_
static void housekeeping_enable(struct zd_mac *mac);
static void housekeeping_disable(struct zd_mac *mac);
+static void set_multicast_hash_handler(void *mac_ptr);
+
int zd_mac_init(struct zd_mac *mac,
struct net_device *netdev,
struct usb_interface *intf)
@@ -51,6 +53,8 @@ int zd_mac_init(struct zd_mac *mac,
softmac_init(ieee80211_priv(netdev));
zd_chip_init(mac-chip, netdev, intf);
housekeeping_init(mac);
+ INIT_WORK(mac-set_multicast_hash_work, set_multicast_hash_handler,
+ mac);
return 0;
}
@@ -132,6 +136,7 @@ out:
void zd_mac_clear(struct zd_mac *mac)
{
+ flush_workqueue(zd_workqueue);
zd_chip_clear(mac-chip);
ZD_ASSERT(!spin_is_locked(mac-lock));
ZD_MEMCLEAR(mac, sizeof(struct zd_mac));
@@ -245,6 +250,42 @@ int zd_mac_set_mac_address(struct net_de
return 0;
}
+static void
Re: [zd1211-devs] longshine usb-wlan stick, anyone ?
On 06-10-05 18:00 walter harms wrote: i was just collecting data for: longshine USBId 1582:6003 zd1211rw from 2006-08-12 (with added usb id) kernel vanilla 2.6.18 modprobe zd1211 Oct 5 15:55:49 linux kernel: ieee80211_crypt: registered algorithm 'NULL' Oct 5 15:55:49 linux kernel: ieee80211: 802.11 data/management/control stack, git-1.1.13 Oct 5 15:55:49 linux kernel: ieee80211: Copyright (C) 2004-2005 Intel Corporation [EMAIL PROTECTED] Oct 5 15:55:50 linux kernel: zd1211rw 2-2:1.0: firmware version 4725 Oct 5 15:55:50 linux kernel: zd1211rw 2-2:1.0: zd1211b chip 1582:6003 v4810 full 00-11-f6 AL2230_RF pa0 g--N Oct 5 15:55:50 linux kernel: zd1211rw 2-2:1.0: eth1 Oct 5 15:55:50 linux kernel: usbcore: registered new driver zd1211rw Oct 5 15:55:50 linux ifup: wlan0 Oct 5 15:55:50 linux ifup: No configuration found for wlan0 The device is on eth1 not wlan0. Ciao, 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.phpp=sourceforgeCID=DEVDEV ___ Zd1211-devs mailing list - http://zd1211.ath.cx/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] Connection dropped after few secs
On 06-09-03 17:51 Marko Huuhilo wrote: Ulrich Kunitz wrote: On 06-09-03 14:51 Marko Huuhilo wrote: Sorry for the lag, I tried to get the zd1211rw installed, but I failed. So I am still using the vendor driver. I cannot help with the vendor driver. Why did you fail to install the zd1211rw? I dl'ed zd1211rw dated 2006-09-02 and zd1211 firmware 2006-09-02 and softmac source. The firmware I got installed, softmac is installed and listed with lsmod, but when I run make in the driver directory, I get zd_netdev.c:208: error: 'ieee80211softmac_wx_set_wap undeclared here (not in a function) and also same error from the following lines, with different variables, all starting with ieee80211softmac_wx. I tried a snapshot from 2006-08-30 also. (I am not an expert with Linux, so I might have done a newbie error.) Kernel 2.6.18 isn't available as a Debian package, I would like to stick with my current kernel. -M. Marko, thank you for the information. It appears that you have an older kernel with a softmac version that doesn't support WAP related functions. You will need to compile a newer kernel version to support the driver. Here is a link, which explains the process for Debian, if you want to try it. http://newbiedoc.sourceforge.net/system/kernel-pkg.html The driver has been included in Linus' current kernel. So the driver will be included in new releases of the distributions and this shouldn't be an issue any more. Regards, Uli -- Uli Kunitz - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Zd1211-devs mailing list - http://zd1211.ath.cx/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] Patching 2.6.18-rcn and later
On 06-08-11 22:41 Adam Hunt wrote: Is it possible to patch 2.6.18-rc4 or later with the old (pre-rewrite) driver or will it conflict with the version that has been merged? If you want to use the vendor driver never compile zd1211rw static into the kernel. If that is ensured, you somehow must ensure that the vendor driver module will be loaded instead of zd1211rw. There are several options to do it: Don't compile the driver itself, simply remove it, unload it (rmmod) if it has been loaded and load the old driver, patch the udev configuration to look for the old driver. Maybe some friendly person could create later patches for major distributions. But don't expect us zd1211rw folks to work on it. So module loading mechanisms are the only issue to care for. Please keep in mind that the vendor driver could have never accepted into the kernel, because of coding style issues and the overall structure. The driver had to be rewritten. If it will conflict may I suggest that a patch of the old driver be released as something like zd1211-old for those of us that have to continue running it while the rewrite stabilizes? The zd1211rw is now pretty stable. I use it for several hours each day. I admit we still have to work on features, there are some issues with specific combinations of RF and ZD1211, but overall the picture is pretty good now. Keep in mind that we are not writing ower own softmac stack and a number of issues now are related to softmac. There is an agreement under the Linux WLAN developers to switch to the descape stack, but that hasn't happened so far for the mainline and descape has still it's own stability issues. However the developers are working on it. Thanks for your time and all the work that you all have done getting this driver rewritten and merged into mainline. I would like to thank everybody, who is testing the rewritten driver. This helps to find bugs and fixing them. Keep on going! Cheers, Uli -- Uli Kunitz - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Zd1211-devs mailing list - http://zd1211.ath.cx/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] [Fwd: Re: Any chance I can make the driver work with SPARC64]
On 06-08-12 02:51 Patrick Simmons wrote: I've looked at that driver, and unfortunately it doesn't yet support the features I need. I want to use it as a sort-of access point, so I'd need either ad-hoc or master mode support. Also, kernel 2.4 seems to be better than 2.6 on the Ultra 5 for reasons unrelated to the zd1211 card. Ok. It works on a number of architectures including PPC32 (big-endian) and x86-64 (64 bit). We would love to hear about experiences with the SPARC. There might be issues with alignment, SPARC doesn't support unaligned memory accesses. I have tried to avoid them, but you cannot know until you have tested it. I'll download rc4 to help test the new driver on SPARC, but I'd also like to get the old driver working if possible. I thought the unrewritten driver worked with PPC32 and x86-64 too, from the wiki. Am I mistaken? It appears that way, but I'm not tracking the vendor driver patches. The original vendor driver does only support x86. Thanks for telling me about SPARC not supporting unaligned memory accesses. The smiley-face error does say something about an unsupported unaligned load/store trap for the kernel. Are unaligned memory accesses known to be present in the old driver? Would they be difficult to identify and replace, if they're there? I may be able to fix a simple issue with the old driver myself if you can tell someone with my level of experience what to look for and how to replace it. If you get those messages, than sure there are such problems. It is not particularly difficult to fix it. Look at get_unaligned() and put_aligned() in asm/unaligned.h. The issue is to find unaligned accesses in the code. The problem with the vendor driver is, that they are writing into byte arrays, so you can't see it simply from the data structures. I would guess there will be issues in the tx and in the rx path. In the tx path there are unaligned 16 bit values in the control set structure. The rx path might have problems with and the combined packet info structure. (This is the best chance for unaligned accesses in the rw driver.) The best way is to look at the trap and find the function, where it happened and look there for unaligned accesses. The Linux Device Driver book http://lwn.net/Kernel/LDD3/ has a nice section on data alignment in chapter 11. I definitely recommend to buy it, it is a great reference. -- Uli Kunitz - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Zd1211-devs mailing list - http://zd1211.ath.cx/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] [2.6.18-rc2, zd1211rw] connection problems
On 06-08-12 21:41 Guennadi Liakhovetski wrote: 20:53:50: usb 1-1.4: handle_retry_failed_int() retry failed interrupt 20:54:43: usb 1-1.4: handle_retry_failed_int() retry failed interrupt It is not a failed interrupt. It is simply an interrupt that notifies, that a packet has been sent several times because no ACK from the receiving station could be received. It's pretty normal and I get it also once in a while. -- Uli Kunitz - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Zd1211-devs mailing list - http://zd1211.ath.cx/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] unreliable signal level
On 06-08-03 18:22 Peter Lueg wrote:
Hi,
In 10m distance (access point to client) I have a greater signal level
as in 1m distance ?!
I add a printk about status-signal_strength in fill_rx_stat() and see
the same.
How does it possible?
As Linus says: Documentation is always wrong. Daniel discovered
it just recently. The problem is that my percent computation code
is now wrong. For fixing it I have done measurements with five ZD1211
devices. This time I want to make sure it is right. Patches will
be available over the next few days.
If you want to recheck status-signal_strength directly, use this
simple patch:
diff --git a/zd_mac.h b/zd_mac.h
index ecf1f78..6e390ff 100644
--- a/zd_mac.h
+++ b/zd_mac.h
@@ -87,9 +87,9 @@ struct rx_length_info {
#define RX_LENGTH_INFO_TAG 0x697e
struct rx_status {
+ u8 signal_quality_cck;
/* rssi */
u8 signal_strength;
- u8 signal_quality_cck;
u8 signal_quality_ofdm;
u8 decryption_type;
u8 frame_status;
--
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.phpp=sourceforgeCID=DEVDEV
___
Zd1211-devs mailing list - http://zd1211.ath.cx/
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] Is it possible to take only a one driver binaryfor both zd1211 and zd1211b?
On 06-08-01 11:25 Jose Pascual wrote: Will be a backport for rewritten driver zd1211rw for 2.4.x? I will not stop anybody from doing it. This is a hobby and I'm concentrating to programm the best driver possible for 2.6. -- 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.phpp=sourceforgeCID=DEVDEV ___ Zd1211-devs mailing list - http://zd1211.ath.cx/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] zd1211rw ICV mismatch
On 06-08-01 18:26 Peter Lueg wrote: I try your HEAD from http://www.deine-taler.de/zd1211/zd1211.git and WEP104 is working The ICV mismatch error is not longer present. Thanks a lot. I'm actually enjoying reading such messages. :-) Here the results of my tests (PXA270): Access point (cisco1100): with Open Authentication Client: WEP128 with open authentication is working. Access point: with Shared Authentication Client: WEP128 with shared authentication (restricted) is working Access point: with Open Authentication and Shared Authentication Client: WEP128 with shared authentication (restricted) crashed (see above, configuration file in attachment). Tests with a laptop have the same result like PXA270. But I have no visible oops. The kernel oops looks like there is a problem in the softmac. I've put it on my TODO list, but fixing the softmac is currently not my priority. I try do get the device plumbing right. Daniel has done the encryption stuff. How is the actual state for WPA? Is there something to heed? I have not checked it personally, but it should somehow work. But there appears to be interaction problems with the softmac. But we will come to it. -- 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.phpp=sourceforgeCID=DEVDEV ___ Zd1211-devs mailing list - http://zd1211.ath.cx/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] Question - Dropping of Packets with CRC Errors
On 06-07-31 02:56 Clifton Watson wrote: Hi guys, I have a question regarding the ZyDAS ZD1211 driver. Are the packets containing CRC errors dropped by the firmware or driver? I would greatly appreciate your help. Thanks. The CRC is computed on the device, but the packet is sent to the host with the error flag set and is then dropped, but this gives the host the possibility to update its statistics and change parameters. I'm not aware of any way to switch the behaviour off. -- 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.phpp=sourceforgeCID=DEVDEV ___ Zd1211-devs mailing list - http://zd1211.ath.cx/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] Is it possible to take only a one driver binary for both zd1211 and zd1211b?
On 06-07-31 18:11 Jose Pascual wrote: I know that driver is for zd1211 and zd1211b but It's not possible to generate a only one binary driver for both. It's possible to do it in two different binary and using modprobe it's posible to resolve it, but It's a loss of memory mainly in embedded systems, The vendor driver uses #ifdefs to distinguish between zd1211 and zd1211b. The rewritten driver zd1211rw combines suppport for both chips in a single module zd1211rw.ko. -- 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.phpp=sourceforgeCID=DEVDEV ___ Zd1211-devs mailing list - http://zd1211.ath.cx/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] Firmware mismatch? Hawking HWL2 and zd1211rw
Hi, Currently I am running ZD1211LnxDrv_2_15_0_0 from the Zydas site (which seems to have a later version of the firmware - can I use a standard converter to change the header files from the hex to bin?). We are using already the new firmware, which has changed around 2_13_0_0. It can be found in the snapshot directory or the git trees. Links can be found in http://zd1211.ath.cx/wiki/DriverRewrite. Please set the environment variable ZD1211_DEBUG=y before you are running the Makefile of the out of tree driver. This will create a lot of DEBUG messages, which might give us a clue. I would recommend to use my tree, because I fixed a pretty serious bug over the weekend, which however doesn't explain your problems. There is also a patch which solved a firmware problem with a Zyxel device. I concentrate on zd1211rw, so I cannot help with the ZYDAS driver. Regards, Uli ZD1211LnxDrv_2_15_0_0 is also not working on the HWL2. Here is some info about what it does:- Zydas zd1211 2_15_0_0 under kernel 2.6.17.7 -- - extract from /var/log/debug - Jul 30 14:25:48 conquest3 kernel: zd1211:bulk out: wMaxPacketSize = 40 Jul 30 14:25:48 conquest3 kernel: zd1211:bulk in: wMaxPacketSize = 40 Jul 30 14:25:48 conquest3 kernel: zd1211:interrupt in: wMaxPacketSize = 40 Jul 30 14:25:48 conquest3 kernel: zd1211:interrupt in: int_interval = 1 Jul 30 14:25:48 conquest3 kernel: zd1211:bulk out: wMaxPacketSize = 40 Jul 30 14:25:48 conquest3 kernel: zd1211:macp-release != EEPVer Jul 30 14:25:48 conquest3 kernel: zd1211:uImgLength = e00 Jul 30 14:25:48 conquest3 kernel: zd1211:translen = e00 Jul 30 14:25:48 conquest3 kernel: zd1211:uCodeOfst = ee00 Jul 30 14:25:48 conquest3 kernel: zd1211:result = e00 Jul 30 14:25:48 conquest3 kernel: zd1211:FIRMWARE_CONFIRM = 1 Jul 30 14:25:48 conquest3 kernel: zd1211:USB Download Boot code success Jul 30 14:25:48 conquest3 kernel: zd1211:uImgLength = e88 Jul 30 14:25:48 conquest3 kernel: zd1211:translen = e88 Jul 30 14:25:48 conquest3 kernel: zd1211:uCodeOfst = f895 Jul 30 14:25:48 conquest3 kernel: zd1211:result = e88 Jul 30 14:25:48 conquest3 kernel: zd1211:FIRMWARE_CONFIRM = 1 Jul 30 14:25:48 conquest3 kernel: zd1211:USB Download Boot code success Jul 30 14:25:48 conquest3 kernel: zd1211:uImgLength = 12a Jul 30 14:25:48 conquest3 kernel: zd1211:translen = 12a Jul 30 14:25:48 conquest3 kernel: zd1211:uCodeOfst = f800 Jul 30 14:25:48 conquest3 kernel: zd1211:result = 12a Jul 30 14:25:48 conquest3 kernel: zd1211:uImgLength = 1400 Jul 30 14:25:48 conquest3 kernel: zd1211:translen = 1000 Jul 30 14:25:48 conquest3 kernel: zd1211:uCodeOfst = ee00 Jul 30 14:25:48 conquest3 kernel: zd1211:result = 1000 Jul 30 14:25:48 conquest3 kernel: zd1211:translen = 400 Jul 30 14:25:48 conquest3 kernel: zd1211:uCodeOfst = f600 Jul 30 14:25:48 conquest3 kernel: zd1211:result = 400 Jul 30 14:25:48 conquest3 kernel: zd1211:FIRMWARE_CONFIRM = 1 Jul 30 14:25:48 conquest3 kernel: zd1211:USB Download Boot code success Jul 30 14:25:48 conquest3 kernel: zd1211:MAC address = 00:0e:xx:xx:xx:xx (edited MAC above in case you want to pass this on) Jul 30 14:25:48 conquest3 kernel: zd1211:AddrEntryTable = f7d4 Jul 30 14:25:48 conquest3 kernel: zd1211:RF_Mode = 0004 Jul 30 14:25:48 conquest3 kernel: zd1211:Pure B-Mode Jul 30 14:25:48 conquest3 kernel: zd1211:File opening did not success Jul 30 14:25:49 conquest3 kernel: zd1211:AllowedChannel = 07ff Jul 30 14:25:49 conquest3 kernel: zd1211:LinkLEDn = 200 Jul 30 14:25:49 conquest3 kernel: zd1205: (exit) zd1205_config, /home/ael/hardware/HWL2/ZD1211LnxDrv_2_15_0_0/src/zd1205.c line 2571 Jul 30 14:25:50 conquest3 kernel: zd1205: (exit) zd1205_init, /home/ael/hardware/HWL2/ZD1211LnxDrv_2_15_0_0/src/zd1205.c line 8352 And from /var/log/messages:- Jul 30 14:25:47 conquest3 kernel: usb 1-1: new full speed USB device using uhci_ hcd and address 2 Jul 30 14:25:47 conquest3 kernel: usb 1-1: configuration #1 chosen from 1 choice Jul 30 14:25:48 conquest3 kernel: Jul 30 14:25:48 conquest3 kernel: _ _ Jul 30 14:25:48 conquest3 kernel: |__ / _| _ \ / \ / ___| Jul 30 14:25:48 conquest3 kernel: / / | | | | | |/ _ \ \___ \ Jul 30 14:25:48 conquest3 kernel: / /| |_| | |_| / ___ \ ___) | Jul 30 14:25:48 conquest3 kernel: /\__, |/_/ \_\/ Jul 30 14:25:48 conquest3 kernel: |___/ Jul 30 14:25:48 conquest3 kernel: zd1211 - version 2.15.0.0 Jul 30 14:25:48 conquest3 kernel: vendor_id = 0ace Jul 30 14:25:48 conquest3 kernel: product_id = 1211 Jul 30 14:25:48 conquest3 kernel: USB 1.1 Host Jul 30 14:25:48 conquest3 kernel: Release Ver = 4802 Jul 30 14:25:48 conquest3 kernel: EEPORM Ver = 4330 Jul 30 14:25:48 conquest3 kernel: Finsih download Firmware. Ready to reboot Jul 30 14:25:48 conquest3 last message repeated 2 times
Re: [zd1211-devs] zd1211rw ICV mismatch
On 06-07-28 10:28 Peter Lueg wrote: Hi, I use a ZD1211 with AL7230B RF chip and the latest zd1211rw driver version from Daniel. Firmware version: zd1211_fw_2006-07-21 CPU: PXA270 Without encryption everything works fine. When I use WEP encryption than comes the following problems: 1) iwconfig eth0 key open mykey The authentication and association process is successfully . The zd12211 can sent arp requests (see it with kismet and tcpdump) and received the arp replay. Everything looks fine until the ICV will be checked. Here the error messages: ieee80211: I ieee80211_rx_frame_decrypt decryption failed (SA=00:40:96:a1:a2:46) res=-2 ieee80211: I ieee80211_rx_frame_decrypt Decryption failed ICV mismatch (key 0) 2) iwconfig eth0 key restricted mykey The authentication and association process failed. In this case I become the following error: SoftMAC: Sent Authentication Request to MYMAC SoftMAC: Shared Key Authentication failed due to a missing challenge. Any ideas? We had some problems recently with WEP, but Daniel fixed them recently. I have pulled his patches, so Daniel and me have now the same master head tree. Your problem looks like a softmac issue, so I would like to know, which Linux kernel you are using. I'm using here John Linville's wireless tree, a modified 2.6.18-rc1. WEP is working here. 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.phpp=sourceforgeCID=DEVDEV ___ Zd1211-devs mailing list - http://zd1211.ath.cx/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] zd1211: Fails during usb initialization
On 06-07-19 14:39 Gopi V. wrote: Can you please tell me the exact location of the driver. The following page contains information about the driver. Links for download can be found under Trees. But please read the whole page. http://zd1211.ath.cx/wiki/DriverRewrite -- 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.phpp=sourceforgeCID=DEVDEV ___ Zd1211-devs mailing list - http://zd1211.ath.cx/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] zd1211: Fails during usb initialization
On 06-07-18 02:06 Gopi wrote: Hi all, I have a USB WLAN stick (with zd1211 chipset). I’m using ZD1211LnxDrv_2_13_0_0.tardriver for it. It is working on a PC environment running Fedora Core 3, Linux 2.6 Kernel. But when I tried it on my custom platform (based on ARM) after cross compiling, I got the following error messages after I plug-in the module and then insmod the driver. Gopi, you are using the original driver from the chip vendor Zydas. This mailing list is used by free software developers, who maintain it's own version of the vendor driver. Daniel Drake and I have worked on a rewrite (zd1211rw) of the driver. This driver doesn't provide all the features of the vendor driver currently, but it runs on multiple platforms. We don't have any reports for ARM yet, but the driver works on x86, x86-64 and PPC32. So it might worth a try, please report any problems on this mailing list. 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.phpp=sourceforgeCID=DEVDEV ___ Zd1211-devs mailing list - http://zd1211.ath.cx/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] [zd1211rw] first impressions (one step closer)
On 06-06-13 19:47 C.S: wrote: This protection fault differs to the others but should be nonetheless useful. Looks like a problem in disconnect. Could you use the latest version of the driver from my git tree http://www.deine-taler.de/zd1211.git/zd1211 It includes the latest patch from Daniel Drake for disconnect(). It would also nice to see, whether you have the same problem with a stock Linus kernel and non-tainted kernel. Everything else doesn't look to bad Regards, Uli -- Uli Kunitz ___ Zd1211-devs mailing list - http://zd1211.ath.cx/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] [zd1211rw] first impressions (one step closer)
On 06-06-10 22:09 C.S: wrote: here some output to make things clear: zd1211rw 2-3:1.0: error ioread32(CR_REG1): -11 It looks like, that you have IO problems on the USB bus. Do you use cable to connect the device? How about using another cable? You may also compile the driver with DEBUG defined. If you use the out-of-tree driver than setting the environment variable ZD1211_DEBUG to y is sufficient (check the file Kbuild). It will give us some more information, but I still believe in the IO problems. Regards, Uli -- Uli Kunitz ___ Zd1211-devs mailing list - http://zd1211.ath.cx/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] [zd1211rw] first impressions (one step closer)
On 06-06-11 20:23 C.S: wrote: Unfortunately i get some general protection fault which i didn't managed to get saved to disk (not even with sysrq) nonetheless i found some other log from earlier of the day, but i can't tell if this is an error because zd1211 and zd1211rw have been loaded at the same time. perhaps it might be useful though i try to get another output of the general protection fault of zd1211rw. Please make sure, to remove zd1211 before you are loading zd1211rw. It is an interesting bug however. Regards, Uli -- Uli Kunitz ___ Zd1211-devs mailing list - http://zd1211.ath.cx/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] What is 1205 ??
Hi Mark! I saw in: http://zd1211.ath.cx/wiki/DriverRewrite the following ink for a presentation on zd1211 in the Linux Wireless developers summit: http://www.deine-taler.de/zd1211/zd1211-wisu.pdf This link is not valid. The presentation is available again. Regards, Uli On Mon, 24 Apr 2006, Mark Ryden wrote: Hello, Thanks! I saw in: http://zd1211.ath.cx/wiki/DriverRewrite the following ink for a presentation on zd1211 in the Linux Wireless developers summit: http://www.deine-taler.de/zd1211/zd1211-wisu.pdf This link is not valid. Is there another site with this presentation ? or can this be fixed ? Regards, Mark On 4/23/06, Ulrich Kunitz [EMAIL PROTECTED] wrote: Hello Mark, What is the 1205 ? is it some chipset ? a controller? I see that zd1211.c uses a struct called zd1205_private , and also methods like zd1205_open() and zd1205_init() in zd1205.c. For the driver rewrite (zd1211rw) I had to look into this. It appears that the ZD1205 has been a WLAN chip (baseband processor) with an PCI interface. The ZD1211 wraps an USB interface around the ZD1205. For the driver, they simply hacked the zd1211 interface on the existing code and used ifdefs for it. We don't make that distinction in rewrite project, because I've yet to be able to buy a ZD1205 card and to test it. These data sheets could be improved, if vendors would mention the chip, that they are using there. Ciao, Uli -- Ulrich Kunitz - [EMAIL PROTECTED] --- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd___ Zd1211-devs mailing list - http://zd1211.ath.cx/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs -- Ulrich Kunitz - [EMAIL PROTECTED] --- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Zd1211-devs mailing list - http://zd1211.ath.cx/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
