From: Ricardo Ribalda Delgado
Date: Mon, 4 Aug 2014 11:11:49 +0200
> After this patch:
>
> [ 32.985530] hso: drivers/net/usb/hso.c: Option Wireless
> [ 33.000452] hso 2-1.4:1.7: Not our interface
> [ 33.001849] usbcore: registered new interface driver hso
>
> root@qt5022:~# ls /dev/ttyHS
On Mon, 2014-08-04 at 11:11 +0200, Ricardo Ribalda Delgado wrote:
> After this patch:
>
> [ 32.985530] hso: drivers/net/usb/hso.c: Option Wireless
> [ 33.000452] hso 2-1.4:1.7: Not our interface
> [ 33.001849] usbcore: registered new interface driver hso
>
> root@qt5022:~# ls /dev/ttyHS*
>
On Tue, 2014-08-05 at 08:59 +0200, Ricardo Ribalda Delgado wrote:
> Hello Dan.
>
> I have also been able to start/stop the gps via the gps control port
> (ttyHS2) and get nmea data port through the gps port. (ttyHS1)
>
> Please tell me if you need more tests
No, this looks good enough. Because
Hello Dan.
I have also been able to start/stop the gps via the gps control port
(ttyHS2) and get nmea data port through the gps port. (ttyHS1)
Please tell me if you need more tests
Regards!
root@qt5022:~# cat /sys/class/tty/*/hsotype
Diagnostic
GPS
GPS Control
Application
Control
Modem
root@qt5
On Mon, 2014-08-04 at 11:20 +0200, Ricardo Ribalda Delgado wrote:
> Suggested-by: Dan Williams
Before we apply this patch though, can you grab for the following for
me?
cat /sys/class/tty/*/hsotype
and lets see if the firmware actually responds. Also, do you get an
'hso0' network interface as
Suggested-by: Dan Williams
On Mon, Aug 4, 2014 at 11:11 AM, Ricardo Ribalda Delgado
wrote:
> After this patch:
>
> [ 32.985530] hso: drivers/net/usb/hso.c: Option Wireless
> [ 33.000452] hso 2-1.4:1.7: Not our interface
> [ 33.001849] usbcore: registered new interface driver hso
>
> root@qt5022:
After this patch:
[ 32.985530] hso: drivers/net/usb/hso.c: Option Wireless
[ 33.000452] hso 2-1.4:1.7: Not our interface
[ 33.001849] usbcore: registered new interface driver hso
root@qt5022:~# ls /dev/ttyHS*
/dev/ttyHS0 /dev/ttyHS1 /dev/ttyHS2 /dev/ttyHS3 /dev/ttyHS4
/dev/ttyHS5
root@