Re: 'virtual HW' into kernel (SystemC)

[MÃrius MontÃn]

Mikael Starvik wrote:

>>Application <-> our driver <-> kernel PCI-subsystem <-> our link <-> 
>>daemon <-> SystemC simulator. 
>>    
>>
>
>  
>
>>Our link and our daemon get all PCI communication, and interface to 
>>SystemC simulator. 
>>Is that so complex to develop? 
>>    
>>
>
>No, not really. I've implemented a link like this
>
>Application<->driver<->our link<->daemon<-TCP/IP->glue<->Verilog simulator
>
>In your case I would probably implement a "fake" PCI bridge that forwards any PCI access to you daemon and puts the requesting process to sleep until the request has been processed. Some drivers may of course break due to the latency. 
>
>Our link is a kernel module that queues up requests from the driver and deliver them to the daemon through a poll/read interface. Each process that make a request is put to sleep until the request has been answered by the dameon. A couple of days of development. A bit more in your case due to the fake PCI bridge (yes, I have implemented one of those as well for cardbus).
>
>Regards
>/Mikael
>
>  
>

Can you send me or post your code?
This code can be a good starting point for us.

Thanks

MÃrius

> 
>
>  
>

begin:vcard
fn;quoted-printable:M=C3=A0rius Mont=C3=B3n
n;quoted-printable;quoted-printable:Mont=C3=B3n;M=C3=A0rius
org;quoted-printable:UAB;Departament de Microelectr=C3=B2nica i Sistemes Electr=C3=B2nics
adr:Campus de la UAB;;QC-2088 ETSE;Bellaterra;Barcelona;08193;SPAIN
email;internet:marius.monton@xxxxxx
tel;work:+34935813534
x-mozilla-html:TRUE
url:http://cephis.uab.es
version:2.1
end:vcard