[riot-notifications] [RIOT-OS/RIOT] Have usable VID/PIDs for standard situations and prototype ones for examples (#12273)
notifications at github.com
Mon Sep 30 13:20:20 CEST 2019
> Especially, I'm not sure we get away with a single number for the "just what the board ships" case, as that may include serial and/or Ethernet only if the application demands a stdio or a network interface, resulting in different USB behaviors.
This is also how I've always understood VID/PID pairs, as one product with a specific and fixed feature set.
> as in Linux and MacOS things always work out of the box, and things like udev can hook into any attribute to decide permissions/groups/names etc
Linux and MacOS seem to match USB interface class and subclass numbers. Not sure if it is possible to use that with Windows too.
IMHO the bootloader really requires a separate PID as it makes DFU flashing a lot more convenient. I would prefer to also have a VID/PID for examples, but I can imagine that they don't allow that use case.
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the notifications