**** BEGIN LOGGING AT Fri Feb 19 02:59:57 2010 Feb 19 05:59:15 The online builder can't create any packages for tosa as far as I can tell (stable or unstable), could someone look into that? Feb 19 20:24:56 howdy ... anyone here compile any voip pkgs for the 5600? Feb 19 20:25:21 sry.. the zaurus sl-5600 Feb 19 20:36:17 kaz00: I unfortunately haven't, I've been trying to get collie to work in the first place Feb 19 20:36:22 Ooops, I misread that Feb 19 20:36:35 I thought you were talking about the 5500/5000 Feb 19 20:37:09 james: do you think there would be much diff between 55/5600 in terms of taking source and getting an ipkg bit baked? Feb 19 20:37:29 What do you need? Feb 19 20:37:33 or rather... bit baking an ipkg Feb 19 20:38:06 there are some linux sip packages that i would like to install Feb 19 20:38:18 see if i can do voip on opie platform Feb 19 20:38:35 It should be relatively simple. Feb 19 20:38:50 that's what i was hoping to hear :) Feb 19 20:39:32 thanks Feb 19 20:40:02 Getting OE setup was the hard part for me. (Well, that and not having tosa (SL-6000) or colie (SL-5500) supported, so I'm trying to get those working. Which required me to try out the dev branch.) Feb 19 20:42:19 http://www.angstrom-distribution.org/building-angstrom Should get you started (If you want dev, checkout a different git branch, where it says 'git checkout origin/stable/2009 -b stable/2009') Feb 19 20:42:30 Also, make sure you have plenty of free disk. Feb 19 20:53:41 kaz00: That make sense? Feb 19 20:55:16 yes. i am just reading through building angstrom right now Feb 19 20:55:32 i have 30+G free, that should be enough? Feb 19 20:56:11 which branch do you recc for basic (but complete) cross compiling? Feb 19 20:56:24 1.8.18? Feb 19 20:56:42 will peek. thanks Feb 19 20:56:49 I've got bitbake-1.8.18 installed Feb 19 20:57:39 did you do that via the wget link for tarball or via git? likely doesnt matter but want to avoid any obvious issues from the outset Feb 19 20:58:07 If on (k)ubuntu, just follow the instructions on here: http://wiki.openembedded.org/index.php/OEandYourDistro though, I had (because of using the dev branch) to upgrade bitbake Feb 19 20:58:18 For that, I grabbed the tarball, and rebuilt it as a deb. Feb 19 20:59:02 great thanks! Feb 19 20:59:24 Which distro are you on? Feb 19 21:04:30 karmic Feb 19 21:04:33 9.10 Feb 19 21:05:03 am reading the deb info right now and installing the reccomended pkgs Feb 19 21:05:25 *mandatory pkgs Feb 19 21:06:53 did you install the deb pkg for bb, or install the tarball? Feb 19 21:07:07 nvm you already answered Feb 19 21:09:05 i see there is the Psyco Python JIT compiler to speed up BitBake. Psyco works on 32-bit x86 platforms only Feb 19 21:09:18 any known amd64 optimizations avail ? Feb 19 21:48:33 james_l: ping Feb 19 22:06:25 ant_home: here Feb 19 22:06:44 hi there Feb 19 22:07:03 so, does tosa build without special patches? Feb 19 22:07:23 I mean, apart that one? Feb 19 22:09:20 It builds on 2.6.29 and 2.6.32+33rc8. 2.6.29 boots and is somewhat usable but usb fails (so no wireless) as does CF wireless cards. I tried out 2.6.33-rc8 to see if the usb issues were fixed. After that fix, 2.6.33-rc8 builds now, but fails to show on the screen. (Or if it does, at minimum the backlight is off.) Feb 19 22:10:26 ok, but thi should be enough for a minimal kexecboot kernel Feb 19 22:12:46 Oh, that is working Feb 19 22:12:53 Sorry if I didn't mention it. Feb 19 22:13:45 on 2.6.29 both opie and x11/gpe get to working somewhat. Opie has few issues on tosa (minus the usb + networking) Feb 19 22:14:21 gpe has the same issues but has the additional problem of the keys on the the slider (I think those are the gpio keys) fail to work. Feb 19 22:15:55 That's pretty much where it's at, the usb is a kernel issue (and fails on usb-storage as well, and I can't get it to load the bluetooth module for my usb bluetooth to see if that messes up.) the networking may well be a configuration issue, and the key issue is a config issue with x11/gpe. Feb 19 22:16:16 Other than that it seems to be working. (Though if those get working, something else will probably come to my notice.) Feb 19 22:17:07 kaz00: in answer to your question, I did it that way because it was simplest for me, and because I didn't notice anything about it. Feb 19 22:20:38 james: ty. i asked only to avoid any compile issues downstream. if it works, i am glad to know. Feb 19 22:21:09 the wiki had the envt var config too so easy Feb 19 22:21:10 It seems to, but as I just listed all the issues I'm having, beware. ;) Feb 19 22:21:24 :D Feb 19 22:21:28 Though, you've got a supported platform. Feb 19 22:21:39 karmic you mean? Feb 19 22:21:42 * james_l just has multiple collies and a tosa. Feb 19 22:21:49 No, target platform. Feb 19 22:21:50 oh Feb 19 22:21:54 yes Feb 19 22:22:27 i just got wpa working on the wifi... which was fairly straight fwd but still have a few projects ahead of me Feb 19 22:22:45 like clearing out / to make room for konqueror Feb 19 22:22:52 and the sip pkg would be fantastic Feb 19 22:23:52 5600 has only 32M Feb 19 22:24:01 You using kexecboot? Feb 19 22:24:19 no... that may be the solution it seems Feb 19 22:24:51 i tried once log ago and it choked. i need to take a look at it again Feb 19 22:25:07 so theres still plenty to do :D Feb 19 22:28:00 ant_home: On collie, I've kexecboot working (via hacking at it from stable, thanks to the bugreport and switching to dev it builds fine, but I haven't reflashed it), and I have one (from stable) console-image which is somewhat useful. Collie TS doesn't work, but unless I'm misremembering, I think everything else does. (cf wifi, sd, buttons, I think suspend) Feb 19 22:28:14 kexecboot on collie has the issue of never suspending though. Feb 19 22:29:20 james: kexecboot is the altboot image? Feb 19 22:29:46 e.g. http://www.angstrom-distribution.org/unstable/images/collie/Angstrom-altboot-console-image-glibc-ipk-2007.12-r9-collie-installkit.tgz ? Feb 19 22:30:03 It's not alt-boot, but very close in idea. Feb 19 22:33:17 james: which version of kexec are you using? Feb 19 22:33:18 james_l: in 2.6.33-rc8 there are still some outstanding power man issues for clamshells Feb 19 22:34:16 There appear to be for tosa as well. (or at least in the lcd driver, as I'm suspecting something changed) Feb 19 22:34:45 kaz00: I think for collie 2.6.26 is the latest Feb 19 22:35:02 kaz00 is on poodle Feb 19 22:35:17 At least you should be 5600, right? Feb 19 22:35:28 yes Feb 19 22:35:43 james_l: yes, legacy touchscreen and keyboard drivers were deprecated, at least for corgi+spitz Feb 19 22:35:55 now usng matrix keyboard Feb 19 22:36:24 and ads7846 ts Feb 19 22:37:08 kaz00: very interesting, we have not enough poodles Feb 19 22:37:16 can you recommend a howto site for kexec? Feb 19 22:37:27 I can build a test 2.6.33 just to see if it boots Feb 19 22:37:37 i downloaded tarball from http://projects.linuxtogo.org/frs/?group_id=50&release_id=132 Feb 19 22:37:59 yes, it's the latest Feb 19 22:38:11 but you need a kernel around it Feb 19 22:38:47 Interesting, absolutely no differences in tosa_bl.c in 2.6.29 and 2.6.32 Feb 19 22:38:49 linux-kexecboot for poodle is stuck at 2.6.26 Feb 19 22:38:58 I mean, never properly tested Feb 19 22:39:03 2.6.24 is working Feb 19 22:39:57 cool. the opie install i have now is 2.6.24 Feb 19 22:40:40 how to install kexecboot? do i bitbake a custom image with it included? Feb 19 22:41:44 or like ant said, i place it in an existing kernel config? Feb 19 22:42:05 sry this is new to me... if you can recommend a site for ref i can read that Feb 19 22:42:11 james_l: http://lists.infradead.org/pipermail/linux-arm-kernel/2010-February/009349.html Feb 19 22:43:08 http://lists.infradead.org/pipermail/linux-arm-kernel/2010-February/009350.html Feb 19 22:43:50 kaz00: atm you build linux-kexecboot by bitbaking any image Feb 19 22:44:20 ant: bitbake builds kexecboot in automatically? Feb 19 22:44:39 I'll try to add some default defconfigs for 2.6.3x for tosa and poodle, based on the clamshell's ones Feb 19 22:44:39 or i use the zaurus header i downloaded? Feb 19 22:45:02 just bitbake console-image Feb 19 22:45:49 ok thanks! :D Feb 19 22:45:51 it calls zaurus-installer (which depends on linux-kexecboot and updater.sh) Feb 19 22:46:05 It should (if it's like mine: tosa) it'll be in installkit Feb 19 22:47:05 james_l: check the tosa specific bits here pls : http://cgit.openembedded.org/cgit.cgi/openembedded/tree/conf/machine/include/zaurus-2.6.inc Feb 19 22:47:24 MACHINE_FEATURES_append_tosa = " usbhost wifi " Feb 19 22:47:33 MACHINE_EXTRA_RRECOMMENDS_tosa = "apm-tosa-suspendfix" Feb 19 22:48:58 the first line should take care of the modules you see failing Feb 19 22:49:13 the second one is hopefully obsoleted by now... Feb 19 22:52:35 Gah, plasma-desktop still is annoying. Feb 19 22:52:42 Thank goodness for ssh Feb 19 22:54:50 What exactly should I be checking? Feb 19 23:04:45 do the modules have been renamed? Feb 19 23:05:18 why not building it in kernel? Feb 19 23:05:42 size is not an issue Feb 19 23:07:41 question on bitbake config: site says to edit build/config/local.conf and set DISTRO = "angstrom-2008.1" MACHINE = "om-gta01" Feb 19 23:07:52 is that distro info still accurate? Feb 19 23:17:00 for poodle you have to set it "poodle" Feb 19 23:19:22 got it. as for distro... there is no angstrom-2009? none in the conf directory Feb 19 23:19:53 but i noticed that the angstrom images are all ca. 2009 Feb 19 23:20:00 maybe lemme check that Feb 19 23:20:59 yes that is the case, but it does not matter Feb 19 23:21:05 ? Feb 19 23:21:47 nvm. they are 2008. and that question was inane. sry. Feb 19 23:24:09 ant_home: it's building the ohci-hcd module and putting it on the image, not loading it though. It's not building the wlan-ng driver (in staging) into the image, it is put into the kernel-modules-prism2_usb-xxxx.ipk Feb 19 23:24:57 is it perhaps compiled in kernel? Feb 19 23:25:24 ah, no, anymore Feb 19 23:40:15 I'm guessing it should be added to task-base.bb ? Feb 19 23:52:34 yes, check task boot, base and -extended Feb 19 23:52:43 sorry, is very late here Feb 19 23:52:53 gn **** ENDING LOGGING AT Sat Feb 20 02:59:57 2010