From owner-cvs-all Thu Jan 6 7:42:47 2000 Delivered-To: cvs-all@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id E45A7155C6; Thu, 6 Jan 2000 07:42:45 -0800 (PST) Subject: Re: cvs commit: src/sys/dev/usb if_kue.c In-Reply-To: from Nick Hibma at "Jan 6, 2000 3: 5:21 pm" To: n_hibma@webweaving.org Date: Thu, 6 Jan 2000 07:42:45 -0800 (PST) Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 840 Message-Id: <20000106154245.E45A7155C6@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk > > Does the device reset after the firmware has been loaded? Reset as in > reattach to the bus. 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. > If it does, you should split the driver in two, > with one part the firmware uploader and the second part the driver for > the firmware. If it did I might have done that already. However it seems fine as it is. -Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message