Re: [Sugar-devel] Pulsing icons don't stop
On Sun, Jul 18, 2010 at 07:21, Gonzalo Odiard godi...@gmail.com wrote:
I am using systemtap in F13 to try to know what is doing sugar.
In my first test I found the pulsing icon in launcher.py never stop.
To monitor sugar-sesion I have a script stap-sugar-session.sh:
[gonz...@aronax sugar-jhbuild]$ cat stap-sugar-session.sh
SUGAR_SESSION_PID=`ps ax | grep sugar-session | grep -v grep | awk
'{printf(%s,$1)}'`
stap -t /usr/share/doc/python-libs-2.6.4/systemtap-sugar-3.stp -x
$SUGAR_SESSION_PID
The file /usr/share/doc/python-libs-2.6.4/systemtap-sugar-3.stp is a
modification of /usr/share/doc/python-libs-2.6.4/systemtap-example.stp, but
you can use it also.
If I start sugar-emulator and execute stap-sugar-session.sh I can see after
start a activity and stop the activity, the pulsing icon continue for ever.
It can be resolved applying the following patch, but I don't know if it's
the right solution. May be it's anything wrong with the properties.
[gonz...@aronax view]$ diff -u launcher.py launcher.py.new
--- launcher.py 2010-07-18 01:39:20.436252902 -0300
+++ launcher.py.new 2010-07-17 01:25:42.893632264 -0300
@@ -122,7 +122,7 @@
self.connect('destroy', self.__destroy_cb)
def __destroy_cb(self, box):
- self._activity_icon.pulsing = False
+ self._activity_icon.set_paused(True)
self._home.disconnect_by_func(self.__active_activity_changed_cb)
def zoom_in(self):
@@ -133,13 +133,13 @@
style.STANDARD_ICON_SIZE,
style.XLARGE_ICON_SIZE))
self._animator.start()
- self._activity_icon.pulsing = True
+ self._activity_icon.set_paused(False)
def __active_activity_changed_cb(self, model, activity):
if activity.get_activity_id() == self._activity_id:
- self._activity_icon.paused = False
+ self._activity_icon.set_paused(False)
else:
- self._activity_icon.paused = True
+ self._activity_icon.set_paused(False)
AFAICS, icon[.props].paused = True should be equivalent to
icon.set_paused(True). Could you check if it's actually the case? May
be a bug in pygobject.
class _Animation(animator.Animation):
There are other files using the same properties.
[gonz...@aronax site-packages]$ pwd
/home/gonzalo/sugar-jhbuild/install/lib/python2.6/site-packages
[gonz...@aronax site-packages]$ grep -r props.pause *
jarabe/view/launcher.py.ori: self._activity_icon.props.paused =
False
jarabe/view/launcher.py.ori: self._activity_icon.props.paused =
True
jarabe/desktop/meshbox.py: net.props.paused = True
jarabe/desktop/meshbox.py: net.props.paused = False
[gonz...@aronax site-packages]$ grep -r props.pulsing *
jarabe/view/launcher.py.ori: self._activity_icon.props.pulsing =
False
jarabe/view/launcher.py.ori: self._activity_icon.props.pulsing = True
jarabe/frame/notification.py: self._icon.props.pulsing = True
jarabe/frame/notification.py: self._icon.props.pulsing = False
jarabe/frame/activitiestray.py: self._icon.props.pulsing = True
jarabe/frame/activitiestray.py: self._icon.props.pulsing = False
jarabe/desktop/meshbox.py: self.props.pulsing = True
jarabe/desktop/meshbox.py: self.props.pulsing = False
jarabe/desktop/meshbox.py: self.props.pulsing = False
jarabe/desktop/meshbox.py: self.props.pulsing = False
jarabe/desktop/meshbox.py: self.props.pulsing = True
jarabe/desktop/meshbox.py: self.props.pulsing = False
jarabe/desktop/meshbox.py: self.props.pulsing = False
I can put the instructions to use systemtap with sugar in the wiki if
anybody think its useful.
That would be great, looks really useful.
Thanks,
Tomeu
--
Gonzalo Odiard
SugarLabs Argentina
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [ASLO] Release Pukllanapac-2
Activity Homepage: http://activities.sugarlabs.org/addon/4320 Sugar Platform: 0.82 - 0.88 Download Now: http://activities.sugarlabs.org/downloads/file/26986/pukllanapac-2.xo Release notes: * saves/restores to Journal * multiple play levels * auto-advances to next level Sugar Labs Activities http://activities.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] behaviour of F-keys on XO HS
i'd like to bring this discussion to a conclusion. i'm starting to be a fan of this proposal of bert's -- it's very simple, keeps the keys the same in sugar and in gnome, and on membrane and non-membrane keyboards, it's backwards compatible with existing use on XO-1, and the volume/ brightness keys remain easily discoverable. it does require that sugar respond to F5 and F6 for journal and frame -- i still don't have a feeling for whether that's an issue or not, and if so, how big. any yeas or nays? paul bert wrote: On 17.07.2010, at 09:31, Bernie Innocenti wrote: El Thu, 15-07-2010 a las 23:08 -0400, Paul Fox escribió: i think everyone (except apple, i'm learning tonight) agrees this is the correct setup when not in sugar. Lenovo also seems to be switching to the Apple layout: http://www.blogcdn.com/www.engadget.com/media/2010/01/thinkpadedgepost16.jpg http://www.thinkpads.com/wp-content/gallery/lenovo-thinkpad-edge-13-review/lenov o-thinkpad-edge-13-keyboard.jpg Almost all the historic F-key mappings have an alternative CTRL+key or ALT+key mapping in modern HIGs. Keys to control laptop volume and brightness are accessed much more frequently, so it's foreseeable that over time they will supplant the F-keys in PC keyboards. +1 IMHO pressing fn to get f1 to f10 makes sense. In my daily routine I much more often change volume or brightness than use the numbered F keys. Looking at this again http://wiki.laptop.org/go/OLPC_Spanish_Non-membrane_Keyboard I propose: f1-f8 produce F key codes both with and without the fn key f9-f12 produce F codes only with fn, and volume/brightness events without fn. So holding down fn always gets you the F key codes, you can change volume/brightness without modifier, and as a bonus you can use the first eight F keys even without the fn key. This mapping should work both in Sugar and outside. - Bert - ___ Devel mailing list de...@lists.laptop.org http://lists.laptop.org/listinfo/devel =- paul fox, p...@laptop.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] behaviour of F-keys on XO HS
On Mon, Jul 19, 2010 at 5:20 PM, Paul Fox p...@laptop.org wrote: i'd like to bring this discussion to a conclusion. i'm starting to be a fan of this proposal of bert's -- it's very simple, keeps the keys the same in sugar and in gnome, and on membrane and non-membrane keyboards, it's backwards compatible with existing use on XO-1, and the volume/ brightness keys remain easily discoverable. it does require that sugar respond to F5 and F6 for journal and frame -- i still don't have a feeling for whether that's an issue or not, and if so, how big. The only activity I am aware of that uses F5 and F6 on the XO is the most recent version of Paint that Gonzolo is working on. Presumably these keymaps could be grabbed by Paint when running on an OLPC XO 1.0 or when we detect the membrane keyboard. Otherwise, we could keep the mapping as Bert suggests. any yeas or nays? Yeah. paul bert wrote: On 17.07.2010, at 09:31, Bernie Innocenti wrote: El Thu, 15-07-2010 a las 23:08 -0400, Paul Fox escribió: i think everyone (except apple, i'm learning tonight) agrees this is the correct setup when not in sugar. Lenovo also seems to be switching to the Apple layout: http://www.blogcdn.com/www.engadget.com/media/2010/01/thinkpadedgepost16.jpg http://www.thinkpads.com/wp-content/gallery/lenovo-thinkpad-edge-13-review/lenov o-thinkpad-edge-13-keyboard.jpg Almost all the historic F-key mappings have an alternative CTRL+key or ALT+key mapping in modern HIGs. Keys to control laptop volume and brightness are accessed much more frequently, so it's foreseeable that over time they will supplant the F-keys in PC keyboards. +1 IMHO pressing fn to get f1 to f10 makes sense. In my daily routine I much more often change volume or brightness than use the numbered F keys. Looking at this again http://wiki.laptop.org/go/OLPC_Spanish_Non-membrane_Keyboard I propose: f1-f8 produce F key codes both with and without the fn key f9-f12 produce F codes only with fn, and volume/brightness events without fn. So holding down fn always gets you the F key codes, you can change volume/brightness without modifier, and as a bonus you can use the first eight F keys even without the fn key. This mapping should work both in Sugar and outside. - Bert - ___ Devel mailing list de...@lists.laptop.org http://lists.laptop.org/listinfo/devel =- paul fox, p...@laptop.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Sugar on a Stick Weekly Meeting Logs (2010/07/19)
Here are the minutes (follow the link at the bottom for the logs): http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100719_1506.html Bernie, what's the state of the VM we had been talking about for Mel and me (I'd really like to have a real bot there). Points raised: * Raffael asked about the state of this feature: http://wiki.sugarlabs.org/go/Features/Feature_intro_language_keyboard_options * We had a convo with Gary and others about the entry barrier for new activity developers in terms of making releases. * The feature freeze is coming close. Next week is the last chance to submit new features. We'd really like to see more feedback from activity authors interested in getting activities in SoaS. Thanks everyone for attending, --Sebastian ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] behaviour of F-keys on XO HS
Yeah How we detect what keyboard is present? Gonzalo On Mon, Jul 19, 2010 at 9:26 PM, Walter Bender walter.ben...@gmail.comwrote: On Mon, Jul 19, 2010 at 5:20 PM, Paul Fox p...@laptop.org wrote: i'd like to bring this discussion to a conclusion. i'm starting to be a fan of this proposal of bert's -- it's very simple, keeps the keys the same in sugar and in gnome, and on membrane and non-membrane keyboards, it's backwards compatible with existing use on XO-1, and the volume/ brightness keys remain easily discoverable. it does require that sugar respond to F5 and F6 for journal and frame -- i still don't have a feeling for whether that's an issue or not, and if so, how big. The only activity I am aware of that uses F5 and F6 on the XO is the most recent version of Paint that Gonzolo is working on. Presumably these keymaps could be grabbed by Paint when running on an OLPC XO 1.0 or when we detect the membrane keyboard. Otherwise, we could keep the mapping as Bert suggests. any yeas or nays? Yeah. paul bert wrote: On 17.07.2010, at 09:31, Bernie Innocenti wrote: El Thu, 15-07-2010 a las 23:08 -0400, Paul Fox escribió: i think everyone (except apple, i'm learning tonight) agrees this is the correct setup when not in sugar. Lenovo also seems to be switching to the Apple layout: http://www.blogcdn.com/www.engadget.com/media/2010/01/thinkpadedgepost16.jpg http://www.thinkpads.com/wp-content/gallery/lenovo-thinkpad-edge-13-review/lenov o-thinkpad-edge-13-keyboard.jpg Almost all the historic F-key mappings have an alternative CTRL+key or ALT+key mapping in modern HIGs. Keys to control laptop volume and brightness are accessed much more frequently, so it's foreseeable that over time they will supplant the F-keys in PC keyboards. +1 IMHO pressing fn to get f1 to f10 makes sense. In my daily routine I much more often change volume or brightness than use the numbered F keys. Looking at this again http://wiki.laptop.org/go/OLPC_Spanish_Non-membrane_Keyboard I propose: f1-f8 produce F key codes both with and without the fn key f9-f12 produce F codes only with fn, and volume/brightness events without fn. So holding down fn always gets you the F key codes, you can change volume/brightness without modifier, and as a bonus you can use the first eight F keys even without the fn key. This mapping should work both in Sugar and outside. - Bert - ___ Devel mailing list de...@lists.laptop.org http://lists.laptop.org/listinfo/devel =- paul fox, p...@laptop.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Gonzalo Odiard Responsable de Desarrollo Sistemas Australes ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] behaviour of F-keys on XO HS
On Mon, Jul 19, 2010 at 9:27 PM, Gonzalo Odiard godi...@gmail.com wrote:
Yeah
How we detect what keyboard is present?
You can possible to detect the XO 1, which guarantees a membrane
keyboard. And a non-OLPC machine, which guarantees a non-membrane
keyboard. It is the XO 1.5 that is at issue. I'll look into it.
-walter
def _get_hardware():
Determine whether we are using XO 1.0, 1.5, or unknown hardware
bus = dbus.SystemBus()
comp_obj = bus.get_object('org.freedesktop.Hal',
'/org/freedesktop/Hal/devices/computer')
dev = dbus.Interface(comp_obj, 'org.freedesktop.Hal.Device')
if dev.PropertyExists('system.hardware.vendor') and \
dev.PropertyExists('system.hardware.version'):
if dev.GetProperty('system.hardware.vendor') == 'OLPC':
if dev.GetProperty('system.hardware.version') == '1.5':
return XO15
else:
return XO1
else:
return UNKNOWN
elif path.exists('/etc/olpc-release') or \
path.exists('/sys/power/olpc-pm'):
return XO1
else:
return UNKNOWN
Gonzalo
On Mon, Jul 19, 2010 at 9:26 PM, Walter Bender walter.ben...@gmail.com
wrote:
On Mon, Jul 19, 2010 at 5:20 PM, Paul Fox p...@laptop.org wrote:
i'd like to bring this discussion to a conclusion.
i'm starting to be a fan of this proposal of bert's -- it's very
simple, keeps the keys the same in sugar and in gnome, and on
membrane and non-membrane keyboards, it's backwards compatible
with existing use on XO-1, and the volume/ brightness keys remain
easily discoverable. it does require that sugar respond to F5
and F6 for journal and frame -- i still don't have a feeling
for whether that's an issue or not, and if so, how big.
The only activity I am aware of that uses F5 and F6 on the XO is the
most recent version of Paint that Gonzolo is working on. Presumably
these keymaps could be grabbed by Paint when running on an OLPC XO 1.0
or when we detect the membrane keyboard. Otherwise, we could keep the
mapping as Bert suggests.
any yeas or nays?
Yeah.
paul
bert wrote:
On 17.07.2010, at 09:31, Bernie Innocenti wrote:
El Thu, 15-07-2010 a las 23:08 -0400, Paul Fox escribió:
i think everyone (except
apple, i'm learning tonight) agrees this is the correct setup
when not in sugar.
Lenovo also seems to be switching to the Apple layout:
http://www.blogcdn.com/www.engadget.com/media/2010/01/thinkpadedgepost16.jpg
http://www.thinkpads.com/wp-content/gallery/lenovo-thinkpad-edge-13-review/lenov
o-thinkpad-edge-13-keyboard.jpg
Almost all the historic F-key mappings have an alternative CTRL+key
or
ALT+key mapping in modern HIGs. Keys to control laptop volume and
brightness are accessed much more frequently, so it's foreseeable
that
over time they will supplant the F-keys in PC keyboards.
+1
IMHO pressing fn to get f1 to f10 makes sense. In my daily
routine I much
more often change volume or brightness than use the numbered F keys.
Looking at this again
http://wiki.laptop.org/go/OLPC_Spanish_Non-membrane_Keyboard
I propose:
f1-f8 produce F key codes both with and without the fn key
f9-f12 produce F codes only with fn, and volume/brightness
events
without fn.
So holding down fn always gets you the F key codes, you can change
volume/brightness without modifier, and as a bonus you can use the
first eight
F keys even without the fn key.
This mapping should work both in Sugar and outside.
- Bert -
___
Devel mailing list
de...@lists.laptop.org
http://lists.laptop.org/listinfo/devel
=-
paul fox, p...@laptop.org
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
--
Walter Bender
Sugar Labs
http://www.sugarlabs.org
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
--
Gonzalo Odiard
Responsable de Desarrollo
Sistemas Australes
--
Walter Bender
Sugar Labs
http://www.sugarlabs.org
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [Testing request] Browse-webkit
rgs and myself have ported Browse to pywebkitgtk with all features and we could use some testing. You can get it from here http://git.sugarlabs.org/projects/browse/repos/mainline/trees/webkit It requires pywebkitgtk 1.1.6 and webkitgtk 1.2.*. Also, note that pywebkitgtk 1.1.6 in fedora (11 and 12 have been observed so far) segfaults. So either wait for the fix or use another distro in a VM. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Read/evince quick follow up
Hi Lucian, Fab thanks. A git clone of your http://git.sugarlabs.org/git/read/evince-2-30.git now does the trick for testing in SoaS Mirabelle. Toolbars look good this time :-) I've only tested it on a couple of Gutenberg text PDFs so far, so yes as you mentioned the Edit toolbar is not so functional yet (no copy, no search). Everything else seems great so far e.g. - creating bookmarks work - page count and current page is correct - forward/back work moving one screens worth at a time (sub menus for by page and bookmarks also work) - view zoom in/out is good - view zoom to fit width is good - incremental zoom widget good - full screen view (and back again) good I'll try a wider range of test PDF's later (with more image content, some really great edu material at http://www.ck12.org if perhaps at our upper target age range). Are there any other document types that evince was supporting that I should go test? Fantastic work!! Regards, --Gary ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Pulsing icons don't stop
AFAICS, icon[.props].paused = True should be equivalent to icon.set_paused(True). Could you check if it's actually the case? May be a bug in pygobject. May be it' s a problem with my sugar-jhbuild enviroment. I will to update all and try again. I can put the instructions to use systemtap with sugar in the wiki if anybody think its useful. That would be great, looks really useful. I will. Thanks, Tomeu -- Gonzalo Odiard SugarLabs Argentina ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] behaviour of F-keys on XO HS
On Mon, 2010-07-19 at 21:33 -0400, Walter Bender wrote:
On Mon, Jul 19, 2010 at 9:27 PM, Gonzalo Odiard godi...@gmail.com wrote:
Yeah
How we detect what keyboard is present?
You can possible to detect the XO 1, which guarantees a membrane
keyboard. And a non-OLPC machine, which guarantees a non-membrane
keyboard. It is the XO 1.5 that is at issue. I'll look into it.
http://wiki.laptop.org/go/OLPC_Firmware_q3a44 mentions:
1889: OLPC keyboard driver, avoid confusing EC with enable scan command
I wonder if somehow the type of detected keyboard is discoverable
via /ofw.
Cheers,
Raúl
-walter
def _get_hardware():
Determine whether we are using XO 1.0, 1.5, or unknown hardware
bus = dbus.SystemBus()
comp_obj = bus.get_object('org.freedesktop.Hal',
'/org/freedesktop/Hal/devices/computer')
dev = dbus.Interface(comp_obj, 'org.freedesktop.Hal.Device')
if dev.PropertyExists('system.hardware.vendor') and \
dev.PropertyExists('system.hardware.version'):
if dev.GetProperty('system.hardware.vendor') == 'OLPC':
if dev.GetProperty('system.hardware.version') == '1.5':
return XO15
else:
return XO1
else:
return UNKNOWN
elif path.exists('/etc/olpc-release') or \
path.exists('/sys/power/olpc-pm'):
return XO1
else:
return UNKNOWN
Gonzalo
On Mon, Jul 19, 2010 at 9:26 PM, Walter Bender walter.ben...@gmail.com
wrote:
On Mon, Jul 19, 2010 at 5:20 PM, Paul Fox p...@laptop.org wrote:
i'd like to bring this discussion to a conclusion.
i'm starting to be a fan of this proposal of bert's -- it's very
simple, keeps the keys the same in sugar and in gnome, and on
membrane and non-membrane keyboards, it's backwards compatible
with existing use on XO-1, and the volume/ brightness keys remain
easily discoverable. it does require that sugar respond to F5
and F6 for journal and frame -- i still don't have a feeling
for whether that's an issue or not, and if so, how big.
The only activity I am aware of that uses F5 and F6 on the XO is the
most recent version of Paint that Gonzolo is working on. Presumably
these keymaps could be grabbed by Paint when running on an OLPC XO 1.0
or when we detect the membrane keyboard. Otherwise, we could keep the
mapping as Bert suggests.
any yeas or nays?
Yeah.
paul
bert wrote:
On 17.07.2010, at 09:31, Bernie Innocenti wrote:
El Thu, 15-07-2010 a las 23:08 -0400, Paul Fox escribió:
i think everyone (except
apple, i'm learning tonight) agrees this is the correct setup
when not in sugar.
Lenovo also seems to be switching to the Apple layout:
http://www.blogcdn.com/www.engadget.com/media/2010/01/thinkpadedgepost16.jpg
http://www.thinkpads.com/wp-content/gallery/lenovo-thinkpad-edge-13-review/lenov
o-thinkpad-edge-13-keyboard.jpg
Almost all the historic F-key mappings have an alternative CTRL+key
or
ALT+key mapping in modern HIGs. Keys to control laptop volume and
brightness are accessed much more frequently, so it's foreseeable
that
over time they will supplant the F-keys in PC keyboards.
+1
IMHO pressing fn to get f1 to f10 makes sense. In my daily
routine I much
more often change volume or brightness than use the numbered F keys.
Looking at this again
http://wiki.laptop.org/go/OLPC_Spanish_Non-membrane_Keyboard
I propose:
f1-f8 produce F key codes both with and without the fn key
f9-f12 produce F codes only with fn, and volume/brightness
events
without fn.
So holding down fn always gets you the F key codes, you can change
volume/brightness without modifier, and as a bonus you can use the
first eight
F keys even without the fn key.
This mapping should work both in Sugar and outside.
- Bert -
___
Devel mailing list
de...@lists.laptop.org
http://lists.laptop.org/listinfo/devel
=-
paul fox, p...@laptop.org
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
--
Walter Bender
Sugar Labs
http://www.sugarlabs.org
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
--
Gonzalo Odiard
Responsable de Desarrollo
Sistemas Australes
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] behaviour of F-keys on XO HS
On Tue, Jul 20, 2010 at 01:04:06AM -0400, Raul Gutierrez Segales wrote: On Mon, 2010-07-19 at 21:33 -0400, Walter Bender wrote: On Mon, Jul 19, 2010 at 9:27 PM, Gonzalo Odiard godi...@gmail.com wrote: Yeah How we detect what keyboard is present? http://wiki.laptop.org/go/OLPC_Firmware_q3a44 mentions: 1889: OLPC keyboard driver, avoid confusing EC with enable scan command That's unrelated, I think. I wonder if somehow the type of detected keyboard is discoverable via /ofw. The manufacturing data may help to narrow the possibilities, but they would have to be maintained correctly in conjunction with any keyboard changes by deployment repair. Perhaps someone else knows more. -- James Cameron http://quozl.linux.org.au/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
