The following reply was made to PR usb/122539; it has been noted by GNATS.
From: John Hein jh...@timing.com
To: bug-follo...@freebsd.org, artur.zabron...@gmail.com
Cc: u...@freebsd.org
Subject: Re: usb/122539: kernel panic: ohci_abort_xfer: not in process context
Date: Thu, 12 Mar 2009 11:44:21
The following reply was made to PR usb/122539; it has been noted by GNATS.
From: John Hein jh...@timing.com
To: bug-follo...@freebsd.org
Cc:
Subject: Re: usb/122539: kernel panic: ohci_abort_xfer: not in process context
Date: Thu, 12 Mar 2009 12:14:42 -0600
The code to pull the patch out
Note: this is not specific to ohci or the device originally used in
this PR. The problem is more generic.
This happens for us when hardware flow control is turned on when using
a usb serial device (specifically an ftdi based one). Eventually if
hardware flow has to kick in and RTS is to be set,
Does anyone have thought about what it would take to support access to
individual usb devices "natively" from a bhyve vm?
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to
blubee blubeeme wrote at 08:42 +0800 on Aug 22, 2018:
> On Wed, Aug 22, 2018 at 8:26 AM John Hein wrote:
>
> Does anyone have thought about what it would take to support access to
> individual usb devices "natively
