matthieu castet wrote:
Daniel Drake wrote:
Matthieu CASTET wrote:
Thanks for looking into all that. This just started happening on one
of my devices (ZD1211B) - it cannot survive a rmmod/insmod cycle
without me having to unplug it. Same problem with the vendor driver.
Same for reboots.
it is the same problem that I have! I have resolved plug peripheral after
the pc start or the reboot!
http://www.nabble.com/file/4430/grep_error_-110.txt grep_error_-110.txt
Norman Jonas-4 wrote:
Hi,
could it be that zd1211rw ( kernel 2.6.18-rc4 ) leaves the device in a
bugged
Matthieu CASTET wrote:
I use a small program to dump the memory :
http://castet.matthieu.free.fr/tmp/debug_ctrl0.c
I compared the eeprom state before and after firmware load.
I notice only 0xffe9-0x changed.
Also 0xfff7-0x where like memory address (and of course
LOAD_VECT_SIZE =
Hi,
On Thu, 21 Sep 2006 19:22:54 +, Matthieu CASTET wrote:
PS : I don't understand with usb_reset_device before upload_firmware
doesn't seem to work.
in fact usb_reset_device does nothing here. I am not able to do a
rmmod/modprobe.
I need to unplug the device.
Daniel, Ulrich is it
Matthieu CASTET wrote:
Daniel, Ulrich is it possible to know if the firmware is already loaded ?
I wanted to use zd_ioread16_locked(chip, version, FW_FIRMWARE_VER);, but
it need context that aren't available at firmware_upload time.
I don't know, and we generally don't get to know fine details
