[okl4-developer] okl4 in qemu emulated gumstix environment

[Ashish Bijlani]

thanks for the suggestion geoff. btw, how do you emulate net when
running on skyeye?
-ashish

On Tue, Aug 26, 2008 at 7:43 AM, Geoffrey Lee <glee at ok-labs.com> wrote:
> On Tue, Aug 26, 2008 at 06:05:28AM -0400, Ashish Bijlani wrote:
>> The latest code doesn't have networking for gumstix. CONFIG_SMC is
>> missing in "linux/kernel-2.6.23-v2/l4linux_config_gumstix". Simply
>> adding CONFIG_SMC doesn't work in the latest code base.
>
>
> Generally to avoid missing dependencies and other things it is
> best to edit the configuration file with menuconfig or similar
> to modify the Linux configuration.
>
> My feeling is you may find it easier to forward port the bits required
> to make the SMC driver work than deal with the limitations
> of using an older OKL4 release.
>
>        -gl
>
>>
>> -Ashish
>>
>> On Tue, Aug 26, 2008 at 6:02 AM, Geoffrey Lee <glee at ok-labs.com> wrote:
>> > On Tue, Aug 26, 2008 at 05:55:28AM -0400, Ashish Bijlani wrote:
>> >> I'm using okl4-1.4.1.1 and it doesn't seem to be having ig_serial
>> >> under "linux/kernel/arch/l4/drivers", however it has "l4e_console". Is
>> >> this normal? How do I enter KDB before executing /etc/init.d/rc?
>> >
>> > The serial driver in 1.4.1.1 is quite different to what's in the
>> > current release, hence it is normal not to find ig_serial.c.  Best
>> > thing you can do is trace the execution path inside your driver.
>> >
>> > You can manually call L4_KDB_Enter() to enter the debugger.
>> >
>> > By the way is there any reason you cannot use a newer version of
>> > OKL4?
>> >
>> >
>> >        -gl
>> >
>> >>
>> >> Thanks,
>> >> Ashish
>> >>
>> >> On Tue, Aug 26, 2008 at 5:49 AM, Geoffrey Lee <glee at ok-labs.com> wrote:
>> >> > On Tue, Aug 26, 2008 at 05:43:51AM -0400, Ashish Bijlani wrote:
>> >> >> Thanks for your quick reply. However, I'm using okl4-1.4 and I didn't
>> >> >> change anything in it. I get shell using skyeye but no network as
>> >> >> skyeye does not emulate smc91x network card. I don't get shell in
>> >> >> qemu. The face that it runs fine on skyeye, indicates that ig_serial
>> >> >> has been configured properly, isn't it?
>> >> >
>> >> > Not necessarily, the simulator may sometimes behave differently
>> >> > to how the hardware really behaves.  Please have a look around
>> >> > the system to see if there are any clues of misbehavior, for
>> >> > example, are you actually receiving any interrupts at all when
>> >> > you hit a key on the serial?  Is the serial driver initialized
>> >> > properly, or if vserial is present on the system at all?  Is there
>> >> > any interaction between the vserial and OK Linux?  The KDB should be
>> >> > quite helpful here.
>> >> >
>> >> >
>> >> >        -gl
>> >> >>
>> >> >> -Ashish
>> >> >>
>> >> >> On Tue, Aug 26, 2008 at 5:39 AM, Geoffrey Lee <glee at ok-labs.com> wrote:
>> >> >> > On Tue, Aug 26, 2008 at 05:04:57AM -0400, Ashish Bijlani wrote:
>> >> >> >> Hi,
>> >> >> >>
>> >> >> >> I'm able to boot OKL4 in QEMU emulated gumstix environment. However,
>> >> >> >> I'm not able to get "Linux user startup!" and following messages on
>> >> >> >> the qemu serial console. Any ideas why?
>> >> >> >>
>> >> >> >> This is what I did:
>> >> >> >>
>> >> >> >> cp build/image.boot /tftpboot/.
>> >> >> >> ../qemu-gumstix/arm-softmmu/qemu-system-arm -M gumstix -hda
>> >> >> >> ../connex-gumstix/flash -net nic -net tap,ifname=qtap0  -m 256
>> >> >> >> -monitor null -serial stdio -m 289 -nographic
>> >> >> >>
>> >> >> >> GUM>
>> >> >> >> GUM> setenv ipaddr 10.0.0.231
>> >> >> >> GUM> setenv serverip 10.0.0.29
>> >> >> >> GUM> tftpboot a2000000 image.boot
>> >> >> >> GUM> bootelf a2000000
>> >> >> >>
>> >> >> >> The OKL4 kernel, wombat, iguana everything is loaded and booted
>> >> >> >> properly. However, I don't see any messages after :
>> >> >> >>
>> >> >> >> NET: Registered protocol family 15
>> >> >> >> VFS: Mounted root (ext2 filesystem) readonly.
>> >> >> >
>> >> >> > This probably means ig_serial.c or the user-level serial driver
>> >> >> > in drivers/ is misconfigured.  The kernel bootup messages get
>> >> >> > shown via the KDB console, which gets routed to the driver
>> >> >> > in the OKL4 kernel.  Once you get to Linux user startup
>> >> >> > output gets routed through /dev/ttyS0, which is backed by
>> >> >> > ig_serial.
>> >> >> >
>> >> >> >        -gl
>> >> >> >
>> >> >> >>
>> >> >> >> Am I missing something?
>> >> >> >>
>> >> >> >> Thanks,
>> >> >> >> Ashish
>> >> >> >>
>> >> >> >> _______________________________________________
>> >> >> >> Developer mailing list
>> >> >> >> Developer at okl4.org
>> >> >> >> https://lists.okl4.org/mailman/listinfo/developer
>> >> >> >>
>> >> >> >
>> >> >> > --
>> >> >> >
>> >> >> >
>> >> >>
>> >> >
>> >> > --
>> >> >
>> >> >
>> >>
>> >
>> > --
>> >
>> >
>>
>
> --
>
>