On 10.11.2009, at 16:14, Scott Tsai wrote:
+ s->temperature++;
You're going to overheat very quickly.
Apart from making the driver work, is this actually useful?
I wanted the temperature to change with time to give a sense of
"something is happening" ^_^
The main user I had in mind was someone new to USB and Linux driver
development
following gregkh's driver tutorial:
http://www.kroah.com/linux/talks/ols_2005_driver_tutorial/
My thinking was that if the temperature never changes, all the USB
packets generated in the 'read_int_callback"
part of the driver would seem like a waste of effort.
How about having a monitor command to change the temperature,
leveraging a "common interface"?
That way in the future real host temperature measurements could maybe
get forwarded there too. At least for battery I've had several people
ask already if it's possible to read the host battery status (incl. AC
status) from inside the VM.
Alex
