> In article <[EMAIL PROTECTED]>,
> Mike Smith  <[EMAIL PROTECTED]> wrote:
> > You're not tying up an interrupt; PCI interrupts are shared.  With the 
> > new PCI code, even if you turn it off, we'll just turn it right back on 
> > again. 8)
> But if IRQ 5 is assigned to the uhci device, then it's not available
> for use by an ISA device, is it?  Or am I all mixed up?

If you're using IRQ 5 for an ISA device, the BIOS will give the PCI 
controller another IRQ (as long as you've told it this). 

> > The problem appears to be a bug in the UHCI driver.
> Could be, and I certainly don't know much about this code.  But
> it seems like the driver is being given reason to assume it has a
> working device when it doesn't really have one.  I assume the device
> is unusable without its interrupt, so shouldn't it fail at probe or
> attach time?

Yes, it should.  It's not bright enough to do that yet.

... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also.  But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view.  [Dr. Fritz Todt]
           V I C T O R Y   N O T   V E N G E A N C E

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to