From owner-freebsd-hackers Tue Mar 23 13:22:18 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id ABE7714CE3 for ; Tue, 23 Mar 1999 13:22:16 -0800 (PST) (envelope-from hibma@skylink.it) Received: from heidi.plazza.it (va-139.skylink.it [194.177.113.139]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id WAA30967; Tue, 23 Mar 1999 22:20:40 +0100 Received: from localhost (localhost.plazza.it [127.0.0.1]) by heidi.plazza.it (8.8.8/8.8.5) with SMTP id XAA02558; Tue, 23 Mar 1999 23:16:33 +0100 (CET) Date: Tue, 23 Mar 1999 23:16:33 +0100 (CET) From: Nick Hibma X-Sender: n_hibma@heidi.plazza.it Reply-To: Nick Hibma To: Doug Rabson Cc: FreeBSD hackers mailing list Subject: Re: scheduling a function call from int routines In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The usbd thing we are doing right now, but I don't like it, as you have to pick up the pieces when the daemon is killed. Try it and you will see what I mean. Lot's of failed transfers. Most probably could be solved, I agree, but not as a first priority, A kernel thread would be easier and I do remember something like that being mentioned somewhere in the manpages. Any chance you know where to find it? Nick > > As in, a USB returns in an interrupt the message the fact that the > > connection status of one of the ports or suspend status has changed. I > > cannot start checking the ports from that interrupt routine, because I > > need to transfer data to the device to make that work. > > > > thanks. > > I think you need a kernel thread, either spawned during system startup or > via a system call from usbd. > > -- > Doug Rabson Mail: dfr@nlsystems.com > Nonlinear Systems Ltd. Phone: +44 181 442 9037 > > > -- e-Mail: hibma@skylink.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message