>Christian Mignon wrote :
>3) use DetaolB. It's one of the many reasons why I created it. :)
But slax as dsl do have X ,when DetaolB will include X with uclibc
not just busybox
francis,
why not leave your development_available as readonly_access (svn_like or
anyftp) it would be great for learning !
(to complement wikipedia_microkernel !!! )
just to recall on linux_kernel stuff
1998 Bowman effort's reverse eng
concrete (as-built) architecture of the Linux kernel : (199
Khi Thứ bảy 09 Tháng chín 2006 8:00 chiều, Stefan Weil viết:
> > Busybox statically or dynamically linked?
> >
> > Which toolchain?
> >
> > Dirk
>
> Hello Dirk,
>
> here is my working configuration:
>
> host tools:
> gcc-Version 3.3.6 (Debian 1:3.3.6-13)
>
> cross tools (mipsel):
> gcc with patches
Khi Thứ bảy 09 Tháng chín 2006 9:16 Sáng, Dirk Behme viết:
>
> So, maybe a toolchain (glibc?) issue?
you are certaily right,
doing the same "compile hello.c,and cont on gdb session "
but with mipsel-uclibc works fine !!!
I did all that from my scratchboxmulticpu-2.3
_
Khi Thứ bảy 09 Tháng chín 2006 9:16 Sáng, Dirk Behme viết:
> Dirk
>
> Btw: Do you can connect and then step/continue with gdb to
> qemu-mipsel?
alas ! no ! cont on gdb_session gives :
[sbox-mipselglibc: ~] > qemu-mipsel -g 1234 hello
qemu: unhandled CPU exception 0x10002 - aborting
pc=0x004001a8
5e-299
> f14: w: d: fd:0 fs:-8.6795e-299
> f16: w: d:0000 fd:0 fs:-8.6795e-299
> f18: w: d: fd:0 fs:-8.6795e-299
> f20: w: d: fd:0 fs:-8.6795e-299
> f22: w: d: fd:0
xamples of how to use your vlan-config,so I can try and apply here !
for info:
I have put many toolchains armeb ,mipsel-openwrt,ppc and a livecd
ready to use ,switching among those 5 toolchains. (scratchbox base-1.0.2)
http://uit.opf.slu.cz/Members/wangji infos ,details
http://mirror.opf.slu.cz/scratchbox/ for toolchains and iso-image
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel
On Monday 06 February 2006 23:34, Michael Fisher wrote:
> My apologies...I was sure I had checked 0.8.0 when it came out and
> verifed the crashing at full-screen but apparently old age is catching
> up with me. I booted it up with DSL and it worked perfectly.
how old are you,sir?
>
> Again, my apo
I tried
qemu -kernel vmlinuz -initrd ramdisk.gz -hda slug.img
vmlinuz,ramdisk.gz,slug.img derived from a working_real_system,
got this error :
"trying to execute code outside RAM or ROM at 0x000a018b."
I suspect there is still something bigendian_at init_ram_address wrong
but don't know where to lo
