Dave Mielke, on Mon 04 Jul 2016 09:27:38 -0400, wrote: > [quoted lines by Samuel Thibault on 2016/07/04 at 07:26 +0200] > > >> >I see that the md driver was added to the 0403/6001 USB ID autodetection > >> >udev rule. Is it really safe to add it? (we used to have issues with at, > >> >ce, and mm, which we disabled in the Debian packaging) > >> > >> As long as only non-generic rules are released, there shouldn't be a > >> problem. > > > >I'm not sure to understand exactly what you mean. > > The fact that yet another braille display is using the same generic USB to > serial adapter doesn't change anything. The only thing that matters is > whether > or not that generic device is caught by the udev rules.
Let's explain: in Debian we do use a udev rule for 0403/6001 because there are popular devices which use this generic ID. We however have to limit the set of drivers that we enable to hm and ht, and notably we removed at, ce and mm, because when a handytech Device is plugged, they were bogusly discovering it (conflicting protocols). So my question means: will the md driver pose the same kind of issue, or is it safe to enable it along hm and ht? Actually, perhaps upstream brltty itself should not enable all these drivers in the generic udev file it ships, since it is well-known that there is no way for brltty to discover by itself which one should be used, and thus I'd say only the most popular non-conflicting ones should be enabled by default (the user can still override 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
