Re: [BRLTTY] Looking at iManufacturer and iProduct for generic USB devices?
Dave Mielke, on Sun 20 Nov 2016 23:34:08 -0500, wrote: > This has now been done. Thanks! So HIMS and HandyTech don't even have a personalized manufacturer field... But at least we won't bother devices which have one. Samuel ___ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: BRLTTY@mielke.cc For general information, go to: http://mielke.cc/mailman/listinfo/brltty
Re: [BRLTTY] Looking at iManufacturer and iProduct for generic USB devices?
This has now been done. -- Dave Mielke | 2213 Fox Crescent | The Bible is the very Word of God. Phone: 1-613-726-0014 | Ottawa, Ontario | http://Mielke.cc/bible/ EMail: d...@mielke.cc | Canada K2A 1H7 | http://FamilyRadio.org/ ___ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: BRLTTY@mielke.cc For general information, go to: http://mielke.cc/mailman/listinfo/brltty
Re: [BRLTTY] Looking at iManufacturer and iProduct for generic USB devices?
Hello, Mariusz, this is a follow-up for debian's bug Bug#667616: brltty greedily grabs serial ports, ftdi_sio loses connection Dave Mielke, on Sun 20 Nov 2016 14:14:43 -0500, wrote: > [quoted lines by Samuel Thibault on 2016/11/20 at 19:25 +0100] > > >Any progress on this? > > No. The discussion stopped before I was convinced I knew exactly what was > wanted, and then I got involved in other stuff and forgot about it. > > As I recall: The idea is to use those strings to help decide if a brltty > driver > should claim a device or not. If a driver specifies a lsit of manufacturer > strings then one of them must match, and/or if a driver speifies a lsit of > product strings then one of them must match. Is that how you understand it? Yes, that's the idea. Very most probably we'll want to include a list of manufacturer strings, since there is very little probability that they change much. > My lingring concern is that, if this feature were being used by a driver, > then > it'd stop recognizing a braille deivce if a slight change were made to those > strings. Yes, that's why I said that this kind of detection could be made an option. Typically by default brltty would not try to match these, but for the cases where we want to check the matches, we'd enable the option. I'm here thinking of auto-start of brltty on all standard systems or installers. In these cases, you want to be sure that it's a braille device plugged in. > Maybe that's an invalid concetrn. Do you know if there's some kind of > understanding that those strings need to be stable or are they really just > intended/used for human readability? I don't know. Perhaps you could discuss directly with the person who raised the concern? I have Cc-ed him. Samuel ___ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: BRLTTY@mielke.cc For general information, go to: http://mielke.cc/mailman/listinfo/brltty
Re: [BRLTTY] Looking at iManufacturer and iProduct for generic USB devices?
[quoted lines by Samuel Thibault on 2016/11/20 at 19:25 +0100] >Any progress on this? No. The discussion stopped before I was convinced I knew exactly what was wanted, and then I got involved in other stuff and forgot about it. As I recall: The idea is to use those strings to help decide if a brltty driver should claim a device or not. If a driver specifies a lsit of manufacturer strings then one of them must match, and/or if a driver speifies a lsit of product strings then one of them must match. Is that how you understand it? My lingring concern is that, if this feature were being used by a driver, then it'd stop recognizing a braille deivce if a slight change were made to those strings. Maybe that's an invalid concetrn. Do you know if there's some kind of understanding that those strings need to be stable or are they really just intended/used for human readability? -- Dave Mielke | 2213 Fox Crescent | The Bible is the very Word of God. Phone: 1-613-726-0014 | Ottawa, Ontario | http://Mielke.cc/bible/ EMail: d...@mielke.cc | Canada K2A 1H7 | http://FamilyRadio.org/ ___ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: BRLTTY@mielke.cc For general information, go to: http://mielke.cc/mailman/listinfo/brltty
Re: [BRLTTY] Looking at iManufacturer and iProduct for generic USB devices?
Hello, Any progress on this? Samuel ___ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: BRLTTY@mielke.cc For general information, go to: http://mielke.cc/mailman/listinfo/brltty
Re: [BRLTTY] Looking at iManufacturer and iProduct for generic USB devices?
Dave Mielke, on Thu 13 Oct 2016 12:14:12 -0400, wrote: > [quoted lines by Samuel Thibault on 2016/10/13 at 17:14 +0200] > > >AIUI, for now brltty only matches idVendor and idProduct. I'm saying it > >could also at least match iManufacturer against "FTDI", to avoid e.g. > >matching *all* 0403:6001 adaptors, but only those which haven't > >programmed it to something else than "FTDI". > > I'm not sure how volatile that'd be as it's possible that a manufacturer > will, > at some point, customize the strings. If we restrict it too much then a > manufacturer action like that would require a new brltty release. Perhaps we can add another parameter to control that? Samuel ___ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: BRLTTY@mielke.cc For general information, go to: http://mielke.cc/mailman/listinfo/brltty
Re: [BRLTTY] Looking at iManufacturer and iProduct for generic USB devices?
[quoted lines by Samuel Thibault on 2016/10/13 at 17:14 +0200] >AIUI, for now brltty only matches idVendor and idProduct. I'm saying it >could also at least match iManufacturer against "FTDI", to avoid e.g. >matching *all* 0403:6001 adaptors, but only those which haven't >programmed it to something else than "FTDI". I'm not sure how volatile that'd be as it's possible that a manufacturer will, at some point, customize the strings. If we restrict it too much then a manufacturer action like that would require a new brltty release. -- Dave Mielke | 2213 Fox Crescent | The Bible is the very Word of God. Phone: 1-613-726-0014 | Ottawa, Ontario | http://Mielke.cc/bible/ EMail: d...@mielke.cc | Canada K2A 1H7 | http://FamilyRadio.org/ ___ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: BRLTTY@mielke.cc For general information, go to: http://mielke.cc/mailman/listinfo/brltty
Re: [BRLTTY] Looking at iManufacturer and iProduct for generic USB devices?
Dave Mielke, on Thu 13 Oct 2016 11:09:56 -0400, wrote: > [quoted lines by Samuel Thibault on 2016/10/13 at 17:05 +0200] > >We haven't added such option to Debian. We do want the devices which use > >generic IDs to be working in Debian without the user to have to know he > >has to set this option to yes. > > Then I don't understand how a whitelist would help since the default is to > recognize it. AIUI, for now brltty only matches idVendor and idProduct. I'm saying it could also at least match iManufacturer against "FTDI", to avoid e.g. matching *all* 0403:6001 adaptors, but only those which haven't programmed it to something else than "FTDI". Samuel ___ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: BRLTTY@mielke.cc For general information, go to: http://mielke.cc/mailman/listinfo/brltty
Re: [BRLTTY] Looking at iManufacturer and iProduct for generic USB devices?
[quoted lines by Samuel Thibault on 2016/10/13 at 17:05 +0200] >We haven't added such option to Debian. We do want the devices which use >generic IDs to be working in Debian without the user to have to know he >has to set this option to yes. Then I don't understand how a whitelist would help since the default is to recognize it. -- Dave Mielke | 2213 Fox Crescent | The Bible is the very Word of God. Phone: 1-613-726-0014 | Ottawa, Ontario | http://Mielke.cc/bible/ EMail: d...@mielke.cc | Canada K2A 1H7 | http://FamilyRadio.org/ ___ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: BRLTTY@mielke.cc For general information, go to: http://mielke.cc/mailman/listinfo/brltty
Re: [BRLTTY] Looking at iManufacturer and iProduct for generic USB devices?
Dave Mielke, on Thu 13 Oct 2016 10:57:40 -0400, wrote: > [quoted lines by Samuel Thibault on 2016/10/13 at 16:40 +0200] > > >Ok, but it's still better to only whitelist those, and not devices for > >which the manufacturer does have programmed something else. > > Yes, that's true. For the current situation, though, isn't brltty being > installed with: braille-device usb:genericDevices=no We haven't added such option to Debian. We do want the devices which use generic IDs to be working in Debian without the user to have to know he has to set this option to yes. Samuel ___ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: BRLTTY@mielke.cc For general information, go to: http://mielke.cc/mailman/listinfo/brltty
Re: [BRLTTY] Looking at iManufacturer and iProduct for generic USB devices?
[quoted lines by Samuel Thibault on 2016/10/13 at 16:40 +0200] >Ok, but it's still better to only whitelist those, and not devices for >which the manufacturer does have programmed something else. Yes, that's true. For the current situation, though, isn't brltty being installed with: braille-device usb:genericDevices=no -- Dave Mielke | 2213 Fox Crescent | The Bible is the very Word of God. Phone: 1-613-726-0014 | Ottawa, Ontario | http://Mielke.cc/bible/ EMail: d...@mielke.cc | Canada K2A 1H7 | http://FamilyRadio.org/ ___ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: BRLTTY@mielke.cc For general information, go to: http://mielke.cc/mailman/listinfo/brltty
Re: [BRLTTY] Looking at iManufacturer and iProduct for generic USB devices?
Dave Mielke, on Thu 13 Oct 2016 10:36:36 -0400, wrote: > [quoted lines by Samuel Thibault on 2016/10/13 at 01:24 +0200] > > >We continue getting reports that brltty happens to get installed on some > >box for some reason, and the generic USB probing interferes with > >non-braille devices. We have notably received: > > > >“for example it grabbed my USB<->1wire > >adapter which had "manufacturer" and "product" field customized: > > > >Device: ID 0403:6001 Future Technology Devices International, Ltd > ... > >Couldn't Brltty use the iManufacturer field (and perhaps iProduct field > >too) to whitelist only devices which have the expected iManufacturer? > > Yes, it certainly could. The problem with this case - 0403:6001 - is that > those > HandyTech devices haven't been programmed to be particularly unique. > >Manufacturer: FTDI >Product: USB <-> Serial Ok, but it's still better to only whitelist those, and not devices for which the manufacturer does have programmed something else. Samuel ___ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: BRLTTY@mielke.cc For general information, go to: http://mielke.cc/mailman/listinfo/brltty
Re: [BRLTTY] Looking at iManufacturer and iProduct for generic USB devices?
[quoted lines by Samuel Thibault on 2016/10/13 at 01:24 +0200] >We continue getting reports that brltty happens to get installed on some >box for some reason, and the generic USB probing interferes with >non-braille devices. We have notably received: > >“for example it grabbed my USB<->1wire >adapter which had "manufacturer" and "product" field customized: > >Device: ID 0403:6001 Future Technology Devices International, Ltd ... >Couldn't Brltty use the iManufacturer field (and perhaps iProduct field >too) to whitelist only devices which have the expected iManufacturer? Yes, it certainly could. The problem with this case - 0403:6001 - is that those HandyTech devices haven't been programmed to be particularly unique. Manufacturer: FTDI Product: USB <-> Serial -- Dave Mielke | 2213 Fox Crescent | The Bible is the very Word of God. Phone: 1-613-726-0014 | Ottawa, Ontario | http://Mielke.cc/bible/ EMail: d...@mielke.cc | Canada K2A 1H7 | http://FamilyRadio.org/ ___ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: BRLTTY@mielke.cc For general information, go to: http://mielke.cc/mailman/listinfo/brltty
[BRLTTY] Looking at iManufacturer and iProduct for generic USB devices?
Hello, We continue getting reports that brltty happens to get installed on some box for some reason, and the generic USB probing interferes with non-braille devices. We have notably received: “for example it grabbed my USB<->1wire adapter which had "manufacturer" and "product" field customized: Device: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x0403 Future Technology Devices International, Ltd idProduct 0x6001 FT232 USB-Serial (UART) IC bcdDevice6.00 iManufacturer 1 MERA-PROJEKT iProduct2 USB <-> 1Wire (MP00202) iSerial 3 MPYRNJYY bNumConfigurations 1 ” Couldn't Brltty use the iManufacturer field (and perhaps iProduct field too) to whitelist only devices which have the expected iManufacturer? Samuel ___ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: BRLTTY@mielke.cc For general information, go to: http://mielke.cc/mailman/listinfo/brltty
