All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: Ionut Cristian Paraschiv <paraschiv.ionut@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: GSoC 2010 - Device state visualization
Date: Tue, 06 Apr 2010 08:50:45 +0200	[thread overview]
Message-ID: <4BBAD9C5.4050208@web.de> (raw)
In-Reply-To: <m2h6fd4ad4f1004030850g647b2cc1wa7b300566da21e01@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1080 bytes --]

Hi Ionat,

Ionut Cristian Paraschiv wrote:
> Hello!
> 
>    My name is Ionut Cristian Paraschiv, and I am from Romania. I am a
> student in the 2nd year at Politehnica University of Bucharest, Faculty of
> Automatic Control and Computers, Computer Science Department. I like to
> program in C, Java, languages that I am very familiar with. I also have some
> knowledge of assembly language, bash scripting, basic networking and working
> with Unix based systems (I have a LPIC-1 certificate).
>   This project seems really interesting. I guess snapshots of the devices
> should be taken and be parsed in a program that displays them in a user
> friendly way.

More precisely: That program would be qemu itself in this project. Think
of typing 'show <some-device-name>' at the monitor prompt (or 'monitor
show <some-device-name>' at the gdb prompt attached to qemu) and then
getting e.g. a list of device registers and their current content.

>   I would like to get in touch with the mentor of this project to talk more
> about it.

Here I am. :)

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]

      reply	other threads:[~2010-04-06  6:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-03 15:50 [Qemu-devel] GSoC 2010 - Device state visualization Ionut Cristian Paraschiv
2010-04-06  6:50 ` Jan Kiszka [this message]

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=4BBAD9C5.4050208@web.de \
    --to=jan.kiszka@web.de \
    --cc=paraschiv.ionut@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.