On Mon, Nov 28, 2016 at 9:31 AM, Marek Marczykowski-Górecki <[email protected]> wrote: > So, if it does not work for some type of devices, I would say it's an > upstream issue. > Any particular example?
In this case it was a JTAG programmer for an FPGA. But AFAICT: >> On 2016-11-28 03:29, Jean-Philippe Ouellet wrote: >> > Right now things only work if some application provides udev rules >> > changing ownership/permissions, or if a user observes things failing >> > and happens to know to go chmod stuff in /dev. And I think it may make sense to allow access for all (passed-through) devices, because for devices to be present in Qubes they need to be explicitly passed through, whereas this is not the case upstream. Upstream it may indeed make sense to protect some devices from access by default. -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/CABQWM_Dpbutp4wq9PQcBcbGU_OSDgFBt%3DCYwpyRL%2BjzXBjVN8Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
