**** BEGIN LOGGING AT Sat Sep 06 02:59:57 2008 Sep 06 08:58:25 freesmartphone.org: 03wessel 07fso-gpsd * ra79873ad595d 10/ (ChangeLog configure.ac): Prepared for release 0.5 Sep 06 10:17:34 shr is looking good :) Sep 06 10:17:51 the image built fine, and I have it loaded on the phone and already working better Sep 06 10:17:55 than 2007.2 or ASU Sep 06 10:17:57 thanks :) Sep 06 10:37:19 mattbnz: sweet Sep 06 10:37:28 what apps are working? Sep 06 10:38:17 maybe somebody in here can answer my question: I have a question about openembedded: why does building qtopia-phone-x11 need some libs (like "libXext") from the host when linking the app? Sep 06 10:41:29 good question - the libs for the executables that end up in the image should all come from staging Sep 06 10:41:41 however, it is possible that some of the host tools that are built require host libraries Sep 06 10:42:56 rwhitby: That's what I thought. All the executables that are deployed should be linking against the crosscompiled libs from OE imho... Sep 06 10:43:08 agreed Sep 06 10:43:16 of course there could be bugs in the build process Sep 06 10:43:33 rwhitby: I doubt that qtopia-phone-x11 is building host tools. Sep 06 10:44:10 it builds a complete toolchain first, and many host tools, before starting the first target executable Sep 06 10:46:05 rwhitby: oh ok. So it could be perfectly valid. Sep 06 10:46:48 if it's happening in the first thousand or so tasks, then it's completely normal Sep 06 10:50:32 rwhitby: it happebend specifically in the "qtopia-phone-x11" package which is 4680-ish Sep 06 10:50:37 happened Sep 06 10:55:57 Hey Sep 06 11:02:29 AndreasD_, here? Sep 06 11:18:02 anyone know if Linux has something similar to FreeBSD's ggate? http://kerneltrap.org/node/3104 Sep 06 11:18:30 would be interesting as a way of providing a 'virtual' usb mass storage device, that interfaces with the real filesystem somehow Sep 06 11:21:30 better ask in a linux channel Sep 06 11:21:48 cb22: just use nfs? Sep 06 11:22:36 cb22: you want filesystem driver in userspace? try fuse Sep 06 11:23:38 not quite Sep 06 11:23:53 Brinky, fuse provides userspace filesystems Sep 06 11:24:00 this is more like a userspace block device Sep 06 11:24:44 cb22: network block device can do it to some extend Sep 06 12:57:21 rwhitby: tangogps is all I've really used so far Sep 06 12:57:40 but just the general loader, navigation and speed Sep 06 12:57:50 is much improved over my experience with the original images Sep 06 12:57:56 mattbnz: that's all FSO Sep 06 12:58:20 what have you used of the SHR overlay over FSO? Sep 06 12:58:21 i've only had the phone for 3 days, so I'm still getting up to speed on all the bits and how the fit together :) Sep 06 12:58:38 ok, did you build the fso-*-image or shr-*-image ? Sep 06 12:58:44 shr-*-image Sep 06 12:58:54 testing or unstable? Sep 06 12:59:00 openmoko-shr-image-glibc-ipk--20080905-om-gta02.rootfs.jffs2 Sep 06 12:59:17 uImage-2.6.24+r5+gitr88bf43840b9df0eb0a077a1394eb564be80a412e-r5-om-gta02.bin Sep 06 12:59:23 is what I flashed onto the phone Sep 06 12:59:25 shr-unstable Sep 06 13:00:35 Do you have *-autorev lines active or inactive in your local.conf? Sep 06 13:01:29 http://home.mattb.net.nz/moko/local.conf Sep 06 13:01:33 so, no Sep 06 13:01:35 should I? Sep 06 13:27:28 ok, tangogps might be about the only app that works reliably Sep 06 13:30:33 Did anbody here (currently) ever boot the GTA from RAM using the debug board and completely bypassing the bootloader? Well, I'm currently trying to do so, writing a HOWTO along. rootfs must be mounted by NFS, since I've not figured out a scheme to determine the mtd partitions yet (either reading it from the u-boot environment using JTAG flash access, or doing it when the kernel is running by RAW mtd read access). But Sep 06 13:30:33 it doesn't bother me, since I want a NFS boot primarily. Sep 06 13:31:07 Oh, I prefectly know, that one can RAM boot by dfu-util. Sep 06 13:47:26 Hi all, can somebody help me with MokoMakefile ?? I've made some changes in $OMDIR/OpenMoko/env/openmoko/trunk/src/target/.. and created patch using quilt but after I run "make openmoko-qtopia-x11-image" the changes which I've made does not appear in generated image. How to make them appear in generated image ?? Sep 06 13:48:49 small typo should be $OMDIR/openmoko/trunk/src/target/.. Sep 06 13:50:14 but anyway does anyone know the answer Sep 06 13:50:16 ?? Sep 06 13:54:29 lmandev: depends on the package being built. Most of them download from the svn repo directly, and don't use what's in $OMDIR/openmoko/trunk/src/target/... Sep 06 14:47:02 hi all... can I get some help for building kernel modules with the MokoMakefile. couldn't find anything on the wiki Sep 06 14:49:06 hil__: be more specific, whats the problem? Sep 06 14:49:48 i'm trying to build a kernel module using the Mokomakefile. can't find anything on the wiki for the procedure Sep 06 14:50:15 there are no details. I have created the openmoko-devel-image Sep 06 14:50:34 there is no specific procedure, its a package as anything else also Sep 06 14:51:09 oh. so the build environment will take care of the rest. I just use the same quilt procedures as normal packages Sep 06 14:51:24 thanks, i guess... I'll try it Sep 06 14:51:33 exact. use linux-openmoko or linux-openmoko-devel Sep 06 14:51:59 er.... linux-openmoko? is that a make target or an irc channel? :$ Sep 06 14:52:08 if you want to change the config go to openembedded/packages/linux/linux-openmoko and use defconf Sep 06 14:52:19 neither nor Sep 06 14:52:22 its a bb Sep 06 14:52:25 ok. got it. Sep 06 14:52:29 ;) Sep 06 14:52:46 i'm not very comfortable with bb files but i guess I'll have to learn :) Sep 06 14:52:49 ah, not defconfig, its defconfig-oe Sep 06 14:52:59 hil__: they help alot :D Sep 06 14:53:30 yeah. I know. the overhead in learning is huge and the learning curve is very steep but I guess it pays off Sep 06 14:53:53 thanks for the help emdete :) Sep 06 14:53:59 it's by far not as complicated as it seems Sep 06 15:12:38 freesmartphone.org: 03mickey 07zhone * r19580728aba0 10/src/zhone: Sep 06 15:12:38 freesmartphone.org: fix logic error in startup procedure: Sep 06 15:12:38 freesmartphone.org: antenna power needs to be turned on _before_ sending the PIN, otherwise it's going to be resetted lateron Sep 06 15:18:42 freesmartphone.org: 03stefan 07artwork * rb24d3c2e66fe 10/illume/illume/ (24 files): illume-fso-theme: Rotating asterisk images were out of sync. Update the missing one. Sep 06 15:20:58 freesmartphone.org: 03mickey 07framework * rd5712c35135b 10/framework/subsystems/ogsmd/modems/abstract/channel.py: Sep 06 15:20:58 freesmartphone.org: ogsmd: try to circumvent race condition for sending SIM init commands Sep 06 15:20:58 freesmartphone.org: Needs testing on other modems Sep 06 15:24:56 so, uh, is milestone 3 coming out today? (if not, any idea when, so i can make the wiki look less foolish?) Sep 06 15:36:06 freesmartphone.org: 03mickey 07zhone * rc27fc2efede1 10/src/zhone: show GSM agent state on display Sep 06 15:36:52 we're working hard on it Sep 06 15:37:04 we want to iron out some showstoppers before releasing it Sep 06 15:37:16 i hope to get it done within the next 48h Sep 06 15:37:19 s/i/we/ Sep 06 15:40:34 cool, thanks mickeyl Sep 06 17:42:54 is http://shr.bearstech.com/Makefile Sep 06 17:43:03 derived from the MokoMakefile ? Sep 06 17:43:22 * mattbnz is trying to learn how the build environment is setup Sep 06 18:35:13 alphaone, here? Sep 06 19:28:21 * hexarith wonders which MACH_TYPE is supplied to the kernel by U-Boot... Sep 06 21:47:00 In objdump -d u-boot/board/neo1973/gta02/lowlevel_foo > lowlevel_foo.S, the assembly looks like the entry point is 0x33f80000, which is the start of the SDRAM bank 7. The wiki is a bit vague about how the initialisation sequence it. With the steppingstone I'd have expected the reset vector code of u-boot being at 0x00000000. And if using JTAG I can see, that after a reset %pc = 0x00000000. So at some point we're gett Sep 06 21:47:00 ing to 0x33f80000, but I can't figure where.... Sep 07 02:17:37 Hello all Sep 07 02:18:15 I'm working on a doom port for the freerunner.. looking for a quick hand on a problem that i've run into. Sep 07 02:18:22 Anyone available for a few minutes? Sep 07 02:19:02 Does this qualify for this channel? If not, I can take it somewhere else? Sep 07 02:22:02 this would be the right channel. i, unfortunately, can't help with your issue right now though. Sep 07 02:22:07 have you posted on the ML? Sep 07 02:22:32 Yep. sure have.. Sep 07 02:22:40 k Sep 07 02:22:46 Just seeing if there were some live people :) Thanks! Sep 07 02:22:54 hehe, yup. Sep 07 02:22:57 no prob. Sep 07 02:23:19 you're more likely to get help if you just ask the question(s) you have rather than asking for help. Sep 07 02:23:33 Thanks.. Will Do. Sep 07 02:23:39 no prob Sep 07 02:24:38 scarlson_: read above again and start with asking questions -__- Sep 07 02:26:00 I've taken a couple of SDL based Doom ports, and have successfully ran om-conf, and have been picking off compile errors (also so far so good). I am VERY new to the OM project. And this one has me stumped. Sep 07 02:27:07 Sep 07 02:27:42 "make[2]: *** [lsdldoom] Error 1 Sep 07 02:27:44 "make[2]: Leaving directory `/home/scott/sources/lxdoom-1.4.1/src' Sep 07 02:27:46 "make[1]: *** [all-recursive] Error 1 Sep 07 02:27:48 "make[1]: Leaving directory `/home/scott/sources/lxdoom-1.4.1' Sep 07 02:27:49 "make: *** [all] Error 2 Sep 07 02:28:03 scarlson_: You're the guy with the SDL compatibility issue? Sep 07 02:28:12 Yes sir. Sep 07 02:28:48 Where does the libSDL.so come from? Sep 07 02:28:50 Running Ubuntu 8.04 .. followed the directions to install the toolchain, and it does not like my libsdl Sep 07 02:28:54 scarlson_: that wasnt error Sep 07 02:29:11 that was just after error quit messages Sep 07 02:29:17 from the ubuntu repo (I have a feeling i should be compiling libsdl also for the freerunner??) Sep 07 02:30:03 sorry. irc client trunced the pasted error Sep 07 02:30:07 Sep 07 02:30:18 and use pastebin Sep 07 02:30:46 "/usr/local/openmoko/arm/lib/gcc/arm-angstrom-linux-gnueabi/4.1.2/../../../../arm-angstrom-linux-gnueabi/bin/ld: cannot find -lSDL Sep 07 02:30:47 with preferably paste from gcc with parameters line to the end Sep 07 02:30:57 okay.. Sep 07 02:31:25 scarlson_: Are you sure the libSDL.so is for armv4t, not x86? Sep 07 02:31:29 try -lSDL-1.2 Sep 07 02:31:32 A "file libSDL.so" should tell Sep 07 02:31:37 it is for the x86.. I Sep 07 02:31:42 scarlson_: try -lSDL-1.2 Sep 07 02:32:09 torindel: as in make -1SDL-1.2 ? Sep 07 02:32:19 scarlson_: Uh... it *is* x86? Sep 07 02:32:39 edit Makefile to use -lSDL-1.2 instead of -lSDL Sep 07 02:32:52 * torindel libSDL-1.2.so.0.7.2: ELF 32-bit LSB shared object, ARM, version 1 (SYSV), dynamically linked, stripped Sep 07 02:33:07 Is libsdl included in the OM toolchain? Sep 07 02:33:11 dunno what idiot made name with -1.2 Sep 07 02:33:17 Okay.. I'm on it. Sep 07 02:36:30 SDL_LIBS = -L/usr/lib -lSDL-1.2 Sep 07 02:36:53 should it still be pointing to /usr/lib? or should it be in the angstrom tree? Sep 07 02:38:06 leave /usr/lib and add -L angstrom path (linker wont use libs for wrong platform anyways) Sep 07 02:38:55 (but OE should add correct -L for you) Sep 07 02:39:22 OM-Conf should? Sep 07 02:40:22 torindel: apparently the -1.2 is debian conventions Sep 07 02:40:45 (so you can have multiple different versions of libraries installed at the same time) Sep 07 02:41:17 hmm. Would it be best to just apt-get remove libsdl/ Sep 07 02:42:33 rwhitby: but there should be libSDL.so also, pointing to correct library and apps that dont care about version should link against libSDL.so (easy system upgradebility) and just apps that require exact version should link against things with bonus numbers -__-; Sep 07 02:42:42 or else you got fix a lot of packages Sep 07 02:43:39 torindel: argue that point with Debian, not me. Sep 07 02:43:45 ;] Sep 07 02:43:51 they choose to make each app link against a specific version Sep 07 02:44:05 (so things can't break just because you install a new version of a library I presume) Sep 07 02:44:34 Once i've editted the Makefile, do I run something before make? Ive ran make and it is stilling looking for -lSDL (even though i've changed it in makefile) Sep 07 02:44:50 Yeah that makes sense.. Sep 07 02:46:16 I'm in new territory here with linux compiling... (Excuse for basic compile question) If I run make after I've changed the Makefile, does it read that file or is there a cache that it reads from? Sep 07 02:46:39 scarlson_: just make symlink libSDL.so that points to that \ Sep 07 02:46:45 number things Sep 07 02:46:53 if you cant get it right Sep 07 02:46:56 you might want to make clean assuming the makefile has a clean target Sep 07 02:47:31 scarlson_: probably some configure is recreating that Makefile you changed Sep 07 02:50:29 ah Sep 07 02:50:58 there isn't a libsdl.so file in the angstrom lib Sep 07 02:51:23 Maybe that explains why it can't find it :) Sep 07 02:52:38 scarlson_: a) unix is case sensitive libsdl.so != libSDL.so b) angstrom builds libSDL-1.2.so not libSDL.so Sep 07 02:55:01 /usr/local/openmoko/arm/arm-angstrom-linux-gnueabi/lib/ Sep 07 02:55:15 Its not in there.. Am I looking in the right spot? **** ENDING LOGGING AT Sun Sep 07 02:59:57 2008