Re: Building for x86
Some of the people in #neo1973-germany (freenode) built OpenMoko for x86, so this seems to be no problem. I guess with Xephyr you'll have OpenMoko in a X-Window on your desktop. On 10/30/07, Simon [EMAIL PROTECTED] wrote: Hi, I've been following the list a bit and I was wondering if it was possible to build openmoko for a native x86 environment? I don't just mean to build the graphical end of it, but also the kernel and everything, have my root setup the way it is on the OpenMoko device. Have only the exact same software running... What I'm looking for is to isolate completely my openmoko build from my system. My system is too old to run OM in qemu, (it took more than 30 min to boot the last time i tried and it wasn't very functional with 1 min delay for clicks). So... I'd rather dual boot into OpenMoko than integrate it into my current system... I haven't done anything yet but I believe I should follow the path of: http://wiki.openmoko.org/wiki/MokoMakefile Making sure to make the modifications explain in pages for setting up OM for Xephyr and Xoo. And then, place it all under its own partition (any partition preference? ext2?) and update my own boot loader (I've been using lilo for long now). Is there any special append=options I should use? I guess the part talking about u-boot should cover this, but if you guys can help with it... If I'm not drunk, this should work, right? Also, having everything native like this, what will happen with the X display? 1024x768 or will it resize with black borders left and right? Thanks in advance, Simon ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SRC_URI arguments, how to
Hi, - On 10/30/07, Pontus Oldberg [EMAIL PROTECTED] wrote: | Would I then have to have a script to pack my local overlay before | building the package ? \-- AFAIK, the bitbake recipe file should take care of building the package. See the simple .bb example here: http://free-opensource.qvantel.net/mediawiki/index.php/OpenMoko_Hello_World_Debian_20072#Autotools_method SK -- Shakthi Kannan http://www.shakthimaan.com ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SRC_URI arguments, how to
Thank you, Would I then have to have a script to pack my local overlay before building the package ? Sorry for my confusion, I'm all new to this build environment. How does everyone else do this ? From my point of view it would be easiest to be able to point SRC_URI to my local overlay base directory and let it copy everything below and including that point to the work directory and the build it. But i'm guessing that there is something that I am missing here =) /Pontus My code doesnt actually sit in the local overlay, only my recipes are there. I have a separate working directory where I do my work. Oh come on, creating a tarball is pretty trivial =D. The bitbake is kinda smart enough to unpack the tarball while building your code. No problems there. Especially when you have a sizeable number of files, copying each and every file is kinda weird (unless its under some Version Control System). But, if your code is in some local svn (..or cvs) repository you could make change the SRC_URI accordingly if you want the copy each file into the build directory behaviour. Digging into the gazillions of recipes in the tree should give you an idea. Bitbake experts, Correct me if i am wrong. =) Regards Sudharshan S blog: http://www.sudharsh.wordpress.com ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Building for x86
Ok, sounds like a good start... germany eh? Well, that's nice, I work on the night shift for a couple more days, i'll be in touch with them! And yes, I'll definitely try Xephyr, but that will be more to develop and tweak quickly, rather than getting the feel of it and trying it out... Thanks! Simon On Oct 30, 2007 3:58 AM, Thomas Gstädtner [EMAIL PROTECTED] wrote: Some of the people in #neo1973-germany (freenode) built OpenMoko for x86, so this seems to be no problem. I guess with Xephyr you'll have OpenMoko in a X-Window on your desktop. On 10/30/07, Simon [EMAIL PROTECTED] wrote: Hi, I've been following the list a bit and I was wondering if it was possible to build openmoko for a native x86 environment? I don't just mean to build the graphical end of it, but also the kernel and everything, have my root setup the way it is on the OpenMoko device. Have only the exact same software running... What I'm looking for is to isolate completely my openmoko build from my system. My system is too old to run OM in qemu, (it took more than 30 min to boot the last time i tried and it wasn't very functional with 1 min delay for clicks). So... I'd rather dual boot into OpenMoko than integrate it into my current system... I haven't done anything yet but I believe I should follow the path of: http://wiki.openmoko.org/wiki/MokoMakefile Making sure to make the modifications explain in pages for setting up OM for Xephyr and Xoo. And then, place it all under its own partition (any partition preference? ext2?) and update my own boot loader (I've been using lilo for long now). Is there any special append=options I should use? I guess the part talking about u-boot should cover this, but if you guys can help with it... If I'm not drunk, this should work, right? Also, having everything native like this, what will happen with the X display? 1024x768 or will it resize with black borders left and right? Thanks in advance, Simon ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Openource handwriting recognition
I believe this merits some very in deep looks: http://risujin.org/cellwriter/ (via http://www.valdyas.org/fading/index.cgi/2007/10/30#cellwriter) signature.asc Description: This is a digitally signed message part. ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Openource handwriting recognition
looks like it was developed with an active digitizer... (eg mousing over stuff the insertion hotspot) On 10/30/07, Gabriel Ambuehl [EMAIL PROTECTED] wrote: I believe this merits some very in deep looks: http://risujin.org/cellwriter/ (via http://www.valdyas.org/fading/index.cgi/2007/10/30#cellwriter) ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Openource handwriting recognition
Two separate quotes from the main website However, some Tablet PCs or PDAs may not have a pen button or any other convenient way to right-click. The alternative gesture to bring up the context menu is the hold-click. Press with the pen without moving for one second and the context menu will show up. If you start drawing ink, you have moved the pen too far. To insert a space, point the mouse cursor at the insertion hotspot at either the bottom or the top of the dividing line between cells. If you are pointing at the hotspot, arrows will appear at the top and bottom of the dividing line, click to insert a space. So yeah, they do talk about mousing over things, but they also talk about PDA/Tablets as well. Either way, this looks like a great stylus input method, but probably won't work too well for a finger input method. -Jonathon -Original Message- From: Brad Midgley [EMAIL PROTECTED] Reply-To: List for OpenMoko community discussion community@lists.openmoko.org To: List for OpenMoko community discussion community@lists.openmoko.org Subject: Re: Openource handwriting recognition Date: Tue, 30 Oct 2007 13:40:26 -0600 looks like it was developed with an active digitizer... (eg mousing over stuff the insertion hotspot) On 10/30/07, Gabriel Ambuehl [EMAIL PROTECTED] wrote: I believe this merits some very in deep looks: http://risujin.org/cellwriter/ (via http://www.valdyas.org/fading/index.cgi/2007/10/30#cellwriter) ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Openource handwriting recognition
On Oct 30, 2007 7:58 PM, Gabriel Ambuehl [EMAIL PROTECTED] wrote: I believe this merits some very in deep looks: http://risujin.org/cellwriter/ (via http://www.valdyas.org/fading/index.cgi/2007/10/30#cellwriter) It seems to work on the Neo. I have made a very quick package for it and uploaded in my feed (see http://wiki.openmoko.org/index.php?title=User:Alessandro#My_Package_Repository). ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
