Re: orrery crashing X
Thanks for applying that, I thought the orrery maintainer would have applied it by now upstream too. When I sent him the patch, he was planning to get a build out that weekend. All of the current orrery development is happening on maemo for n900. I never heard whether is faster to draw each point direct to display, or to draw to a buffer and display the buffer. If my change is slower, and you have fixed the stack corruption when lots of events are sent to the glamo, then you may not want my patch. Ben On 11/15/2010 04:15 PM, Martin Jansa wrote: > On Thu, Sep 02, 2010 at 08:25:34PM -0400, Benjamin Deering wrote: > >> Hello All, >> >> I've missed having orrery this summer. Today I took a look at why it >> was causing X to crash. The crash happens when the program calls >> gdk_draw_point for every star it displays. I changed my copy to draw >> all of the stars into a GdkPixbuf, then I copy the GdkPixbuf onto the >> drawable area. >> >> Maybe someone knows why lots of gdk_draw_points would crash X. >> >> I think using the GdkPixbuf is faster anyways, so I'll try to add this >> to the bug posted on the orrery project page. >> >> Ben >> > Xorg crash fixed > http://git.openembedded.org/cgit.cgi/openembedded/commit/?id=a02d3d0eefe03576c33294b4201fdbe6bde21cde > > I'll apply your orrery patch too, but pitty that upstream didn't apply it > (afaik). > > Regards, > ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: orrery crashing X
On Thu, Sep 02, 2010 at 08:25:34PM -0400, Benjamin Deering wrote: > Hello All, > > I've missed having orrery this summer. Today I took a look at why it > was causing X to crash. The crash happens when the program calls > gdk_draw_point for every star it displays. I changed my copy to draw > all of the stars into a GdkPixbuf, then I copy the GdkPixbuf onto the > drawable area. > > Maybe someone knows why lots of gdk_draw_points would crash X. > > I think using the GdkPixbuf is faster anyways, so I'll try to add this > to the bug posted on the orrery project page. > > Ben Xorg crash fixed http://git.openembedded.org/cgit.cgi/openembedded/commit/?id=a02d3d0eefe03576c33294b4201fdbe6bde21cde I'll apply your orrery patch too, but pitty that upstream didn't apply it (afaik). Regards, -- Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [GTA04] When is the next and more powerful openmoko releasing
About the case. Would GeeksphoneONE/Zeus case fit us? I know they have a sliding keyboards but maybe we can work something out. Even better, I would love to see a full keyboard on my Neo. On Sun, Nov 14, 2010 at 4:00 PM, W. B. Kranendonk wrote: > > > --- On Sat, 11/13/10, Dr. H. Nikolaus Schaller wrote: > > (one series of problems) > > > > We could solve that by adding a jump start resistor. > > > > Then, we soldered the OMAP3530 and Pop Memory chip and > > connected RS232: > > > > http://download.goldelico.com/gta04/images/DSC00679.jpg > > > > It did identify itself as "40W" on the RS232 (...) must fit into 64k SRAM > built into > > the OMAP > > chip. So we are back to C64 times :) > > > > With this tool, we could identify that the (external) SDRAM > > (...) quite a long lead time. For the series version this will be > > very easy to fix. > > > Un-be-lievable! Your updates read as detectives, I am looking forward to > seeing the plot revolving and coming to a good end :-) > > Thanks again! > > Boudewijn > > > > > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community > -- - Atilla Filiz Eindhoven University of Technology Embedded Systems, Master's Programme ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
