From owner-freebsd-mobile Sun Oct 3 11:47:29 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from dingo.cdrom.com (castles530.castles.com [208.214.165.94]) by hub.freebsd.org (Postfix) with ESMTP id 38A8614A00 for ; Sun, 3 Oct 1999 11:47:26 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id LAA06910; Sun, 3 Oct 1999 11:36:54 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199910031836.LAA06910@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Peter Radcliffe Cc: FreeBSD Mobile List Subject: Re: PAO3 and FreeBSD3.3 In-reply-to: Your message of "Sun, 03 Oct 1999 14:29:42 EDT." <19991003142942.D9480@pir.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 03 Oct 1999 11:36:54 -0700 From: Mike Smith Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Matt White probably said: > > What's happening is that my laptop, a Sony PCG-719c, has a uhci usb > > controller. FreeBSD recoginizes the controller, but for some reason the > > controller wants to place itself at IRQ 255, which sounds suspiciouly like > > a -1 gettig stuck into an unsigned char but I really haven't spent a lot > > of time trying to figure out why this is happening. > > > > create_intr: requested irq255 too high, limit is 15 > > I believe the usb support isn't doing pnp yet. In the BIOS change the > PNP OS setting to 'no' and you'll get a real IRQ set by the BIOS. What you mean is "the PCI bus is not doing resource allocation yet". More updated USB code will refuse to connect to a device that doesn't have interrupts enabled. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message