[okl4-developer] okl4 on openmoko under qemu-neo

Tue Aug 5 10:45:22 EST 2008

On Thu, Jul 31, 2008 at 11:39:07PM -0500, Ashish Bijlani wrote:
> I get the following compile time error messages :
> 

These are spurious and can be ignored - Linux kernel uses a
check to test for missing system calls that is not applicable
to L4.

	-gl

> <stdin>:101:2: warning: #warning syscall restart_syscall not implemented
> <stdin>:105:2: warning: #warning syscall exit not implemented
> <stdin>:109:2: warning: #warning syscall fork not implemented
> <stdin>:113:2: warning: #warning syscall read not implemented
> <stdin>:117:2: warning: #warning syscall write not implemented
> <stdin>:121:2: warning: #warning syscall open not implemented
> <stdin>:125:2: warning: #warning syscall close not implemented
> <stdin>:133:2: warning: #warning syscall creat not implemented
> <stdin>:137:2: warning: #warning syscall link not implemented
> <stdin>:141:2: warning: #warning syscall unlink not implemented
> <stdin>:145:2: warning: #warning syscall execve not implemented
> <stdin>:149:2: warning: #warning syscall chdir not implemented
> <stdin>:153:2: warning: #warning syscall time not implemented
> <stdin>:157:2: warning: #warning syscall mknod not implemented
> <stdin>:161:2: warning: #warning syscall chmod not implemented
> <stdin>:165:2: warning: #warning syscall lchown not implemented
> <stdin>:177:2: warning: #warning syscall lseek not implemented
> <stdin>:181:2: warning: #warning syscall getpid not implemented
> <stdin>:185:2: warning: #warning syscall mount not implemented
> <stdin>:193:2: warning: #warning syscall setuid not implemented
> <stdin>:197:2: warning: #warning syscall getuid not implemented
> <stdin>:205:2: warning: #warning syscall ptrace not implemented
> <stdin>:209:2: warning: #warning syscall alarm not implemented
> <stdin>:217:2: warning: #warning syscall pause not implemented
> <stdin>:221:2: warning: #warning syscall utime not implemented
> <stdin>:233:2: warning: #warning syscall access not implemented
> <stdin>:245:2: warning: #warning syscall sync not implemented
> <stdin>:249:2: warning: #warning syscall kill not implemented
> <stdin>:253:2: warning: #warning syscall rename not implemented
> <stdin>:257:2: warning: #warning syscall mkdir not implemented
> <stdin>:261:2: warning: #warning syscall rmdir not implemented
> <stdin>:265:2: warning: #warning syscall dup not implemented
> and few others....
> 
> WARNING: "default_virtpool" [vmlinux] is COMMON symbol
> WARNING: "__pd_ext_lock" [vmlinux] is COMMON symbol
> WARNING: "default_physpool" [vmlinux] is COMMON symbol
> WARNING: "cb" [vmlinux] is COMMON symbol
> WARNING: "__pd_ext_thread" [vmlinux] is COMMON symbol
> WARNING: "intervm_bwd" [vmlinux] is COMMON symbol
> WARNING: "__pd_ext_space" [vmlinux] is COMMON symbol
> WARNING: "__iguana_pager" [vmlinux] is COMMON symbol
> WARNING: "test_file" [vmlinux] is COMMON symbol
> WARNING: "intervm_ctl_mutex" [vmlinux] is COMMON symbol
> WARNING: "__okl4_environ" [vmlinux] is COMMON symbol
> WARNING: "ftable" [vmlinux] is COMMON symbol
> WARNING: "intervm_fwd" [vmlinux] is COMMON symbol
> WARNING: "__pd_ext_utcb" [vmlinux] is COMMON symbol
> WARNING: "dummy" [vmlinux] is COMMON symbol
> WARNING: "test_file_2" [vmlinux] is COMMON symbol
> WARNING: "intervm_ctl" [vmlinux] is COMMON symbol
> WARNING: "__pd_ext_return_space" [vmlinux] is COMMON symbol
> WARNING: "default_clist" [vmlinux] is COMMON symbol
> WARNING: vmlinux.o(.text+0x20): Section mismatch: reference to
> .init.text:free_initmem (between 'init_post' and 'try_name')
> WARNING: vmlinux.o(.text+0x82c): Section mismatch: reference to
> .init.data:bootmem_area (between '__libc_setup' and '__lib_init')
> WARNING: vmlinux.o(.text+0x830): Section mismatch: reference to
> .init.data:bootmem_areas (between '__libc_setup' and '__lib_init')
> WARNING: vmlinux.o(.text+0xb40): Section mismatch: reference to
> .init.data:boot_command_line (between 'main' and '__sys_entry')
> WARNING: vmlinux.o(.text+0xb6c): Section mismatch: reference to
> .init.text:start_kernel (between 'main' and '__sys_entry')
> 
> -ashish
> 
> On Thu, Jul 31, 2008 at 11:14 PM, Ashish Bijlani
> <ashish.bijlani at gmail.com> wrote:
> > I got it working finally. I was missing the -serial stdio and -nographic.
> >
> > However, it pagefaults. The log is attached.
> >
> > Am I missing something?
> >
> > Please lemme know.
> >
> > -ashish
> >
> > On Thu, Jul 31, 2008 at 9:53 PM, Ashish Bijlani
> > <ashish.bijlani at gmail.com> wrote:
> >> Hi,
> >>
> >> I've been trying to boot okl4 on openmoko neo1973 qemu-neo based
> >> emulator, but it doesn't work. Nothing appears on the screen.
> >>
> >>  PATH=/home/ashish/okl4/opt/nicta/tools/gcc-3.4.4-glibc-2.3.5/arm-linux/bin/:$PATH
> >> ./tools/build.py machine=gta01 project=iguana wombat=true
> >> toolprefix=/home/ashish/okl4/opt/nicta/tools/gcc-3.4.4-glibc-2.3.5/arm-linux/bin/arm-linux-
> >> simulate
> >>
> >> This is what I did -
> >>
> >> * downloaded qemu-neo from
> >> http://wiki.openmoko.org/wiki/Openmoko_under_QEMU followed the
> >> instructions to build openmoko emulated environment. linux boots fine
> >> in this emulated environment.
> >>
> >> * copied "qemu-system-arm" and  "openmoko/openmoko-flash.base"  under
> >> "/opt/okl/Linux-i386/usr/share/qemu-neo/"
> >>
> >> The command that seems to be executing is -
> >> "/opt/okl/Linux-i386/bin/qemu-system-arm -M gta01 -m 130 -mtdblock
> >> /opt/okl/Linux-i386/usr/share/qemu-neo/openmoko-flash.base -serial
> >> stdio -nographic -kernel %s" % (source[0].abspath)
> >>
> >> I tried booting okl4/build/images/image.boot directly - doesn't work.
> >> Emulator loads u-boot and then u-boot loads the kernel at 0x30100000 -
> >> fails (Bad Magic Number)
> >> arm-softmmu/qemu-system-arm -M gta01 -m 130 -mtdblock
> >> openmoko/openmoko-flash.image -kernel
> >> /home/ashish/okl4/okl4_2.1/build/images/image.boot -usb -show-cursor
> >>
> >> On the mailing list archive I saw this post
> >> http://lists.okl4.org/pipermail/developer/2008-April/000917.html and
> >> tired changing the load addr to 0x31000000 - doesn't work - u-boot
> >> loads okl4, but fails with Bad Magic Number again.
> >>
> >> I tried booting the binary image (invoking objcopy) as well since
> >> u-boot boots linux's binary bootable image on qemu-neo, but it fails
> >> as well with Bad Magic Number.
> >>
> >> Am I missing something? Please help.
> >>
> >> Also, in the code base I didn't see any server/driver dirs for flash
> >> and networking for openmoko/gta01 so just curious to know how okl4
> >> virtualizes flash/network for linux based virtual machines running on
> >> top of okl4?
> >>
> >> Thanks,
> >> Ashish
> >>
> >
> 
> _______________________________________________
> Developer mailing list
> Developer at okl4.org
> https://lists.okl4.org/mailman/listinfo/developer
> 

-- 