qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alessandro Corradi" <ale.corradi@gmail.com>
To: Nicolas SAUZEDE-NONST <nicolas.sauzede-nonst@st.com>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: Cosimulation
Date: Thu, 24 Aug 2006 08:41:59 +0200	[thread overview]
Message-ID: <b921df970608232341u7e73a9c1x95396e7a712023ed@mail.gmail.com> (raw)
In-Reply-To: <44EAC199.7070509@st.com>

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

Hi nicolas,

Thank you very much for your reply. In attachment you find the sc dscription
of the cirrus logic, The problem is that it is implement with a different
version of SystemC built by my university. In fact the card description
isn't a problem for me.
This description concern the emulation of 8 register and the communication
is via socket trought a message struct. The open connection is made at init
function of the card (I think) and in read/write function
(..._ioport_read/write) there are the message send/receive via socket as you
write for your remote device.
The point is that I need to be recognize by qemu and more important
recognize by debian device driver of the cirrus. I think this will be
impossbile for me :) but I try!

There are some open point for me:

1) In read/write functions i need only to descrive the operation on the
register, right? As in parallel.c, for each register there is the ioctl call
in base of the register (status, data...) I think i only need to do the
same;

2) The init function is a full open point... I wrote than there is the
socket connection, but I don't know if I need to recognize it as a pci-card.
Can somebody help me?

3) Interrupt implementation: I need only to implement ..._update_irq right?
It seems no problem, but I want to be secure about it.

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: 2990 bytes --]

      parent reply	other threads:[~2006-08-24  6:42 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 ` [Qemu-devel] Fwd: Cosimulation Alessandro Corradi
2006-08-23  8:18   ` [Qemu-devel] systemc trial Nicolas SAUZEDE-NONST
2006-08-24  6:41 ` Alessandro Corradi [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=b921df970608232341u7e73a9c1x95396e7a712023ed@mail.gmail.com \
    --to=ale.corradi@gmail.com \
    --cc=nicolas.sauzede-nonst@st.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).