From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GG8ui-0000BY-Pd for qemu-devel@nongnu.org; Thu, 24 Aug 2006 02:42:04 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GG8uh-0000BL-4R for qemu-devel@nongnu.org; Thu, 24 Aug 2006 02:42:03 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GG8ug-0000BI-Qo for qemu-devel@nongnu.org; Thu, 24 Aug 2006 02:42:02 -0400 Received: from [64.233.166.179] (helo=py-out-1112.google.com) by monty-python.gnu.org with esmtp (Exim 4.52) id 1GG92g-0005G7-MD for qemu-devel@nongnu.org; Thu, 24 Aug 2006 02:50:18 -0400 Received: by py-out-1112.google.com with SMTP id x31so532218pye for ; Wed, 23 Aug 2006 23:42:01 -0700 (PDT) Message-ID: Date: Thu, 24 Aug 2006 08:41:59 +0200 From: "Alessandro Corradi" In-Reply-To: <44EAC199.7070509@st.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_58884_4391146.1156401719808" References: <44EAC199.7070509@st.com> Subject: [Qemu-devel] Re: Cosimulation Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Nicolas SAUZEDE-NONST , qemu-devel ------=_Part_58884_4391146.1156401719808 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline 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 : > > 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 > *********************************** > > ------=_Part_58884_4391146.1156401719808 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline 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
***********************************


------=_Part_58884_4391146.1156401719808--