From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Daniel Pimentel <d4n1@d4n1.org>, help-guix@gnu.org
Subject: Re: Microscheme failed
Date: Mon, 04 Jul 2016 10:10:56 +0200 [thread overview]
Message-ID: <87inwlhlgv.fsf@gnu.org> (raw)
In-Reply-To: <87vb0mdj4w.fsf@elephly.net> (Ricardo Wurmus's message of "Mon, 04 Jul 2016 08:14:55 +0200")
Hello!
Ricardo Wurmus <rekado@elephly.net> skribis:
> For my AVR programmers I have this in my system configuration:
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> (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?
Ludo’.
next prev parent reply other threads:[~2016-07-04 8:11 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 [this message]
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 ` Microscheme failed Daniel Pimentel
2016-07-04 12:30 ` 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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87inwlhlgv.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=d4n1@d4n1.org \
--cc=help-guix@gnu.org \
--cc=rekado@elephly.net \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).