qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Anderson Lizardo" <anderson.lizardo@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [4215] Nokia N800 machine support (ARM).
Date: Thu, 17 Apr 2008 23:43:31 -0400	[thread overview]
Message-ID: <5b5833aa0804172043o76747a53ie18fdce6f760c356@mail.gmail.com> (raw)
In-Reply-To: <fb249edb0804171603k7c5ed858g6e89b5fc34a00ae5@mail.gmail.com>

On Thu, Apr 17, 2008 at 7:03 PM, andrzej zaborowski <balrogg@gmail.com> wrote:
>  The firmware kernel is very quiet, so if it's unable to mount the
>  initfs, it'll hang at the blank screen.  A kernel built from sources
>  will dump logs on the third serial port.  To boot Linux you'll need to
>  provide the kernel and a flash image with at least two of the five
>  partitions present on it.  The flash is supplied with "-mtdblock
>  filename" and the file should be of 276824064 bytes (256 MB of data +
>  OOB data at the end).  You'll need to have the initfs and the rootfs
>  present in this image, and for Maemo also the "config" partition (not
>  my fault). Poky (pokylinux.org) boots fine with just the stock initfs
>  + Poky rootfs.

A nice feature would be to allow the host to communicate with nolo
running inside qemu (e.g. through a TCP server or something), then
modify the free 0xFFFF flasher (http://nopcode.org/0xFFFF/) to be able
to communicate with this server. In practice, this would allow to
"flash" the emulated device like we do for the real hardware.

Is that feasible?

Regards,
-- 
Anderson Lizardo
Instituto Nokia de Tecnologia (INdT)
Manaus - Brazil

  reply	other threads:[~2008-04-18  3:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-14 21:57 [Qemu-devel] [4215] Nokia N800 machine support (ARM) Andrzej Zaborowski
2008-04-15  8:00 ` [Qemu-devel] " John R. Hogerhuis
2008-04-17 21:58   ` andrzej zaborowski
2008-04-17 20:59 ` consul
2008-04-17 23:03   ` andrzej zaborowski
2008-04-18  3:43     ` Anderson Lizardo [this message]
2008-04-18 12:13       ` 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=5b5833aa0804172043o76747a53ie18fdce6f760c356@mail.gmail.com \
    --to=anderson.lizardo@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).