search for: dump_str

...> Does OpenBSD have something like FreeBSD's usbconfig? You could try retrieving other string descriptors to see if this is something that got moved (and iOEMInformation happened to point to the right string), or if it is just a mistake in the source code. > > usbconfig -u 0 -a 1 dump_string 3 I haven't explored to see if OpenBSD has the equivalent (or similar) command. On the other hand, I did have a test system set up with FreeBSD 11.0 (AMD64), nut-2.7.4_1 from the FreeBSD pkg. :) dmseg excerpt for the UPS: ugen1.2: <CPS> at usbus1 Result of the command, where &q...

On 5/30/2017 10:47 PM, Charles Lepple wrote: > On May 22, 2017, at 11:13 AM, Mike <the.lists at mgm51.com> wrote: >> >> On 5/21/2017 10:39 AM, Charles Lepple wrote: [snip] > Even though the CPS sub-driver has been written already, I would like to take a look at the raw "explore" mode output: > >

On Jun 5, 2017, at 11:21 AM, Mike <the.lists at mgm51.com> wrote: > > Result of the command, where "n" is incremented in a loop: > > # usbconfig -u 1 -a 2 dump_string n > STRING_0x00 = 0x04, 0x03, 0x09, 0x04 > STRING_0x01 = <CP1500AVRLCDa> > STRING_0x02 = <CTHGN200xxxx> > STRING_0x03 = <CPS> > STRING_0x04 = <PbAcid> > STRING_0x05 = <BF01512BA31> > STRING_0x06 = <read error> > STRING_0x07 = &l...

...s remembering). Does OpenBSD have something like FreeBSD's usbconfig? You could try retrieving other string descriptors to see if this is something that got moved (and iOEMInformation happened to point to the right string), or if it is just a mistake in the source code. usbconfig -u 0 -a 1 dump_string 3