qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alessandro Corradi" <ale.corradi@gmail.com>
To: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Fwd: Cosimulation
Date: Wed, 23 Aug 2006 00:49:06 +0200	[thread overview]
Message-ID: <b921df970608221549w17f77c5amc65324062ae53756@mail.gmail.com> (raw)
In-Reply-To: <44EAC199.7070509@st.com>

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

Hi Nicolas,
Thank you for reply! The "only" trouble is that I need to descrive it as a
pci device. Taking the parallel port as an example is  very usefull for
simple  hardware  as you  made.  But I need some info for write my device
into qemu, in particular the init function for pci device as the ne2000 (In
init function of network card it set pci_conf, should I need to set up? And
what arguments should I put in pci_register_io_region function?).
My emulated device for the moment need to run in i386 architeture so I have
not to be completeness about cpu target etc...
Anyway I appreciate if you can send me your written device so I can see if
it can help me!

Thanks

Ale

2006/8/22, Nicolas SAUZEDE-NONST <nicolas.sauzede-nonst@st.com>:
>
> Hi Alessandro,
>
> Concerning your cosimulation problem, I may help a little bit,
> because when you first posted on the qemu dev list about your sysc
> project,
> it motivated me to first learn about systemc (which I didn't know) and to
> start hacking qemu to connect them together.
>
> Well I must admit I'm pretty satisfied of the results,
> I managed to build some small sysc dumb devices (gates, counters,
> ram/buffers, fpu etc..)
> (with a FIR filter in mind indeed), defined some sort of sysc written
> "interface" that offers a bus+signals to sysc, while connecting to qemu
> via a socket.
> Within qemu, I created a parallel-like device (as you said on the ml
> recently) and so I can probe my device from within guest OS (dos, linux,
> etc..)
> the device is called remote.c (like a "remote" parallel-like device)
>
> If you want I can send you some rough version of my project to see how
> (ugly) I did
> and maybe we can share our experiences...
>
> Regards,
>
> NS.
>
> --
> Best regards,
> NS.
> ************************************
> Nicolas SAUZEDE -- Subco
> ST Microelectronics Grenoble
> 12, rue Jules Horowitz, BP 217
> 38019 Grenoble Cedex
> STB Tel : 041 5142
> EXT Tel : 0476585142
> ***********************************
>
>

[-- Attachment #2: Type: text/html, Size: 2379 bytes --]

       reply	other threads:[~2006-08-22 22:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <44EAC199.7070509@st.com>
2006-08-22 22:49 ` Alessandro Corradi [this message]
2006-08-23  8:18   ` [Qemu-devel] systemc trial Nicolas SAUZEDE-NONST
2006-08-24  6:41 ` [Qemu-devel] Re: Cosimulation Alessandro Corradi

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=b921df970608221549w17f77c5amc65324062ae53756@mail.gmail.com \
    --to=ale.corradi@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).