Re: udev rules for wedo

2011-07-15 Thread Martin Langhoff 
On Thu, Jul 14, 2011 at 1:52 PM, Jerry Vonau jvo...@shaw.ca wrote:
 Looks to me that what is provided by scratch should be part of
 olpc-utils.

Yes. For 11.3.0 I'm planning to either update the rules provided in
olpc-utils or split it off to a separate package - I've already posted
a review request for a suitable pkg.

This is becase we'll have several different rpms providing libs that
can use wedo and nxt.



m
-- 
 martin.langh...@gmail.com
 mar...@laptop.org -- Software Architect - OLPC
 - ask interesting questions
 - don't get distracted with shiny stuff  - working code first
 - http://wiki.laptop.org/go/User:Martinlanghoff
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

udev rules for wedo

2011-07-14 Thread Jerry Vonau 
Hi all:

Playing around with wedo, I've found that scratch is providing udev
rules for wedo and there are rules installed by olpc-utils. I'm
wondering if the rules provided by scratch should be used in place of or
in conjunction with the olpc provided rules in /etc/udev/rules.d. Here
are the contents of the 2 files for F11.

30-olpc-wedo.rules:
 # Lego WeDo
SYSFS{idVendor}==0694, SYSFS{idProduct}==0003, GROUP=dialout,
MODE=0660

45-lego-wedo.rules:
# Lego WeDo
SYSFS{idVendor}==0694, SYSFS{idProduct}==0003, MODE=0666

Looks to me that what is provided by scratch should be part of
olpc-utils. 

Jerry 

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: udev rules for wedo

2011-07-14 Thread Paul Fox 
jerry wrote:
  Hi all:
  
  Playing around with wedo, I've found that scratch is providing udev
  rules for wedo and there are rules installed by olpc-utils. I'm
  wondering if the rules provided by scratch should be used in place of or
  in conjunction with the olpc provided rules in /etc/udev/rules.d. Here
  are the contents of the 2 files for F11.
  
  30-olpc-wedo.rules:
   # Lego WeDo
  SYSFS{idVendor}==0694, SYSFS{idProduct}==0003, GROUP=dialout,
  MODE=0660
  
  45-lego-wedo.rules:
  # Lego WeDo
  SYSFS{idVendor}==0694, SYSFS{idProduct}==0003, MODE=0666
  
  Looks to me that what is provided by scratch should be part of
  olpc-utils. 

i believe scratch supplies rules because (at least at the time) it
could be installed on XO distributions that didn't include udev
rules at all.

and since the 'olpc' user is a member of group 'dialout', i think these
rules are equivalent in practice.  (except for use by 'other',
and i'm not sure how that would happen on an XO.)   both rules
give the olpc user read/write access to the device.

are you seeing a conflict or other problem?

paul

  
  Jerry 
  
  ___
  Devel mailing list
  Devel@lists.laptop.org
  http://lists.laptop.org/listinfo/devel

=-
 paul fox, p...@laptop.org
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: udev rules for wedo

2011-07-14 Thread Rafael Ortiz 
On Thu, Jul 14, 2011 at 1:05 PM, Paul Fox p...@laptop.org wrote:

 jerry wrote:
   Hi all:
  
   Playing around with wedo, I've found that scratch is providing udev
   rules for wedo and there are rules installed by olpc-utils. I'm
   wondering if the rules provided by scratch should be used in place of or
   in conjunction with the olpc provided rules in /etc/udev/rules.d. Here
   are the contents of the 2 files for F11.
  
   30-olpc-wedo.rules:
# Lego WeDo
   SYSFS{idVendor}==0694, SYSFS{idProduct}==0003, GROUP=dialout,
   MODE=0660
  
   45-lego-wedo.rules:
   # Lego WeDo
   SYSFS{idVendor}==0694, SYSFS{idProduct}==0003, MODE=0666
  
   Looks to me that what is provided by scratch should be part of
   olpc-utils.

 i believe scratch supplies rules because (at least at the time) it
 could be installed on XO distributions that didn't include udev
 rules at all.

 This is my impresion too, last versions of scratch included these rules.



 and since the 'olpc' user is a member of group 'dialout', i think these
 rules are equivalent in practice.  (except for use by 'other',
 and i'm not sure how that would happen on an XO.)   both rules
 give the olpc user read/write access to the device.

 are you seeing a conflict or other problem?

 paul

  
   Jerry
  
   ___
   Devel mailing list
   Devel@lists.laptop.org
   http://lists.laptop.org/listinfo/devel

 =-
  paul fox, p...@laptop.org

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel