On Mon, Nov 5, 2018 at 9:04 AM Ian Lepore wrote:
> I've always wanted a way to add VID/PID combos to ugsensa's internal
> list on the fly, like via hints or sysctl or something, to make this
> kind of quick test easier. But I never find time to add the feature.
>
I have code to do this generical
On Sun, 2018-11-04 at 19:05 -0500, Mike Andrews wrote:
> On Fri, 2 Nov 2018, CeDeROM wrote:
>
> >
> > Try to add VID/PID of your device into a usbmodem driver. Use
> > configurations to see which one works with your device. Rebuild the
> > module/kernel, reboot, try it out untill success.
> >
>
Sorry, that would be USBSERIAL then if only UART-TO-USB is necessary, I
have also added custom FTDI based driver (KT-LINK JTAG/SWD/UART) interface
that way, just add VIP/PID to the list and it should work :-)
--
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
_
On Sun, Nov 4, 2018 at 5:06 PM Mike Andrews wrote:
> On Fri, 2 Nov 2018, CeDeROM wrote:
>
> > Try to add VID/PID of your device into a usbmodem driver. Use
> > configurations to see which one works with your device. Rebuild the
> > module/kernel, reboot, try it out untill success.
> >
> > After y
On Fri, 2 Nov 2018, CeDeROM wrote:
Try to add VID/PID of your device into a usbmodem driver. Use
configurations to see which one works with your device. Rebuild the
module/kernel, reboot, try it out untill success.
After your device is recognised by usbmodem and creates several cuaU*
devices..
Try to add VID/PID of your device into a usbmodem driver. Use
configurations to see which one works with your device. Rebuild the
module/kernel, reboot, try it out untill success.
After your device is recognised by usbmodem and creates several cuaU*
devices.. still Your device may require uploadin
On Fri, Nov 2, 2018, 22:11 Warner Losh wrote:
> On Fri, Nov 2, 2018 at 8:04 AM Andrey V. Elsukov
> wrote:
>
> > On 02.11.2018 16:59, Warner Losh wrote:
> > > All the commands for USB modems should be described here:
> > >
> > > https://www.usb.org/sites/default/files/CDC_EEM10.pdf
> > >
On Fri, Nov 2, 2018 at 8:04 AM Andrey V. Elsukov wrote:
> On 02.11.2018 16:59, Warner Losh wrote:
> > All the commands for USB modems should be described here:
> >
> > https://www.usb.org/sites/default/files/CDC_EEM10.pdf
> >
> > I'm sorry, but I don't have time currently to decode th
On 02.11.2018 16:59, Warner Losh wrote:
> All the commands for USB modems should be described here:
>
> https://www.usb.org/sites/default/files/CDC_EEM10.pdf
>
> I'm sorry, but I don't have time currently to decode the Linux traces
> and compare with FreeBSD.
>
>
> One thing to
On Fri, Nov 2, 2018 at 3:57 AM Hans Petter Selasky wrote:
> On 11/2/18 10:24 AM, Andrey V. Elsukov wrote:
> > On 02.11.2018 12:12, Hans Petter Selasky wrote:
> >>> # cu -l /dev/cuaU0
> >>> Connected
> >>>
> >>>
> >>>
> >>
> >> Did you try "-s" option to set another baudrate?
> >
> > Yes, the res
On 11/2/18 10:24 AM, Andrey V. Elsukov wrote:
On 02.11.2018 12:12, Hans Petter Selasky wrote:
# cu -l /dev/cuaU0
Connected
Did you try "-s" option to set another baudrate?
Yes, the result is the same.
# cu -s 115200 -l /dev/cuaU0
Connected
If I understand correctly from
https://
On 02.11.2018 12:12, Hans Petter Selasky wrote:
>> # cu -l /dev/cuaU0
>> Connected
>>
>>
>>
>
> Did you try "-s" option to set another baudrate?
Yes, the result is the same.
# cu -s 115200 -l /dev/cuaU0
Connected
If I understand correctly from
https://www.bit0.com/tmp/usbmon-ciscoasa-v
On 11/2/18 9:53 AM, Andrey V. Elsukov wrote:
On 02.11.2018 11:45, Hans Petter Selasky wrote:
And it seems in Linux it is handled by generic CDC ACM driver without
any quirks. So, I think the problem is with our umodem(4) or ucom(4)
driver.
No, I didn't.
The usbmon dumps above are still there,
On 02.11.2018 11:45, Hans Petter Selasky wrote:
>>> And it seems in Linux it is handled by generic CDC ACM driver without
>>> any quirks. So, I think the problem is with our umodem(4) or ucom(4)
>>> driver.
>>>
>> No, I didn't.
>>
>> The usbmon dumps above are still there, and if someone can sugges
On 11/2/18 1:01 AM, Mike Andrews wrote:
On 11/1/18 4:59 PM, Andrey V. Elsukov wrote:
On 27.09.2017 05:11, Mike Andrews wrote:
This is the USB read transfer. The other side is not returning any
data, so neither is "cu" printing anything. Maybe you can try to get a
similar trace from the system
On 11/1/18 4:59 PM, Andrey V. Elsukov wrote:
On 27.09.2017 05:11, Mike Andrews wrote:
This is the USB read transfer. The other side is not returning any
data, so neither is "cu" printing anything. Maybe you can try to get a
similar trace from the system where it works?
Looks to me like some ki
On 27.09.2017 05:11, Mike Andrews wrote:
>> This is the USB read transfer. The other side is not returning any
>> data, so neither is "cu" printing anything. Maybe you can try to get a
>> similar trace from the system where it works?
>>
>> Looks to me like some kind of protocol error, that the Cisc
On Tue, 19 Sep 2017, Hans Petter Selasky wrote:
On 09/19/17 18:15, Mike Andrews wrote:
12:03:37.726830 usbus4.3 SUBM-BULK-EP=0082,SPD=FULL,NFR=1,SLEN=0,IVAL=0
frame[0] READ 1024 bytes
flags 0xa
status 0xcf023
Hi,
Look for:
-BULK-EP=0082
This is the USB read transfer. T
On 09/19/17 18:15, Mike Andrews wrote:
12:03:37.726830 usbus4.3 SUBM-BULK-EP=0082,SPD=FULL,NFR=1,SLEN=0,IVAL=0
frame[0] READ 1024 bytes
flags 0xa
status 0xcf023
Hi,
Look for:
-BULK-EP=0082
This is the USB read transfer. The other side is not returning any data,
so neit
On Tue, 19 Sep 2017, Hans Petter Selasky wrote:
On 09/19/17 16:22, Mike Andrews wrote:
I'm trying to get the USB console of a Cisco ASA 5506-X firewall (not
terribly obscure hardware) talking to FreeBSD, and having some trouble. The
relevant dmesg at probe time is:
umodem0 on uhub7
umo
On 09/19/17 16:22, Mike Andrews wrote:
I'm trying to get the USB console of a Cisco ASA 5506-X firewall (not
terribly obscure hardware) talking to FreeBSD, and having some trouble.
The relevant dmesg at probe time is:
umodem0 on uhub7
umodem0:
on usbus4
umodem0: data interface 1, h
I'm trying to get the USB console of a Cisco ASA 5506-X firewall (not
terribly obscure hardware) talking to FreeBSD, and having some trouble.
The relevant dmesg at probe time is:
umodem0 on uhub7
umodem0: on usbus4
umodem0: data interface 1, has no CM over data, has no break
...and /dev
22 matches
Mail list logo