Date: Thu, 6 Jan 2000 21:17:31 +0100 (CET) From: Nick Hibma <n_hibma@webweaving.org> To: Bill Paul <wpaul@FreeBSD.ORG> Cc: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/sys/dev/usb if_kue.c Message-ID: <Pine.BSF.4.20.0001062114560.698-100000@localhost> In-Reply-To: <20000106154245.E45A7155C6@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> No: the device only seems to attach once. The info KLSI sent me mentions > the following: > > // Our code will have the USB pullup line drop, wait far a bit, > // execute the downloaded code at interrupt 100 (0x64). > // > // (4) The LAST MODULE downloaded will have to turn on the USB pullup line > // so the host machine can now see the "new" device. > > I'm not sure what this means, but once the firmware is loaded and running, > the device continues working without the hub driver or usbd reacting in > any special way. Shoot, that is wrong. It should reset the device. the USB stack does not reread the descriptors and gets things all wrong. If for example the firmware adds a new pipe to the device, it won't be available until the device is reset. The reason why I am asking is that AnchorChips has a chip that resets only the USB stack half after the firmware has been uploaded. Serial port devices work that way. On the USB stack side you see a reconnect happening that detaches the device the firmware was uploaded to and shows up with a new device with a new VID, PID or RID, indicating that the configuration of the device has changed. Cheers, Nick -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.20.0001062114560.698-100000>