[Qemu-devel] wireless pci device driver

[Qemu-devel] wireless pci device driver

[Clemens Kolbitsch]

> If you need a wireless PCI device, I can provide code for
> TNETW1130 (ACX111). Get it from
> http://svn.berlios.de/svnroot/repos/ar7-firmware/qemu/trunk/hw/tnetw1130.c
>
> It works partially with an emulated Linux 2.6.20:
> the PCI card is recognized, and it loads firmware.
>
>   
wow!! it'll take a good look at that... the whole day i've been trying 
to reverse engineer some of the atheros driver (obviously without any 
good results due to my poor knowledge of this stuff).

this could save me A LOT of work!!

greets,
  Clemens

Re: [Qemu-devel] Create Fake PCI Cards

[Clemens Kolbitsch]

> If you need a wireless PCI device, I can provide code for
> TNETW1130 (ACX111). Get it from
> http://svn.berlios.de/svnroot/repos/ar7-firmware/qemu/trunk/hw/tnetw1130.c
>
> It works partially with an emulated Linux 2.6.20:
> the PCI card is recognized, and it loads firmware.
>
> Stefan
>   
hi!
did you ever get it to work in qemu? by now, i've tried about a dozen 
drivers both in win xp and linux (kubuntu with ndiswrapper), but no success.

win xp first only saw an unknown ethernet card. then i forced it to use 
dlink dwl-520(+), texas instruments/us robotics drivers but only get a 
problem when installing "hardware could not be started"

linux's lspci says that it is a texas instruments ACX111 - so that is 
good. but without a working winxp driver, i don't think i'll ever get 
ndiswrapper working (by the way... yes, i need ndiswrapper and not an 
linux-original driver.. but since i have to get it to work in winxp as 
well, the linux-part should not be a problem afterwards :-)  )

did you ever get further??
thanks!!

[Qemu-devel] Getting started programming a HW Device

[Clemens Kolbitsch]

Hi everyone!
Could someone please point out some links to a good documentation and/or 
tutorial on how to write hardware devices for qemu?

I have been reading through the parallel & ne2k code and - although it 
is not that hard - just do not get all the information necessary it seems.

are there some places, where functions like
 - qemu_chr_ioctl
 - cpu_register_io_memory
 - pci_register_io_memory
 - pci_register_device
 - etc.

are described shortly (or even in more detail ;-)  )?

My current problem is the following: While loading a module in the 
client-os it get the error

"cannot reserve PCI memory region"

(from the dadwifi (yes - not madwifi) ath_pci module).

What do i have to do in order to get this right?

cheers!

[Qemu-devel] QEMU/PCI shutdown event

[Clemens Kolbitsch]

hi everyone!
i'm programming a pci-device that includes some threads & 
socket-connections (that allow remote debugging of my device).

however, i want to cleanly shutdown all threads and sockets when qemu 
exits... is there an easy way of getting informed of a qemu shutdown?

(something similar to pci_device_init...)

thanks!!

RE: [Qemu-devel] QEMU/PCI shutdown event

[Dor Laor]

>hi everyone!
>i'm programming a pci-device that includes some threads &
>socket-connections (that allow remote debugging of my device).
>
>however, i want to cleanly shutdown all threads and sockets when qemu
>exits... is there an easy way of getting informed of a qemu shutdown?
>
>(something similar to pci_device_init...)
>
>thanks!!
>

You can use qemu_register_reset handler.
Note that it get's called when the guests exits but not if you just quit
the monitor.

[Qemu-devel] Detecting Client OS BSOF/Kernel Oops

[Clemens Kolbitsch]

Hi!
I'd like to detect if the client OS crashes... right now, only for 
linux, but windows systems will become interesting for me as well in the 
future...

Is there an easy way of detecting if a BSOD or a kernel oops happened?? 
Maybe that'd be possible by checking if the IP is inside a certain range 
(I could find that location, I think... it does not have to be working 
generically... for specific client OS would be sufficient)!!

Thanks!

Re: [Qemu-devel] Detecting Client OS BSOF/Kernel Oops

[Avi Kivity]

Clemens Kolbitsch wrote:
> Hi!
> I'd like to detect if the client OS crashes... right now, only for
> linux, but windows systems will become interesting for me as well in
> the future...
>
> Is there an easy way of detecting if a BSOD or a kernel oops
> happened?? Maybe that'd be possible by checking if the IP is inside a
> certain range (I could find that location, I think... it does not have
> to be working generically... for specific client OS would be
> sufficient)!!

You could try checking whether the hlt instruction (on x86) was executed
with interrupts disabled.


-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.

Re: [Qemu-devel] Detecting Client OS BSOF/Kernel Oops

[Flavien Lebarbe]

Hi,



Clemens Kolbitsch wrote :
>
> I'd like to detect if the client OS crashes... right now, only for 
> linux, but windows systems will become interesting for me as well in the 
> future...
> 

Real machines usually have hardware watchdogs for that. I do not know
if qemu has one available for your target but that's the way I would
go. Of course, you would have to configure the watchdog driver/daemon
in the OS, so OS support is important.

Flavien.

Re: [Qemu-devel] Detecting Client OS BSOF/Kernel Oops

[Mark Williamson]

> Clemens Kolbitsch wrote :
> > I'd like to detect if the client OS crashes... right now, only for
> > linux, but windows systems will become interesting for me as well in the
> > future...
>
> Real machines usually have hardware watchdogs for that. I do not know
> if qemu has one available for your target but that's the way I would
> go. Of course, you would have to configure the watchdog driver/daemon
> in the OS, so OS support is important.

Watchdog devices can be pretty simple - probably coming down to just a few IO 
ports.  A QEMU-based watchdog device ought to be fairly easy to implement, 
I'd imagine.  I've been thinking about doing this but haven't got round to 
tackling it yet.

Cheers,
Mark

-- 
Dave: Just a question. What use is a unicyle with no seat?  And no pedals!
Mark: To answer a question with a question: What use is a skateboard?
Dave: Skateboards have wheels.
Mark: My wheel has a wheel!

RE: [Qemu-devel] QEMU/PCI shutdown event

[Clemens Kolbitsch]

>>> hi everyone!
>>> i'm programming a pci-device that includes some threads &
>>> socket-connections (that allow remote debugging of my device).
>>>
>>> however, i want to cleanly shutdown all threads and sockets when qemu
>>> exits... is there an easy way of getting informed of a qemu shutdown?
>>>
>>> (something similar to pci_device_init...)
>>>
>>> thanks!!
>>>
>>>     
>>>       
>> You can use qemu_register_reset handler.
>> Note that it get's called when the guests exits but not if you just quit
>> the monitor.
>>   
>>     
> dear qemu-developers,
> i think it would be very helpful, if such a possibility exists.. maybe 
> you could consider implementing this in a future release :-)
>
> just a suggestion ;-)
>
> greets!
>   

sorry for this aweful post!! seems i forgot to delete half the message :-(