On Mon, Oct 29, 2007 at 05:21:48PM -0500, Paul B Schroeder wrote:
>
>
> Greg KH wrote:
>> On Tue, Oct 23, 2007 at 01:57:59PM -0500, Paul B Schroeder wrote:
>>> I'm trying to get console messages from both a typical serial port and
>>> via a USB serial device using the io_ti driver. You can see my
On Mon, Oct 29, 2007 at 05:21:48PM -0500, Paul B Schroeder wrote:
> I finally got a chance to play with it a bit, it seems to work if I add
> 'CONSOLE=/dev/ttyUSB0' to my kernel command line for init to read that from
> the
> environment. I shouldn't have to do that though.. It also seems that
Greg KH wrote:
> On Tue, Oct 23, 2007 at 01:57:59PM -0500, Paul B Schroeder wrote:
>> I'm trying to get console messages from both a typical serial port and via a
>> USB
>> serial device using the io_ti driver. You can see my kernel command line in
>> the
>> messages below. Using kernel ver
On Mon, 29 Oct 2007, Phil Endecott wrote:
> Dear Experts,
>
> I have a simple user-space driver that uses usbdevfs.
>
> As I understand it, there is no way to select() on data being available
> on an endpoint. So I have one thread per endpoint which does an
> ioctl(USBDEVFS_BULK) read. This
Dear Experts,
I have a simple user-space driver that uses usbdevfs.
As I understand it, there is no way to select() on data being available
on an endpoint. So I have one thread per endpoint which does an
ioctl(USBDEVFS_BULK) read. This is fine, until I need to shut down
(that part of) the dr
