search for: vmw_

Displaying 4 results from an estimated 4 matches for "vmw_".

Did you mean: vmi_
2015 Dec 02
2
[PATCH 3/6] Input: Update vmmouse.c to use the common VMW_PORT macros
...t; + unsigned long __dummy1 = 0, __dummy2 = 0; \ > > > > > > >> > > > > > > >> Why do we need to initialize dummies? > > > > > > > > > > > > > > Because for some commands those parameters to VMW_PORT() can be both > > > > > > > input and outout. > > > > > > > > > > > > The vmmouse commands do not use them as input though, so it seems we > > > > > > are simply wasting CPU cycles setting them to 0 just because we are...
2015 Dec 02
2
[PATCH 3/6] Input: Update vmmouse.c to use the common VMW_PORT macros
...t; + unsigned long __dummy1 = 0, __dummy2 = 0; \ > > > > > > >> > > > > > > >> Why do we need to initialize dummies? > > > > > > > > > > > > > > Because for some commands those parameters to VMW_PORT() can be both > > > > > > > input and outout. > > > > > > > > > > > > The vmmouse commands do not use them as input though, so it seems we > > > > > > are simply wasting CPU cycles setting them to 0 just because we are...
2015 Dec 02
4
[PATCH 3/6] Input: Update vmmouse.c to use the common VMW_PORT macros
...\ > > > > >> > + unsigned long __dummy1 = 0, __dummy2 = 0; \ > > > > >> > > > > >> Why do we need to initialize dummies? > > > > > > > > > > Because for some commands those parameters to VMW_PORT() can be both > > > > > input and outout. > > > > > > > > The vmmouse commands do not use them as input though, so it seems we > > > > are simply wasting CPU cycles setting them to 0 just because we are > > > > using the new VMW_PO...
2015 Dec 02
4
[PATCH 3/6] Input: Update vmmouse.c to use the common VMW_PORT macros
...\ > > > > >> > + unsigned long __dummy1 = 0, __dummy2 = 0; \ > > > > >> > > > > >> Why do we need to initialize dummies? > > > > > > > > > > Because for some commands those parameters to VMW_PORT() can be both > > > > > input and outout. > > > > > > > > The vmmouse commands do not use them as input though, so it seems we > > > > are simply wasting CPU cycles setting them to 0 just because we are > > > > using the new VMW_PO...