From owner-freebsd-hackers@FreeBSD.ORG Tue Jul 15 10:01:59 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5F88C37B401 for ; Tue, 15 Jul 2003 10:01:59 -0700 (PDT) Received: from smtp.web.de (smtp02.web.de [217.72.192.151]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1C07C43FA3 for ; Tue, 15 Jul 2003 10:01:58 -0700 (PDT) (envelope-from nakal@web.de) Received: from [80.135.116.154] (helo=[80.135.116.154]) by smtp.web.de with esmtp (TLSv1:DES-CBC3-SHA:168) (WEB.DE 4.98 #244) id 19cTBc-0003sW-00 for freebsd-hackers@freebsd.org; Tue, 15 Jul 2003 19:01:56 +0200 From: Martin To: freebsd-hackers@freebsd.org In-Reply-To: <3F13A769.F7AF78CA@mindspring.com> References: <1058119316.547.22.camel@klotz.local> <3F13A769.F7AF78CA@mindspring.com> Content-Type: text/plain Message-Id: <1058288512.1026.30.camel@klotz.local> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.3 Date: 15 Jul 2003 19:01:52 +0200 Content-Transfer-Encoding: 7bit Sender: nakal@web.de Subject: Re: USB device programming with ugen [Solved] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jul 2003 17:01:59 -0000 On Tue, 2003-07-15 at 09:04, Terry Lambert wrote: > The attach should have failed, if it didn't have an interrupt. Somehow uhci0 didn't have interrupt, but it managed to find the webcam on ugen0. Don't ask me why. I have attached my logs below. You can see many devices sharing same irq. I don't know what line 2 means exactly, but if it means that my USB-controller was assigned irq 11, it could lock several important devices at once, if IRQs are not handled properly. In new logs uhci0 was found configured on irq 9. Earlier dmesg (from /var/log/messages): Jul 11 20:35:58 xxx kernel: uhci0: port 0xc000-0xc01f at device 7.2 on pci0 Jul 11 20:35:58 xxx kernel: pci_cfgintr: 0:7 INTD routed to irq 11 ... Jul 11 20:35:58 xxx kernel: ugen0: WINBOND W9967CF, rev 1.10/1.10, addr 2 ... Jul 11 20:35:58 xxx kernel: sym0: <875> port 0xc400-0xc4ff mem 0xe7002000-0xe7002fff,0xe7001000-0xe70010ff irq 11 at device 11.0 on pci0 ... Jul 11 20:35:58 xxx kernel: atapci1: port 0xd400-0xd4ff,0xd000-0xd003,0xcc00-0xcc07 irq 11 at device 19.0 on pci0 Jul 11 20:35:58 xxx kernel: ata2: at 0xcc00 on atapci1 Jul 11 20:35:58 xxx kernel: atapci2: port 0xe000-0xe0ff,0xdc00-0xdc03,0xd800-0xd807 irq 11 at device 19.1 on pci0 Jul 11 20:35:58 xxx kernel: ata3: at 0xd800 on atapci2 Now dmesg: uhci0: port 0xc000-0xc01f irq 9 at device 7.2 on pci0 ... ugen0: WINBOND W9967CF, rev 1.10/1.10, addr 2 ... sym0: <875> port 0xc400-0xc4ff mem 0xe7002000-0xe7002fff,0xe7001000-0xe70010ff irq 11 at device 11.0 on pci0 ... atapci1: port 0xd400-0xd4ff,0xd000-0xd003,0xcc00-0xcc07 irq 11 at device 19.0 on pci0 ata2: at 0xcc00 on atapci1 atapci2: port 0xe000-0xe0ff,0xdc00-0xdc03,0xd800-0xd807 irq 11 at device 19.1 on pci0