From: "andrzej zaborowski" <balrogg@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu-system-arm -M akita/terrier - which roms work? (and cursor issue)
Date: Tue, 24 Jul 2007 03:25:42 +0200 [thread overview]
Message-ID: <fb249edb0707231825r57bd529dq742f6aba11ad3c69@mail.gmail.com> (raw)
In-Reply-To: <20070724011115.GA44643@saturn.kn-bremen.de>
On 24/07/07, Juergen Lock <nox@jelal.kn-bremen.de> wrote:
> Hi!
>
> I just played with this a bit and although I got the stuff at
> http://pokylinux.org/releases/clyde-2.0/
> somewhat working (tried the akita ones going after
> http://butterfeet.org/?m=200705
> , I seem to miss -showcursor and consequently got no cursor
> which made navigating the gui a `little' difficult... :) - anyway
> I couldnt get the sharp rom kernel to boot further than showing
> the splash screen with a blinking cursor (i tried terrier and akita ones,
That would suggest that it's hanging somewhere in the userspace (but
not necessarily). Have you tried booting with no init scripts? (e.g.
init=/bin/sh) Otherwise do you have sources for the kernel you're
using so that you could enable initcalls debugging in its config?
> they both seem to hang somewhere regardless of a proper -mtdblock passed
> or even none, at least info registers in the monitor showed no changes.)
When you issue "info registers" more than likely the kernel is always
in the idle loop saving the battery power, so it will almost always
show the same values, even if there are actually processes running and
doing some work.
> Anyone know which roms work? atm I want to play with debian for the
> existing sharp rom that i have on the zaurus (a c3200), so a rom thats
> at least similar to sharp would be preferable...
Unfortunately I have no physical zaurus, so no access to any Sharp rom
because they are copyrighted. Installing debian however should not
depend on what rom you use, afterall debian is supposed to replace the
contents.
Cheers
next prev parent reply other threads:[~2007-07-24 1:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-24 1:11 [Qemu-devel] qemu-system-arm -M akita/terrier - which roms work? (and cursor issue) Juergen Lock
2007-07-24 1:25 ` andrzej zaborowski [this message]
2007-07-24 20:25 ` Juergen Lock
2007-07-25 20:13 ` andrzej zaborowski
2007-07-26 21:37 ` [Qemu-devel] qemu-system-arm -M akita/terrier - which roms work? (have first patches now :) Juergen Lock
2007-07-27 22:25 ` andrzej zaborowski
2007-07-27 22:27 ` andrzej zaborowski
2007-07-28 0:12 ` Juergen Lock
2007-07-29 1:15 ` [Qemu-devel] qemu-system-arm -M akita/terrier - which roms work? (more patches... :) Juergen Lock
2007-07-29 1:46 ` andrzej zaborowski
2007-07-29 22:30 ` Juergen Lock
2007-07-31 0:37 ` Juergen Lock
2007-07-31 20:42 ` Juergen Lock
2007-07-31 21:31 ` andrzej zaborowski
2007-07-31 23:32 ` Juergen Lock
2007-08-02 20:04 ` Juergen Lock
2007-08-20 22:45 ` [Qemu-devel] qemu-system-arm -M akita/terrier - which roms work? (more patches, this time keyboard... :) Juergen Lock
2007-07-24 1:36 ` [Qemu-devel] qemu-system-arm -M akita/terrier - which roms work? (and cursor issue) andrzej zaborowski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fb249edb0707231825r57bd529dq742f6aba11ad3c69@mail.gmail.com \
--to=balrogg@gmail.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).