On Tuesday 07 September 2010 21:13:25 Nick Hibma wrote:
Maybe you can make PR on the issue and assign it to USB. Currently
there is no way of knowing which /dev/cuaUXXX belongs to which USB
device. Probably we can add the USB bus and address number as a part
of the device coordinates. So
Two things are needed:
1) path to the device so you can distinguish two identical devices.
2) map u3gN to cuaUX.Y
My problem is the latter:
Processing event '+u3g0 vendor=0x0af0 product=0x7601 devclass=0xff
devsubclass=0xff sernum= release=0x intclass=0xff intsubclass=0xff
at
On Wed, Sep 08, 2010 at 09:00:46AM +0200, Hans Petter Selasky wrote:
On Tuesday 07 September 2010 21:13:25 Nick Hibma wrote:
Maybe you can make PR on the issue and assign it to USB. Currently
there is no way of knowing which /dev/cuaUXXX belongs to which USB
device. Probably we can add
Maybe you can make PR on the issue and assign it to USB. Currently there is
no way of knowing which /dev/cuaUXXX belongs to which USB device. Probably
we can add the USB bus and address number as a part of the device
coordinates. So that /dev/ugen1.1 only creates /dev/cuaU1.1.xxx entries.
And
On Thursday 06 May 2010 11:07:00 Alexandr Rybalko wrote:
On Wed, 5 May 2010 21:57:20 +0200
Hans Petter Selasky hsela...@c2i.net wrote:
Hi,
Thanks for all good ideas. Can you give some feedback on the following
solution:
http://p4web.freebsd.org/@@19?ac=10
Looks interest, can
On Wed, 5 May 2010 21:57:20 +0200
Hans Petter Selasky hsela...@c2i.net wrote:
Hi,
Thanks for all good ideas. Can you give some feedback on the following
solution:
http://p4web.freebsd.org/@@19?ac=10
Looks interest, can You send to me patch to svn head. (So more difference in
p4,
Hi,
Maybe you can make PR on the issue and assign it to USB. Currently there is no
way of knowing which /dev/cuaUXXX belongs to which USB device. Probably we can
add the USB bus and address number as a part of the device coordinates. So
that /dev/ugen1.1 only creates /dev/cuaU1.1.xxx entries.
On Wednesday 05 May 2010 09:52:15 Hans Petter Selasky wrote:
Hi,
Maybe you can make PR on the issue and assign it to USB. Currently there is
no way of knowing which /dev/cuaUXXX belongs to which USB device. Probably
we can add the USB bus and address number as a part of the device
Hi,
On Wed, 5 May 2010 10:46:30 +0200
Milan Obuch freebsd-...@dino.sk wrote:
On Wednesday 05 May 2010 09:52:15 Hans Petter Selasky wrote:
Hi,
Maybe you can make PR on the issue and assign it to USB. Currently there is
no way of knowing which /dev/cuaUXXX belongs to which USB device.
Hi,
Thanks for all good ideas. Can you give some feedback on the following
solution:
http://p4web.freebsd.org/@@19?ac=10
--HPS
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any
At 04:48 AM 12/14/2009, Hans Petter Selasky wrote:
On Monday 14 December 2009 08:42:04 Ed Schouten wrote:
Hello Trevor,
* Trevor Blackwell t...@tlb.org wrote:
I can't seem to find a way to match USB serial ports tty names. I
have two serial USB devices, which I can distinguish easily
On Sunday 13 December 2009 23:45:07 Trevor Blackwell wrote:
I can't figure out how to map the USB devices to tty names.
I think this is not possible at the moment. And there is no TTY API to pass
this information. Please provide a patch.
--HPS
___
* Hans Petter Selasky hsela...@c2i.net wrote:
Also TTY should have a printout in dmesg, which unit is create if this
string is specified.
Just patch your ucom driver to print that information. It doesn't belong
in the TTY layer. Can't you just extend usbconfig to also dump that
information?
--
On Monday 14 December 2009 09:53:51 Ed Schouten wrote:
* Hans Petter Selasky hsela...@c2i.net wrote:
Also TTY should have a printout in dmesg, which unit is create if this
string is specified.
Just patch your ucom driver to print that information. It doesn't belong
in the TTY layer. Can't
USB_IOCTL_GET_PARENT_NAME
That seems like the right approach. Is there only ever one associated
parent driver? Are there cases where it should report both a serial
network interface?
--
Trevor Blackwell650 776 7870t...@tlb.org
On Monday 14 December 2009 18:44:01 Trevor Blackwell wrote:
USB_IOCTL_GET_PARENT_NAME
That seems like the right approach. Is there only ever one associated
parent driver? Are there cases where it should report both a serial
network interface?
That's a good question how to best standardise
I can't seem to find a way to match USB serial ports tty names. I
have two serial USB devices, which I can distinguish easily from
usbconfig show_ifdrv
ugen2.2: URG-Series USB Driver Hokuyo Data Flex for USB at usbus2,
cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON
ugen2.2.0: umodem0: Hokuyo
Hello Trevor,
* Trevor Blackwell t...@tlb.org wrote:
I can't seem to find a way to match USB serial ports tty names. I
have two serial USB devices, which I can distinguish easily from
usbconfig show_ifdrv
snip
and they result in two ttys:
/dev/cuaU0
/dev/cuaU1
Be
I cannot seem to find a way to identify serial ports. I have two
serial USB devices, which I can distinguish easily from usbconfig:
ugen2.3: URG-Series USB Driver Hokuyo Data Flex for USB at usbus2,
cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON
ugen0.2: USB-Serial Controller Prolific Technology
19 matches
Mail list logo
