Am now getting a "zero dot" hang on my XO-1.5
Upgraded os125 to kernel 2.6.31_xo1.5-20100607.1740.1.olpc.ead3d3e.i586 Now, whenever I boot, right after the line "Loading ramdisk image from /pci/s...@c/d...@1:\boot/initrd.img ..." I get the message "General Protection Exception" - and the boot hangs. The bypass is to do a complete reset (pull AC and battery for a bit), and only then try the boot -- now the boot proceeds normally. The problem is consistently repeatable. I did not have the problew when booting os125 with its original (month-old) kernel. XO-1.5 B2. Q3A39C. mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: multi-touch
On 11 Jun 2010, at 04:14, Peter Robinson wrote: > On Tue, Jun 8, 2010 at 4:05 PM, Gary Martin wrote: >> On 8 Jun 2010, at 09:53, "C. Scott Ananian" wrote: >> >>> On Tue, Jun 8, 2010 at 4:20 AM, Carlos Nazareno wrote: If possible, go for a minimum of 5 touch points capability, which is what Apple has I think. >> >> Yes, it would be good to keep in mind a likely use case where two children >> interact with one device screen (example, the various split screen piano >> apps on the iPad where two people can play face to face). >> >> Regards, >> --Gary >> >> P.S. Anyone have RDP working on an iPad with Sugar in a VirtualBox? I have >> it working OK via VNC for UI testing, but RDP would allow passing over >> audio, and allow the Sugar VM to be run headless. > > I believe itap is a very good RDP client for the ipad. Thanks Peter. Quick update, it's either itap or Desktop Connect. I've emailed both about Virtual Box support. itap folks kindly/honestly say VB is not yet properly supported, with some users reporting success but others reporting severe graphical problems — say they will officially support VB in a future release. Desktop Connect folks gave me a slightly open response of 'yes this should work fine with Desktop Connect V 2.0, please let us know if you experience any issues.' [Damn, just been out for drinks with a whole swarm of iPad/iPhone developers, I knew there was something else I should have been picking their brains over] Regards, --Gary > Peter ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: multi-touch
> > I believe itap is a very good RDP client for the ipad. > iT hasn't been pulled from the iStore yet for copyright iNfringement. I am iN shock :-) ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: multi-touch
On Tue, Jun 8, 2010 at 4:05 PM, Gary Martin wrote: > On 8 Jun 2010, at 09:53, "C. Scott Ananian" wrote: > >> On Tue, Jun 8, 2010 at 4:20 AM, Carlos Nazareno wrote: >>> If possible, go for a minimum of 5 touch points capability, which is >>> what Apple has I think. > > Yes, it would be good to keep in mind a likely use case where two children > interact with one device screen (example, the various split screen piano apps > on the iPad where two people can play face to face). > > Regards, > --Gary > > P.S. Anyone have RDP working on an iPad with Sugar in a VirtualBox? I have it > working OK via VNC for UI testing, but RDP would allow passing over audio, > and allow the Sugar VM to be run headless. I believe itap is a very good RDP client for the ipad. Peter ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Reason for the "one dot" hang found!
On 10 Jun 2010, at 20:53, Daniel Drake wrote:
> On 10 June 2010 10:58, Bernie Innocenti wrote:
>> Hello,
>>
>> with the serial cable Richard gave me, I figured out what's causing a
>> rare lockup during boot which has been riddling the XO-1 since when we
>> moved to F11.
>>
>> The /etc/rc.sysinit script contains this line:
>>
>> # Sync waiting for storage.
>> { rmmod scsi_wait_scan ; modprobe scsi_wait_scan ; rmmod scsi_wait_scan ;
>> } >/dev/null 2>&1
>>
>> It gets executed while udev is loading modules in parallel. Apparently,
>> something in the kernel ends up dead-locking on module load:
>>
>>
>> 1 tty1 Ss+0:02 /sbin/init
>> 945 ?Ss 0:00 /bin/sh -e -c ?runlevel --set S >/dev/null ||
>> true???/
>> 950 ?S 0:00 \_ /bin/bash /etc/rc.d/rc.sysinit
>> 1597 ?D 0:00 \_ modprobe scsi_wait_scan
>
> I strongly doubt this is the issue. This is a very simple module.
>
> Note your other blocked process:
>
>> 1035 ?D< 0:00 /sbin/modprobe -b
>> pci:v11ABd4102sv11ABsd00
>
> This one also has a lower process ID, suggesting that it was run first.
>
> I suspect there is a crash/hang within this module, and at this point,
> attempting to load any other module (scsi_wait_scan or otherwise) will
> hang. Due to contention on a lock, corruption, a dead kernel thread,
> or something like that.
>
> My suggested next steps in diagnosis:
> 1. Identify which device is pci:v11ABd4102
> Anyone can do this on any XO-1 with: lspci -vd 11ab:4102
> I'm pretty sure its a part of the CAFE chip but I don't have an XO to check.
00:0c.2 Multimedia video controller: Marvell Technology Group Ltd. Unknown
device 4102 (rev 10) (pro-if 01)
Subsystem: Marvell Technology Group Ltd. Unknown device 4100
Flags: bus master, 66MHz, medium, latency 32, IRQ 11
Memory at fe028000 (32-bit, non-prefetchable) [size=16K]
Capabilities:
Kernel driver in use: cafe1000-ccic
This is from an XO-1 running build 767, Sugar 0.82.1, firmware Q2E18.
Regards,
--Gary
> 2. Look at dmesg at point of crash
> Considering that you got a process tree I guess you can also run some
> other commands at point of hang?
> Run "dmesg" and capture output.
>
> 3. Capture kernel task dump at point of crash
> echo t > /proc/sysrq-trigger
> The task dump will appear in kernel logs (dmesg).
>
> Daniel
> ___
> Devel mailing list
> Devel@lists.laptop.org
> http://lists.laptop.org/listinfo/devel
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Re: multi-touch
On 8 Jun 2010, at 09:53, "C. Scott Ananian" wrote: > On Tue, Jun 8, 2010 at 4:20 AM, Carlos Nazareno wrote: >> If possible, go for a minimum of 5 touch points capability, which is >> what Apple has I think. Yes, it would be good to keep in mind a likely use case where two children interact with one device screen (example, the various split screen piano apps on the iPad where two people can play face to face). Regards, --Gary P.S. Anyone have RDP working on an iPad with Sugar in a VirtualBox? I have it working OK via VNC for UI testing, but RDP would allow passing over audio, and allow the Sugar VM to be run headless. > Apple actually supports 11 on the iPad. Palm and the iPhone support 5. > http://daringfireball.net/linked/2010/05/10/gemmell-multitouch > --scott > > -- > ( http://cscott.net/ ) > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Reason for the "one dot" hang found!
i forgot to give the link to the thread daniel refers to: http://lists.laptop.org/pipermail/devel/2008-June/thread.html#15432 i'm afraid there's not much to be drawn from there in the way of conclusions, though. paul paul wrote: > daniel wrote: > > On 10 June 2010 18:32, Bernie Innocenti wrote: > > > It's the camera controller. Hence, the other module being loaded must be > > > cafe_ccic. > > > > > > Looking at the initialization of cafe_ccic, there seems to be a > > > complicated dance of mutexes and spin locks, plus a kernel thread and a > > > bunch of sleeps. All the ingredients for a good deadlock are present :-) > > > > I doubt it is directly related to locking. > > If (as you say) there is no crash in the logs then I suspect it is > > related to an infinite loop within the initialization code. > > > > And this all seems very familiar. Google for a thread titled > > "cafe_ccic/ov7670 hang on boot" from the 8.2 days. > > I suspect we never fixed that bug upstream and that same commit needs > > to be reverted from the new kernel. > > good catch, good call. commit 8815ea29a9bcbab2a3c7fbc28987cac67c2c41d0 > is a revert for 6d77444aca298b43a88086be446f943cd0442ef7, and is present > in the testing branch (i.e., XO-1 802 and earlier), but not in our > current 2.6.31 branch. > > paul > =- > paul fox, p...@laptop.org > ___ > 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: Reason for the "one dot" hang found!
daniel wrote: > On 10 June 2010 18:32, Bernie Innocenti wrote: > > It's the camera controller. Hence, the other module being loaded must be > > cafe_ccic. > > > > Looking at the initialization of cafe_ccic, there seems to be a > > complicated dance of mutexes and spin locks, plus a kernel thread and a > > bunch of sleeps. All the ingredients for a good deadlock are present :-) > > I doubt it is directly related to locking. > If (as you say) there is no crash in the logs then I suspect it is > related to an infinite loop within the initialization code. > > And this all seems very familiar. Google for a thread titled > "cafe_ccic/ov7670 hang on boot" from the 8.2 days. > I suspect we never fixed that bug upstream and that same commit needs > to be reverted from the new kernel. good catch, good call. commit 8815ea29a9bcbab2a3c7fbc28987cac67c2c41d0 is a revert for 6d77444aca298b43a88086be446f943cd0442ef7, and is present in the testing branch (i.e., XO-1 802 and earlier), but not in our current 2.6.31 branch. paul =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
[Fwd: Record-79 is better, but not good enough]
Thanks for your amazing testing work, but please also keep sugar-devel@ posted when discussing activity bugs. I've also cc'd the current Record maintainers to attract their attention. I can confirm the 5 seconds of silence before sound starts on the XO-1.5. Sound was also quite faint. On the XO-1.5, Measure (v29) also seems to have the input levels wrong. The samples look as if they were always in overrange. - Mensaje reenviado De: Mikus Grinbergs Reply-to: mi...@bga.com Para: Devel , Fedora OLPC Asunto: Record-79 is better, but not good enough Fecha: Thu, 10 Jun 2010 14:11:46 -0500 Record-79 launches, works adequately on XO-1.5 (os125): Video - worked ok; played back ok in Record, Jukebox, Browse very first frame was dim, off-color Audio - worked ok; played back ok in Jukebox; sound level acceptable but Record and Browse played back 5 sec of silence before sound output began Photo - worked ok; played back ok in Record, Image Viewer Record-79 launched, but was sometimes unusable on F11-on-XO-1 (os15, os240py) Video - often would hang while trying to perform save sound is quite faint very first frame was dim, off-color High quality caused Record to vanish played back ok in Record, Jukebox played back thumbnail-size in Browse Audio - sound is quite faint played back in Record, Jukebox, Browse - but there was 5 sec of silence before sound output began Photo - worked ok; played back ok mikus ___ olpc mailing list o...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/olpc -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Reason for the "one dot" hang found!
On 10 June 2010 10:58, Bernie Innocenti wrote:
> Hello,
>
> with the serial cable Richard gave me, I figured out what's causing a
> rare lockup during boot which has been riddling the XO-1 since when we
> moved to F11.
>
> The /etc/rc.sysinit script contains this line:
>
> # Sync waiting for storage.
> { rmmod scsi_wait_scan ; modprobe scsi_wait_scan ; rmmod scsi_wait_scan ; }
> >/dev/null 2>&1
>
> It gets executed while udev is loading modules in parallel. Apparently,
> something in the kernel ends up dead-locking on module load:
>
>
> 1 tty1 Ss+ 0:02 /sbin/init
> 945 ? Ss 0:00 /bin/sh -e -c ?runlevel --set S >/dev/null ||
> true???/
> 950 ? S 0:00 \_ /bin/bash /etc/rc.d/rc.sysinit
> 1597 ? D 0:00 \_ modprobe scsi_wait_scan
I strongly doubt this is the issue. This is a very simple module.
Note your other blocked process:
> 1035 ? D< 0:00 /sbin/modprobe -b
> pci:v11ABd4102sv11ABsd00
This one also has a lower process ID, suggesting that it was run first.
I suspect there is a crash/hang within this module, and at this point,
attempting to load any other module (scsi_wait_scan or otherwise) will
hang. Due to contention on a lock, corruption, a dead kernel thread,
or something like that.
My suggested next steps in diagnosis:
1. Identify which device is pci:v11ABd4102
Anyone can do this on any XO-1 with: lspci -vd 11ab:4102
I'm pretty sure its a part of the CAFE chip but I don't have an XO to check.
2. Look at dmesg at point of crash
Considering that you got a process tree I guess you can also run some
other commands at point of hang?
Run "dmesg" and capture output.
3. Capture kernel task dump at point of crash
echo t > /proc/sysrq-trigger
The task dump will appear in kernel logs (dmesg).
Daniel
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Re: Reason for the "one dot" hang found!
On 10 June 2010 18:32, Bernie Innocenti wrote: > It's the camera controller. Hence, the other module being loaded must be > cafe_ccic. > > Looking at the initialization of cafe_ccic, there seems to be a > complicated dance of mutexes and spin locks, plus a kernel thread and a > bunch of sleeps. All the ingredients for a good deadlock are present :-) I doubt it is directly related to locking. If (as you say) there is no crash in the logs then I suspect it is related to an infinite loop within the initialization code. And this all seems very familiar. Google for a thread titled "cafe_ccic/ov7670 hang on boot" from the 8.2 days. I suspect we never fixed that bug upstream and that same commit needs to be reverted from the new kernel. Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Reason for the "one dot" hang found!
El Thu, 10-06-2010 a las 16:53 -0300, Daniel Drake escribió: > > 1 tty1 Ss+0:02 /sbin/init > > 945 ?Ss 0:00 /bin/sh -e -c ?runlevel --set S >/dev/null || > > true???/ > > 950 ?S 0:00 \_ /bin/bash /etc/rc.d/rc.sysinit > > 1597 ?D 0:00 \_ modprobe scsi_wait_scan > > I strongly doubt this is the issue. This is a very simple module. > > Note your other blocked process: > > > 1035 ?D< 0:00 /sbin/modprobe -b > > pci:v11ABd4102sv11ABsd00 > > This one also has a lower process ID, suggesting that it was run first. > > I suspect there is a crash/hang within this module, and at this point, > attempting to load any other module (scsi_wait_scan or otherwise) will > hang. Due to contention on a lock, corruption, a dead kernel thread, > or something like that. Ok, makes sense. If one module hangs during init, any subsequent invocation of modprobe would also hang. > My suggested next steps in diagnosis: > 1. Identify which device is pci:v11ABd4102 > Anyone can do this on any XO-1 with: lspci -vd 11ab:4102 > I'm pretty sure its a part of the CAFE chip but I don't have an XO to check. It's the camera controller. Hence, the other module being loaded must be cafe_ccic. Looking at the initialization of cafe_ccic, there seems to be a complicated dance of mutexes and spin locks, plus a kernel thread and a bunch of sleeps. All the ingredients for a good deadlock are present :-) Jonathan, can you make your best guess? > 2. Look at dmesg at point of crash > Considering that you got a process tree I guess you can also run some > other commands at point of hang? > Run "dmesg" and capture output. I did, but there was nothing interesting in dmesg, which is what I would expect from a pure locking bug. Moreover, CONFIG_DEBUG_MUTEXES is turned off. Perhaps interestingly, on regular boots, I can see some psmouse initialization messages intermixed with the cafe_ccic ones. > 3. Capture kernel task dump at point of crash > echo t > /proc/sysrq-trigger > The task dump will appear in kernel logs (dmesg). Ok, I'll do it as soon as I see it again. BTW: this bug seems to be easier to trigger by forcing a shutdown while some data is being written to disk. -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Record-79 is better, but not good enough
Record-79 launches, works adequately on XO-1.5 (os125): Video - worked ok; played back ok in Record, Jukebox, Browse very first frame was dim, off-color Audio - worked ok; played back ok in Jukebox; sound level acceptable but Record and Browse played back 5 sec of silence before sound output began Photo - worked ok; played back ok in Record, Image Viewer Record-79 launched, but was sometimes unusable on F11-on-XO-1 (os15, os240py) Video - often would hang while trying to perform save sound is quite faint very first frame was dim, off-color High quality caused Record to vanish played back ok in Record, Jukebox played back thumbnail-size in Browse Audio - sound is quite faint played back in Record, Jukebox, Browse - but there was 5 sec of silence before sound output began Photo - worked ok; played back ok mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: using libertas_tf with F11 on XO-1
Hi Martin, On Thu, Jun 10, 2010 at 21:45, Martin Langhoff wrote: > On Tue, Jun 8, 2010 at 12:18 PM, Assim Deodia > wrote: > > I am trying to load libertas_tf_usb module on XO-1 to use it as an AP. > > but when I modprobe libertas_tf_usb (after unloading libertas and usb8xxx > > Hi Assim! > > I don't think many people have been playing with it recently -- though > it is important and we'd love to see it working (and a howto, or > patches, if you come up with any). > > I can suggest some leads to follow: > > AFAIK, the libertas_tf we carry is the same as upstream, so these > instructions are relevant > http://wireless.kernel.org/en/users/Drivers/libertastf > > I have already followed these instructions as it is. They are same as on http://wiki.laptop.org/go/Libertas_Thinfirmware_HOWTO. But for some reason they does not seems to be working. atleast not at my end. You are talking about building your own kernel -- was libertas_tf not > compiled for the kernel on F11/XO-1? > libertas_tf doesn't come compile in pre-build kernels. I have rebuilt the kernel rpms with libertas_tf and libertas_tf_usb enabled. if anyone interested in testing at their own end can get the rpms from me. > > I also tried blacklisting libertas and usb8xxx but still they are loading > at > > the boot time. > > That's weird, but may be happening in the initramfs. > > If the above hints don't help, might be time to open a conversation at > linux-wireles > http://wireless.kernel.org/en/developers/MailingLists#linux-wireless_online_archives > > I will try some more hacks at my end else will mail the above list. Thanks for the pointers. > cheers, > > > m > -- > martin.langh...@gmail.com > mar...@laptop.org -- School Server Architect > - ask interesting questions > - don't get distracted with shiny stuff - working code first > - http://wiki.laptop.org/go/User:Martinlanghoff > -- Assim Deodia ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: using libertas_tf with F11 on XO-1
On Tue, Jun 8, 2010 at 12:18 PM, Assim Deodia wrote: > I am trying to load libertas_tf_usb module on XO-1 to use it as an AP. > but when I modprobe libertas_tf_usb (after unloading libertas and usb8xxx Hi Assim! I don't think many people have been playing with it recently -- though it is important and we'd love to see it working (and a howto, or patches, if you come up with any). I can suggest some leads to follow: AFAIK, the libertas_tf we carry is the same as upstream, so these instructions are relevant http://wireless.kernel.org/en/users/Drivers/libertastf You are talking about building your own kernel -- was libertas_tf not compiled for the kernel on F11/XO-1? > I also tried blacklisting libertas and usb8xxx but still they are loading at > the boot time. That's weird, but may be happening in the initramfs. If the above hints don't help, might be time to open a conversation at linux-wireles http://wireless.kernel.org/en/developers/MailingLists#linux-wireless_online_archives cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - 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
Re: Reason for the "one dot" hang found!
Laura an I are travelling accross the Interoceanic road equipped only with
our
2 XO-1s loaded with your most excellent os240py image.
This bug is most definitively the most annoying and I am so happy you seem
to have found a workaround. I´ll probably try to comment out the line
in rc.sysinit today and test it.
Thanks for the information!
We´ll report as we are preparing "Misky Pachamama" (Sweet Earth) Sugar
Camp event in Puno, high in the Andes, in front of the Titicaca Lake.
We plan to have a workshop with developers, teachers, and also a translation
sprint for Aymara and Quechua languages.
Cheers!
BTW: Alt-Tab and some other shortcuts, are annoyance nº2 for me.
We´ll continue to test and share this image with the community here.
Sebastian
2010/6/10 Bernie Innocenti
> Hello,
>
> with the serial cable Richard gave me, I figured out what's causing a
> rare lockup during boot which has been riddling the XO-1 since when we
> moved to F11.
>
> The /etc/rc.sysinit script contains this line:
>
> # Sync waiting for storage.
> { rmmod scsi_wait_scan ; modprobe scsi_wait_scan ; rmmod scsi_wait_scan ;
> } >/dev/null 2>&1
>
> It gets executed while udev is loading modules in parallel. Apparently,
> something in the kernel ends up dead-locking on module load:
>
>
> 1 tty1 Ss+0:02 /sbin/init
> 945 ?Ss 0:00 /bin/sh -e -c ?runlevel --set S >/dev/null ||
> true???/
> 950 ?S 0:00 \_ /bin/bash /etc/rc.d/rc.sysinit
> 1597 ?D 0:00 \_ modprobe scsi_wait_scan
> 946 ttyS0Rs 0:00 /bin/bash --
> 1712 ttyS0R+ 0:00 \_ ps afx
> 1010 ?S 1035 ?D< 0:00 /sbin/modprobe -b
> pci:v11ABd4102sv11ABsd00
>
>
> So it's definitely a kernel bug. Would someone like to dig into the init
> function of scsi_wait_scan to find out the root cause?
>
> Since the XO-1 is in long-term maintenance at this point, to save time
> we could opt instead for a quick & dirty solution such as commenting out
> the modprobe line in rc.sysinit. As far as I can tell, it's not needed
> on the XO.
>
> --
> // Bernie Innocenti - http://codewiz.org/
> \X/ Sugar Labs - http://sugarlabs.org/
>
> ___
> Devel mailing list
> Devel@lists.laptop.org
> http://lists.laptop.org/listinfo/devel
>
--
Sebastian Silva
http://somosazucar.org/
"Te imaginas si te pudieran enseñar sólo a leer pero no a escribir??"
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Reason for the "one dot" hang found!
Hello,
with the serial cable Richard gave me, I figured out what's causing a
rare lockup during boot which has been riddling the XO-1 since when we
moved to F11.
The /etc/rc.sysinit script contains this line:
# Sync waiting for storage.
{ rmmod scsi_wait_scan ; modprobe scsi_wait_scan ; rmmod scsi_wait_scan ; }
>/dev/null 2>&1
It gets executed while udev is loading modules in parallel. Apparently,
something in the kernel ends up dead-locking on module load:
1 tty1 Ss+0:02 /sbin/init
945 ?Ss 0:00 /bin/sh -e -c ?runlevel --set S >/dev/null || true???/
950 ?S 0:00 \_ /bin/bash /etc/rc.d/rc.sysinit
1597 ?D 0:00 \_ modprobe scsi_wait_scan
946 ttyS0Rs 0:00 /bin/bash --
1712 ttyS0R+ 0:00 \_ ps afx
1010 ?Shttp://codewiz.org/
\X/ Sugar Labs - http://sugarlabs.org/
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] Multitouch in Fedora
On Thu, Jun 10, 2010 at 09:13:49AM +0200, Tomeu Vizoso wrote: > I guess they are talking about something related to Unity, which is > Canonical's UX of choice for netbooks. Unity was supposed at the UDS > to sit in a similar place to GNOME Shell so it will most probably be > using multi touch with Gtk+. > > If anybody has more details in how this impacts OLPC and Sugar, it > would be great if they could share. Perhaps trivial, but Ubuntu jobs have been in my RSS feeds for a year or two, and there's been a row of ARM related positions. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] Multitouch in Fedora
On Wed, Jun 9, 2010 at 22:18, Peter Robinson wrote: > Hi, > > I know people were wondering about multitouch. In the last couple of > days there's a couple of posts regarding Multitouch in fedora for > those that are interested. > > http://www.j5live.com/2010/06/09/multitouch-working-in-fedora/ > > http://blogs.gnome.org/carlosg/2010/06/09/getting-multitouch-to-just-work/ I asked around yesterday and as far as I could see nobody were planning any specific work on (multi-)touch with Gtk+. As the companies doing Linux products with that capability had gone with Qt. But just now have come across this news: http://infoworld.com/d/mobilize/canonical-developing-ubuntu-os-tablets-778 I guess they are talking about something related to Unity, which is Canonical's UX of choice for netbooks. Unity was supposed at the UDS to sit in a similar place to GNOME Shell so it will most probably be using multi touch with Gtk+. If anybody has more details in how this impacts OLPC and Sugar, it would be great if they could share. Regards, Tomeu ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
