Nearly all the PCI drivers have tables of vendor/device IDs.
They all have slightly different forms, and none of them use
a common macro / format like USB. So each driver needs a
line or two to describe the table so we can extract the data
from the .ko. Some drivers don't have lists, and those will
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203289
Bug ID: 203289
Summary: BeagleBone Black invalid USB target descriptors
Product: Base System
Version: 11.0-CURRENT
Hardware: Any
OS: Any
Status: New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203289
--- Comment #1 from Ed Maste ---
For reference here is the Device Descriptor for the stock Linux BBB image:
ugen1.5: at usbus1, cfg=0 md=HOST spd=HIGH
(480Mbps) pwr=ON (2mA)
bLength = 0x0012
bDescriptorType = 0x0001
bcdUSB = 0x02
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203289
Hans Petter Selasky changed:
What|Removed |Added
CC||hsela...@freebsd.org
--- Com
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203289
--- Comment #3 from Hans Petter Selasky ---
More specifically this structure:
const struct usb_temp_device_desc usb_template_serialnet = {
.getStringDesc = &serialnet_get_string_desc,
.ppConfigDesc = serialnet_configs,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203289
--- Comment #4 from Ed Maste ---
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.
On Wed, Sep 23, 2015 at 9:26 AM, Warner Losh wrote:
> Nearly all the PCI drivers have tables of vendor/device IDs.
> They all have slightly different forms, and none of them use
> a common macro / format like USB. So each driver needs a
> line or two to describe the table so we can extract the da