Date: Wed, 23 Sep 2015 20:04:03 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-usb@FreeBSD.org Subject: [Bug 203289] BeagleBone Black invalid USB target descriptors Message-ID: <bug-203289-17-eIJYYWchEk@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-203289-17@https.bugs.freebsd.org/bugzilla/> References: <bug-203289-17@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203289 --- Comment #4 from Ed Maste <emaste@freebsd.org> --- Hi HPS, thanks for the reply. I put this in to keep track of this issue while investigating it; I'll have a look at updating the descriptor values in the template when I get set up for BBB builds in a bit. I was able to get a functional USB serial port in Windows with the BBB image despite the device qualifier descriptor issue, it's just that the USB tool complained. As an aside, we'll need to do something different to support the network interface with Windows hosts. This page makes it sound like Windows has support for the CDC Ethernet Networking Control Model: https://msdn.microsoft.com/en-us/library/windows/hardware/ff537037%28v=vs.85%29.aspx but I wasn't able to actually find any evidence of that (looking for Class_02 and SubClass_06). It looks like the options are: * 3rd party CDC Ethernet class drivers for Windows http://www.thesycon.de/eng/usb_network.shtml These are proprietary and Windows 10 is "coming soon" * Implement CDC MBIM target in FreeBSD Likely fairly straightforward. MBIM does not Ethernet encapsulate frames, I think it's just IP. * Implement RNDIS target in FreeBSD The host side (if_urndis.c) is pretty small - we could probably implement it without much trouble. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-203289-17-eIJYYWchEk>