Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - radiochickenwax

Pages: 1 2 [3] 4 5 ... 11
Debian / Kernel Conf File For Kernel
« on: July 02, 2008, 11:36:13 pm »
Thanks a lot for your help.  I'm not very experienced with kernel building and still having troubles.


1. get the patch from yonggun's site. and apply it using patch -p0 < patch-2.6.24

I'm not sure if this is right, but I renamed the patch from to patch- and applied using
Code: [Select]
patch -p1 < patch- instead of -p0 (-p0 asked me on every step which file to patch).  Is this patch valid for 2.6.24 only?

It also says on that
These are patched with angstrom patches and without cpufreq.

I think the correct page for the patches is:, but I don't know for sure.


Code: [Select]
make zImage ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi-
works okay.


Code: [Select]
make uImage ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi-
immediately after says:
Code: [Select]
  CHK     include/linux/version.h
make[1]: `include/asm-arm/mach-types.h' is up to date.
  CHK     include/linux/utsrelease.h
  CALL    scripts/
:1097:2: warning: #warning syscall fadvise64 not implemented
:1265:2: warning: #warning syscall migrate_pages not implemented
:1321:2: warning: #warning syscall pselect6 not implemented
:1325:2: warning: #warning syscall ppoll not implemented
:1365:2: warning: #warning syscall epoll_pwait not implemented
  CHK     include/linux/compile.h
  Kernel: arch/arm/boot/Image is ready
  Kernel: arch/arm/boot/zImage is ready
  UIMAGE  arch/arm/boot/uImage
"mkimage" command not found - U-Boot images will not be built
  Image arch/arm/boot/uImage is ready

Code: [Select]
make clean before doing
Code: [Select]
make uImage ... seems to work, but I haven't flashed yet.  It gives "arch/arm/boot/Image" instead of "arch/arm/boot/uImage" as I'd anticipated.

Debian / Kernel Conf File For Kernel
« on: July 02, 2008, 03:56:27 am »

1. Are we missing the step to patch the kernel sources?

2. Does this cross-compiler support distcc?

3. Will
Code: [Select]
make uImage instead of
Code: [Select]
make zImage build for uBoot?

4. Could someone point me in the direction of the "fastfpe" and "cpufreq" patches?
                      (4a.  They need to be applied separately right?)

5. How about tetsu's pressure sensitive patches?

PocketPenguin / Gumstix
« on: June 30, 2008, 10:51:34 am »
Quote from: Ragnorok
600Mhz XScale w/ 128MB Ram on a board the size of a stick of gum.

...and they sell a 4.3" touch-screen (bigger than the SL6000) for $80!  Yep, I've gotta get me one of these.  It'd be nice to hook it up to the zaurus for a mobile cluster if nothing else.

For Sale / Wanted / Sold: Sl6000 + Sled And Batteries
« on: June 29, 2008, 06:14:43 pm »
You guys are awesome.  I didn't even have time to contribute!  (which is okay by me I guess, kinda broke)  I'll try to do more pdaxrom development and testing if a 6000 release comes out.

PocketPenguin / Gumstix
« on: June 28, 2008, 01:29:49 am »
another thing that concerns me about gumstix is that no one seems to comment on it, and the OS is built via OpenEmbedded.  This is the Open Embedded Software Foundation forum right?  I would think (semi) open hardware would draw a lot of attention, maybe enough to have its own thread?

For Sale / Wanted / Sold: Sl6000 + Sled And Batteries
« on: June 27, 2008, 02:36:02 am »
I'm in for InSearchOf's fund... PM me...

For Sale / Wanted / For Sale: Enfora Quad-band Gsm/gprs Modem
« on: June 27, 2008, 02:03:12 am »
I'm thinking of buying this card, since my phone just died recently.

Would anyone care to comment how well it works with the zaurus?  The following link:

claims that it does NOT use EDGE.


Collected more links here related to my question:

Enfora Gsm110 Gprs Connection Problems
Using a Zaurus as Cell Phone
GSM CF Card: C860 as Cellphone
Mobile Phone Type Applications, A litte work on Zphoneing You'll love!!!
How-TO: Connet CF GPRS/GSM (AudioVox RTM8000) to internet


sparkfun's gsm modules/accessories

garsh, this whole GSM thing seems a little complex!

PocketPenguin / Gumstix
« on: June 21, 2008, 10:25:36 pm »
I was vaguely thinking that a mintyboost could be hacked to power the gumstix, and a large altoids or camel cigarette tin could be used as a starter case for the complete mobile setup.

At a glance, all that would need to be done is change the usb port to a 4mm coaxial, or buy the $10 converter.  I've been kinda busy, so finding the parts on hasn't really panned out just yet.

PocketPenguin / Gumstix
« on: June 21, 2008, 10:22:30 pm »
Didn't find this here yet, but I didn't really search, so forgive me if this is a repeat post.  At best, this might renew some interest.

It's got everything we would need at a reasonable price AFAIK ; not much documentation however.  If anyone has done this already, maybe some links/notes/screenshots could be posted?

I haven't really seen any screenshots of Xorg running yet, but it's supposedly in one of the available ROM images. with matchbox/kdrive

EDIT:  gumstix was mentioned way back here over two years ago along with the coLibri module which has been upgraded now to the pxa320 @ 806MHz, but doesn't come with OpenEmbedded.

EDIT2:  mini-ITX is too big.  (saving to buy a robostix combo)

Debian / Why Is Debian Slow?
« on: June 21, 2008, 10:02:46 pm »
Quote from: domi007
You can try crosstool.
It can download all the things you need for cross-compile. It has a specific script for intel-xscale processors.


Any pointers to a zaurus/cross-tool "how to"?

Zaurus - pdaXrom / Pdaxng
« on: June 21, 2008, 09:39:23 pm »
Quote from: InSearchOf
Ok, only 1 person signed up for the mailing list so far!.. Come on, All the cool kids are doing it!!!... I'm looking for fol\ks that want to help, want to ask questions, want to test... Whatever just sign up and speak!


Are the archives going to be available?

I just signed up, but it still says "permission denied".  Please don't let this distract you from actually working on the ROM, I was just curious if there is current activity on the mailing list.

6000 - Tosa / Tosa Development Plan
« on: April 24, 2007, 02:19:06 pm »
This sorta reminds me of the etched marble experiments

I downloaded the build tools mentioned before:

I decoded the scripts from pdaxrom beta1 and OZ 3.4.5 rc2 with the edecsh.c program.  I'll try attaching them to this post in a little while.

Meanie's build tools have endecsh compiled already.
Grab an file (I used the one from pdaXrom C3000 beta2) and use the endecsh utility to decode it into a normal shell script and customise the script.
# endecsh -d updater.txt

Then use endecsh to encode the script.
# endecsh -e updater.txt

You can compile endecsh yourself or extract it from the updater-tools.bin file.


The updater-tools.bin file is a tar file. It contains utilities from the pdaXrom tools.tar file.

... and indeed the endesch program is there.

I'd think putting fairly little in the jffs2, and including altboot, or configuring uboot or doing a pivot root to sd or cf would be the best bet
[div align=\"right\"][a href=\"index.php?act=findpost&pid=159616\"][{POST_SNAPBACK}][/a][/div]

Altboot to SD would be my option of choice, since CF seems to have problems between suspends on Tosa in my experiences with PocketWorkstation. Hopefully, the larger SD support with the OZ kernel will bypass the 1GB limitation, and ipkg-link will still work for the CF slot.

I'm a little confused about how altboot works, so that might take awhile to figure out.  Also, as mentioned before, and from what I can see so far, the two versions have very  different installer scripts, which is a little intimidating, but I feel like I'm getting at least a little closer to patching them together, or at least understanding whether the OZ 2.6 kernel will flash with the pdaxrom rootfs.

Another thing that's troubling me is that pdaxii13 uses the 2.4.20 kernel, (from pdaxrom beta2)  and OZ3.4.5 uses a 2.6 kernel... not sure which version off-hand.  I think that choice was made mainly because pdaxrom beta4 (with the 2.6 kernel)  seemed so buggy compared to beta3 (with the 2.4 kernel) , but there might be more technical reasons as well.

Gonna try to work on the initrd.bin files with the jffs2 filesystems next. (maybe later today, or tomorrow... turns out I didn't have any time for a couple weeks, but I'd really like to get back to this sooner than later).

6000 - Tosa / Tosa Development Plan
« on: April 23, 2007, 08:01:03 pm »
Yeah, I've been wanting to do something like that for awhile.  The trouble is which elements to put into the jffs2 filesystem, and that seems a matter of personal preference.  
To some extent it doesn't even matter, I'd be happy right now just to get the pdaxrom rootfs to boot with the OZ kernel.  I'll try this a little later today, and post some results.

6000 - Tosa / Tosa Development Plan
« on: April 22, 2007, 06:48:00 pm »
Alternatively, you could also use the OZ kernel and customise the OZ installer, and build a custom pdaXrom rootfs and make a initrd.bin file from that instead of using the OZ rootfs.
[div align=\"right\"][{POST_SNAPBACK}][/a][/div]

This sounds like the best option for me personally.

The OZ installer on the other hand is quite stupid. it just assumes a standard partition layout and flashes the ROM/distro. The pdaXrom installer is much better in this regard. it has options to allow user to resize partitions, etc..., the best would be to have an option in the installer to restore the original / generate the required partition table.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=159496\"][{POST_SNAPBACK}][/a][/div]

So, to follow this path, we could use [a href=\"]your build tools[/url] to customize the following: =  need to modify versiion of pdaxrom's
zImage.bin = OZ or angstrom kernel image (untouched?)
initrd.bin = need to put elements from pdaxrom's jffs2 and OZ's jffs2 filesystems.

6000 - Tosa / Making Angstrom Work On Tosa
« on: April 22, 2007, 05:17:10 pm »
Try today's build and report/update bugs in the OE bugtracker
[div align=\"right\"][{POST_SNAPBACK}][/a][/div]


[div align=\"right\"][a href=\"index.php?act=findpost&pid=159500\"][{POST_SNAPBACK}][/a][/div]

The OE bugtracker is at [a href=\"][/url], not here
[div align=\"right\"][a href=\"index.php?act=findpost&pid=159502\"][{POST_SNAPBACK}][/a][/div]

Agreed, this thread is not a bugtracker.  Rather, it is a forum to do more than list bugs.

Would you prefer that no one discuss issues with the angstrom distro outside of the bugtracker and/or wiki?

Pages: 1 2 [3] 4 5 ... 11