00:35:52 | Sammy | morning all |
07:24:36 | erikm | morning |
07:25:34 | Sammy | morning ...erikm |
07:27:55 | Russ | so how's the demo going? |
07:31:08 | erikm | Russ: no idea :) |
07:31:18 | Russ | heh |
07:31:42 | erikm | Russ: I have a couple of backup demos, so *I* can show something |
07:33:07 | Russ | a rock the cradle yo-yo trick? |
07:33:39 | erikm | Russ: no, one MPEG2 decoding demo (continuously plays MPEG2 movies to the LCD) |
07:33:56 | erikm | Russ: and a clock&voltage scaling demo with real-time measurents |
09:05:36 | Sammy | erikm : do you have free time ? |
09:08:21 | erikm | not really |
09:08:36 | erikm_lunch | and I |
09:08:44 | erikm_lunch | I'm having lunch right now |
10:16:59 | Sammy | why ./configure --with-linux-prefix=/skiff/local/arm-linux --with-board=lart "arm-lart-linux-gnu" need the command in " " |
10:17:25 | erikm | which command? |
10:18:50 | Sammy | arm-lart-linux-gnu |
10:18:58 | Sammy | what's this for ? |
10:19:04 | erikm | that doesn't need to be in " " |
10:19:10 | erikm | the shell won't expand it |
10:19:54 | Sammy | oh , that's I just you want to let you know ... |
10:20:27 | Sammy | I mean if I don't add that , and the blob binary code still can make it .. |
10:20:59 | Sammy | so I am curious what's this command use for |
10:22:56 | Sammy | and also in Guide to ARMLinux for Develop write that host=i386 , and I don't type it , and also still can pass the cross compiler ...so strange |
10:25:22 | erikm | arm-lart-linux-gnu is the target architecture. you almost never need host=i386,only if you're building a canadian cross compiler |
10:25:47 | erikm | if the guide to armlinux says you need a --host flag, it is wrong |
10:26:44 | Sammy | ho ho this book write by Wooky and Paul Webb ... |
10:27:04 | Sammy | Do U know them ? |
10:28:38 | Sammy | so if I don't give target architecture , cross compiler still know that to compiler for ARM ? |
10:28:45 | Sammy | right |
10:31:29 | erikm | I know wookey, yes |
10:32:12 | erikm | no, if you don't supply the target architecture, the configure script will not know that you want to cross compile and quite a lot of incorrect assumptions |
10:34:24 | erikm | oh, and using the flag --with-linux-prefix=/skiff/local/arm-linux will _not_ work. the --with-linux-prefix expects the path to the configured _kernel_ source, not to the processed headers from the cross compiler |
10:40:54 | Sammy | om ... but I still can pass it , and after make the size is the same |
10:41:08 | Sammy | -rwxr-xr-x 1 root 13974 Sep 5 19:50 blob |
10:41:09 | Sammy | -rwxr-xr-x 1 root 12950 Sep 5 19:50 blob-rest |
10:41:10 | Sammy | -rwxr-xr-x 1 root 23536 Sep 5 19:50 blob-rest-elf32 |
10:41:12 | Sammy | -rwxr-xr-x 1 root 600 Sep 5 19:50 blob-start |
10:41:12 | Sammy | -rwxr-xr-x 1 root 35311 Sep 5 19:50 blob-start-elf32 |
10:41:41 | erikm | well, plain luck if it works. but don't complain if it doesn't. |
10:44:38 | Sammy | but my cross compiler put in /skiff/local/ not /usr/local/ I am following the handhelds.org HOWTO Build A Cross Toolchain For ARM .... |
10:45:09 | Sammy | So maybe this is why it work I think |
10:45:34 | Sammy | LART show |
10:45:50 | erikm | all nice and well, but the kernel headers in the cross compiler toolchain are NOT the correct kernel headers. if it works fine, but it is not guaranteed to work |
10:46:39 | Sammy | ioi .. |
10:47:17 | Sammy | so what is your suggest ? |
10:48:10 | Sammy | at now I can cross compiler the blob for lart , next step , I want to show some massage on LCD on LART |
10:48:32 | erikm | Sammy: install X and use xmessage |
10:48:51 | Sammy | X server ? |
10:49:52 | erikm | yes, compile kernel with SA1100 frame buffer device |
10:50:23 | erikm | after that you can run X server, or just echo foobar > /dev/tty1 |
10:50:44 | erikm | or mmap(/dev/fb0) and directly draw on the frame buffer |
10:51:52 | erikm | or use microwindows |
10:51:56 | Sammy | is that sa1100fb.c with in kernel original ? |
10:52:10 | erikm | or qt for framebuffer, or GTK+ for framebuffer |
10:52:24 | erikm | it's in the latest -np kernel |
10:53:05 | Sammy | yah , I see it the QT for framebuffer is what I want to use ... |
10:54:42 | Sammy | sorry what is -np ? I don't know more about kernel , but I am hard reading from the side arm.linux |
10:56:43 | erikm | -np is the nicolas pitre patch set |
10:56:51 | erikm | (it *is* explained on the LART site) |
10:58:59 | Sammy | oh I know , sorry , just lost memory ... |
11:00:01 | Sammy | so that if I usr cross compiler don't use that build by my self ? |
11:03:33 | erikm | parse error, sorry. if you have a precompiled cross compiler you don't have to build that yourself (if that is what you mean) |
11:07:48 | Sammy | yah , which one should I use ? |
11:09:04 | Sammy | and the point is which kernel header is currect ? |
11:11:24 | Sammy | I use binutils-2.9.5.0.22 & gcc02.95.2 & glibc-2.1.2 & kernel-2.4.7 & gcc-2.95.2-diff-991022 & gcc-fold-const,patch & patch-2.4.7-rmkl |
11:11:43 | Sammy | which one is wrong ? |
11:20:55 | erikm | don't even *think* about building your own cross compiler, just download one of my precompiled compilers, like the gcc-2.95.2 or gcc-2.95.3 based |
11:21:21 | erikm | (preferably the gcc-2.95.2 version) |
11:21:45 | erikm | it's tested, it works, it's known good |
11:27:56 | Sammy | Thanx erikm .... |
11:29:30 | Sammy | is watching the maillist #539 and #540 ... |
11:35:46 | Sammy | thanx again ... |
11:36:20 | Sammy | for the answer ARM boot |
11:36:40 | erikm | oh, was that you |
11:36:50 | Sammy | no , |
11:37:18 | Sammy | buy now for me is the same place to do , |
11:38:09 | Sammy | so know where to start is important ...I think |
11:41:59 | erikm | no, it isn't. you don't even have to care about it. I've been running arm-linux on a LART for over a year without even knowing where the kernel started. |
11:42:50 | erikm | only when nicolas pitre changed the discontiguous memory support a year ago I needed to know how the kernel started because his patches broke on LART. |
11:45:26 | Sammy | but If I don't , how do I know what time the frame buffer is on ? |
11:46:06 | Sammy | I mean know the step by start kernel until show the login : |
11:46:26 | erikm | why do you even *care* when the framebuffer is on? |
11:47:15 | Sammy | because now my setp is show something on LCD ... |
11:47:23 | erikm | it's on as soon as userland starts, i.e.: when init is started. |
11:49:34 | Sammy | all driver is start there ? |
11:52:05 | erikm | of course, otherwise the kernel wouldn't be initialised |
11:52:46 | Sammy | OK , tell you what I think ,step by step , from start , boot and then kernel on LCD show , filesystem and ramdisk is on , QT on , show something like HELLO World on LCD screen , and can use touch panel ... |
11:53:15 | Sammy | and say that just like handheld is right |
11:55:01 | Sammy | and then I can porting blob , kernel , .....to another platform.... |
11:55:14 | Sammy | like Tuxscreen .... |
11:56:28 | erikm | that's more or less the idea, yes |
11:57:20 | Sammy | but if I want to use QT , right now I must let the framebuffer on, |
12:00:02 | erikm | which is quite a logical assumption, yes. |
12:01:29 | Sammy | because the experience porting linux and QT on IPAQ , I still don't know what they doing behind ... |
12:47:22 | sammy_ | erikm : what is the time on your place ? |
12:48:40 | erikm | 15:50 |
12:50:55 | sammy_ | ~ difference 6hr ... it's time to go home . good night . |
12:51:52 | erikm | 'night |