From: Daniel Pimentel <d4n1@d4n1.org>
To: ludo@gnu.org
Cc: help-guix@gnu.org
Subject: Re: Microscheme failed
Date: Thu, 14 Jul 2016 11:22:09 -0300 [thread overview]
Message-ID: <677969efa60aeb2d2b9bfa6669605b7e@d4n1.org> (raw)
In-Reply-To: <87inwlhlgv.fsf@gnu.org>
>> (define avrispmkii-udev-rule
>> (udev-rule "90-avrispmkii.rules"
>> "\
>> SUBSYSTEM!=\"usb\", ACTION!=\"add\", GOTO=\"avrisp_end\"
>>
>> # Atmel Corp. JTAG ICE mkII
>> ATTR{idVendor}==\"03eb\", ATTR{idProduct}==\"2103\", MODE=\"660\",
>> GROUP=\"dialout\"
>> # Atmel Corp. AVRISP mkII
>> ATTR{idVendor}==\"03eb\", ATTR{idProduct}==\"2104\", MODE=\"660\",
>> GROUP=\"dialout\"
>> # Atmel Corp. Dragon
>> ATTR{idVendor}==\"03eb\", ATTR{idProduct}==\"2107\", MODE=\"660\",
>> GROUP=\"dialout\"
>>
>> LABEL=\"avrisp_end\"\n"))
>>
>> (operating-system
>> …
>> (services (cons* (modify-services %desktop-services
>> (udev-service-type config =>
>> (udev-configuration
>> (inherit config)
>> (rules (append
>> (udev-configuration-rules config)
>> (list
>> avrispmkii-udev-rule))))))))
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> Should we add this as an optional service or to the default set of udev
> rules?
>
It works. I think a good solution as optional service now.
Thanks,
Note: Ricardo, I reported avr-toolchain bug in bug-guix. I'll try debug
and fix it.
--
Daniel Pimentel (aka d4n1)
next prev parent reply other threads:[~2016-07-14 14:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-03 22:12 Microscheme failed Daniel Pimentel
2016-07-04 6:14 ` Ricardo Wurmus
2016-07-04 8:10 ` Ludovic Courtès
2016-07-04 14:55 ` udev rules and system configuration (was: Microscheme failed) Ricardo Wurmus
2016-07-04 15:46 ` udev rules and system configuration Ludovic Courtès
2016-07-04 18:05 ` Ricardo Wurmus
2016-07-05 8:34 ` Ludovic Courtès
2016-07-14 14:22 ` Daniel Pimentel [this message]
2016-07-04 12:30 ` Microscheme failed Daniel Pimentel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=677969efa60aeb2d2b9bfa6669605b7e@d4n1.org \
--to=d4n1@d4n1.org \
--cc=help-guix@gnu.org \
--cc=ludo@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.