Hi,
From: Nick Hudson , Date: Sun, 05 Apr 2015 10:12:50 +0100
> On 04/05/15 01:52, Ryo ONODERA wrote:
>> Hi,
>>
>> I believe that following patch is good for us because my USB modem
>> device
>> is bad information and it should be treated as special case.
>>
>> Index: sys/dev/usb/umodem.c
>>
On Wed, Apr 08, 2015 at 11:50:29AM +0100, Nick Hudson wrote:
> and with umodem.c:1.66 removed?
usbd_new_device bus=0xbfc9205c port=3 depth=2 speed=3
usbd_new_device: adding unit addr=3, rev=200, class=2, subclass=0, protocol=0,
maxpacket=64, len=18, speed=3
usbd_new_device: new dev (addr 3), dev=
On 04/07/15 20:52, Christof Meerwald wrote:
On Sun, Apr 05, 2015 at 10:12:50AM +0100, Nick Hudson wrote:
Can you boot with -xv flags and an updated -current kernel with USB_DEBUG
and usbdebug set? I've add some more debug output to the kernel.
this is the output I get when plugging in the USB c
On Sun, Apr 05, 2015 at 10:12:50AM +0100, Nick Hudson wrote:
> Can you boot with -xv flags and an updated -current kernel with USB_DEBUG
> and usbdebug set? I've add some more debug output to the kernel.
this is the output I get when plugging in the USB cable with the
-current kernel (leaving umod
From: Nick Hudson , Date: Sun, 05 Apr 2015 10:12:50 +0100
> On 04/05/15 01:52, Ryo ONODERA wrote:
>> Hi,
>>
>> I believe that following patch is good for us because my USB modem
>> device
>> is bad information and it should be treated as special case.
>>
>> Index: sys/dev/usb/umodem.c
>> =
On 04/05/15 01:52, Ryo ONODERA wrote:
Hi,
I believe that following patch is good for us because my USB modem device
is bad information and it should be treated as special case.
Index: sys/dev/usb/umodem.c
===
RCS file: /cvsroot/src
Hi,
I believe that following patch is good for us because my USB modem device
is bad information and it should be treated as special case.
Index: sys/dev/usb/umodem.c
===
RCS file: /cvsroot/src/sys/dev/usb/umodem.c,v
retrieving revis
On Sat, Apr 04, 2015 at 04:13:28PM +0100, Nick Hudson wrote:
> On 04/04/15 10:55, Christof Meerwald wrote:
> > if (uaa->class == UICLASS_CDC_DATA &&
> >uaa->subclass == UISUBCLASS_DATA)
> > return (UMATCH_IFACECLASS_IFACESUBCLASS);
> >
> >which clearly looks wrong to me.
>
> Ye
On 04/04/15 10:55, Christof Meerwald wrote:
On Sat, Apr 04, 2015 at 04:15:40PM +0900, Ryo ONODERA wrote:
From: Christof Meerwald , Date: Sat, 4 Apr 2015 08:42:23
+0200
On Sat, Apr 04, 2015 at 08:50:01AM +0900, Ryo ONODERA wrote:
Please remove cdce(4) and umodem(4) entries from your kernel con
From: Christof Meerwald , Date: Sat, 4 Apr 2015 11:55:35
+0200
> On Sat, Apr 04, 2015 at 04:15:40PM +0900, Ryo ONODERA wrote:
>> From: Christof Meerwald , Date: Sat, 4 Apr 2015 08:42:23
>> +0200
>> > On Sat, Apr 04, 2015 at 08:50:01AM +0900, Ryo ONODERA wrote:
>> >> Please remove cdce(4) and umo
On Sat, Apr 04, 2015 at 04:15:40PM +0900, Ryo ONODERA wrote:
> From: Christof Meerwald , Date: Sat, 4 Apr 2015 08:42:23
> +0200
> > On Sat, Apr 04, 2015 at 08:50:01AM +0900, Ryo ONODERA wrote:
> >> Please remove cdce(4) and umodem(4) entries from your kernel configuration
> >> file (your device sh
Hi,
From: Christof Meerwald , Date: Sat, 4 Apr 2015 08:42:23
+0200
> On Sat, Apr 04, 2015 at 08:50:01AM +0900, Ryo ONODERA wrote:
>> Please remove cdce(4) and umodem(4) entries from your kernel configuration
>> file (your device should be recognized as ugen(4)) and run
>> $ gcc -o probe_usb prob
From: Martin Husemann , Date: Sat, 4 Apr 2015 07:15:20 +0200
> On Sat, Apr 04, 2015 at 08:50:01AM +0900, Ryo ONODERA wrote:
>> blymn@ provides me the program to print interface detail.
>> See http://mail-index.netbsd.org/current-users/2014/01/21/msg024127.html
>> or attached probe_usb.c .
>
> Yes
On Sat, Apr 04, 2015 at 08:50:01AM +0900, Ryo ONODERA wrote:
> Please remove cdce(4) and umodem(4) entries from your kernel configuration
> file (your device should be recognized as ugen(4)) and run
> $ gcc -o probe_usb probe_usb.c
> # ./probe_usb /dev/ugen0.00
# ./probe_usb /dev/ugen0.00
length:
On Sat, Apr 04, 2015 at 08:50:01AM +0900, Ryo ONODERA wrote:
> blymn@ provides me the program to print interface detail.
> See http://mail-index.netbsd.org/current-users/2014/01/21/msg024127.html
> or attached probe_usb.c .
Yes, that is what I was thinking of - we should make it work with any usb
Hi,
From: Martin Husemann , Date: Fri, 3 Apr 2015 19:44:09 +0200
> On Fri, Apr 03, 2015 at 05:02:15PM +0200, Christof Meerwald wrote:
>> I have now enabled the umodem driver again, but reverted
>> /src/sys/dev/usb/umodem.c to revision 1.65 and it's still working for
>> me. So looks like the chang
On Fri, Apr 03, 2015 at 05:02:15PM +0200, Christof Meerwald wrote:
> I have now enabled the umodem driver again, but reverted
> /src/sys/dev/usb/umodem.c to revision 1.65 and it's still working for
> me. So looks like the changes done in r1.66 result in the umodem
> driver kicking in (and interferi
On Fri, Apr 03, 2015 at 12:08:00PM +0200, Christof Meerwald wrote:
> I then recompiled the NetBSD kernel with the umodem driver disabled
> and it suddenly started working:
>
> cdce0 at uhub2 port 3 configuration 1 interface 0
> cdce0: Linux 4.0.0-rc4-bone0 with musb-hdrc RNDIS/Ethernet Gadget, rev
On Fri, Apr 03, 2015 at 04:05:27PM +0200, Martin Husemann wrote:
> On Fri, Apr 03, 2015 at 12:08:00PM +0200, Christof Meerwald wrote:
> > But surely there must be a better way to get it working...
> What devices/interfaces does it present?
> You should be able to query with usbdevs(8).
# usbdevs -
On Fri, Apr 03, 2015 at 12:08:00PM +0200, Christof Meerwald wrote:
> But surely there must be a better way to get it working...
What devices/interfaces does it present?
You should be able to query with usbdevs(8).
Martin
Hi,
so I just installed NetBSD on my ODROID-C1 and it seems to work quite
well. But one thing that didn't work out of the box was trying to
establish a network connection via USB to my Beaglebone Black (running
Linux with g_ether).
On the Linux side I have the g_ether modules loaded with option
u
21 matches
Mail list logo
