On 09/28 05:56, Mateusz Lenik wrote:
> On Thu, Sep 28, 2017 at 07:39:58PM +0200, tu...@posteo.de wrote:
> > The interesting thing is: I have a pololu avr programmer (v20, an
> > ISP-programmer it is), which uses also /dev/ttyACM...and that
> > one works fine. I plugged it in simultanously to ensure
On Thu, Sep 28, 2017 at 07:39:58PM +0200, tu...@posteo.de wrote:
> The interesting thing is: I have a pololu avr programmer (v20, an
> ISP-programmer it is), which uses also /dev/ttyACM...and that
> one works fine. I plugged it in simultanously to ensure all drivers
> get loaded...and then I plugge
On 09/28 05:03, Mateusz Lenik wrote:
> On Thu, Sep 28, 2017 at 05:03:14PM +0200, tu...@posteo.de wrote:
> > I have one of these:
> >
> > Bus 006 Device 018: ID 16d0:0753 MCS Digistump DigiSpark
> >
> > ... snip ...
> >
> > SUBSYSTEMS=="usb", ATTRS{idVendor}=="16d0", ATTRS{idProduct}=="0753",
> > M
On Thu, Sep 28, 2017 at 05:03:14PM +0200, tu...@posteo.de wrote:
> I have one of these:
>
> Bus 006 Device 018: ID 16d0:0753 MCS Digistump DigiSpark
>
> ... snip ...
>
> SUBSYSTEMS=="usb", ATTRS{idVendor}=="16d0", ATTRS{idProduct}=="0753",
> MODE:="0666"
> KERNEL=="ttyACM*", ATTRS{idVendor}=="16d0
Hi,
may bet this is part of the theory about the relationship
between the forest and the trees...I am trying this already
for a longer time.
I have one of these:
When plugged in, lsusb reports those as:
Bus 006 Device 018: ID 16d0:0753 MCS Digistump DigiSpark
and in the verbose form:
Bus 006
5 matches
Mail list logo
