- 06 Sep, 2011 18 commits
-
-
Aaro Koskinen authored
Use a common init function for module and built-in driver. Signed-off-by:
Aaro Koskinen <aaro.koskinen@iki.fi> Signed-off-by:
Greg Kroah-Hartman <gregkh@suse.de>
-
Aaro Koskinen authored
Remove incorrect/misleading text from parameter descriptions. Signed-off-by:
-
Aaro Koskinen authored
Delete all references to mode "none". It should be handled like any other invalid mode. Signed-off-by:
-
Aaro Koskinen authored
According to the comment, the default mode should be 800x600x8 while the index points actually to 800x600x16. Change the comment and move the definition instead of changing the current behaviour. Signed-off-by:
-
Aaro Koskinen authored
The default mode is the same regardless of the display type, except for XG21/LCD which is determined dynamically. Signed-off-by:
-
Aaro Koskinen authored
Fail the probe if the LCD resolution described in card firmware does not match any of the supported modes. Signed-off-by:
-
Aaro Koskinen authored
The code for determining the default video mode is unnecessarily duplicated in XGIfb_search_mode() and XGIfb_search_vesamode() functions. Signed-off-by:
-
Aaro Koskinen authored
The same default video mode should be assumed regardless if the driver is a module or not. This won't change the current behaviour, but it will simplify further changes. Signed-off-by:
-
Aaro Koskinen authored
XGIfb_search_mode() is always called with a valid string pointer. Signed-off-by:
-
Aaro Koskinen authored
When searching the video mode, some HW details needs to be known. Therefore it's not possible to do that reliably before probe(). Signed-off-by:
-
Aaro Koskinen authored
If the driver fails to get LVDS LCD data from the firmware, it falls back to using driver's hardcoded values. However, this is done too early in the probe. The selected video mode index is not yet known, and also in some cases it could be defaulting to -1 resulting in a read outside the array. Fix this by moving the array lookup after the video mode validation. Signed-off-by:
Dan Carpenter <error27@gmail.com> Signed-off-by:
-
Aaro Koskinen authored
Check option values with kstrtoul(). This will also eliminate some checkpatch warnings about simple_strtoul() usage. Signed-off-by:
-
Aaro Koskinen authored
The global data is already initialized to zero. Signed-off-by:
-
Aaro Koskinen authored
Print options only if they are given. Delete other messages. Signed-off-by:
-
Aaro Koskinen authored
It's possible to disable the built-in xgifb driver with the kernel command line option: video=xgifb:off This is already handled by the generic framebuffer layer (fb_get_options() will return TRUE resulting in init failure), so no need to process the option in the driver. Signed-off-by:
-
Aaro Koskinen authored
Delete redundant branches for "mode" and "vesa" options. Signed-off-by:
-
Aaro Koskinen authored
Setting any of the FB options will disable ypan as a side effect. It should be disabled only by the "noypan" option. Signed-off-by:
-
Aaro Koskinen authored
Delete parameters which have no effect. Signed-off-by:
-
- 29 Aug, 2011 22 commits
-
-
Bill Pemberton authored
The serqt_usb2 driver will not work properly with the ssu100 device even though it claims to support it. The ssu100 is supported by the ssu100 driver in mainline so there is no need to have it claimed by serqt_usb2. Signed-off-by:
Bill Pemberton <wfp5p@virginia.edu> Cc: stable <stable@kernel.org> Signed-off-by:
-
Alexey Khoroshilov authored
In case if condition (kd != isdongle(peasycap)) becomes true, easycap_poll() returns without releasing easycapdc60_dongle[kd].mutex_video. The patch adds mutex_unlock() before that return. Found by Linux Driver Verification project (linuxtesting.org). Signed-off-by:
Alexey Khoroshilov <khoroshilov@ispras.ru> Acked-by:
Tomas Winkler <tomas.winkler@intel.com> Signed-off-by:
-
Mark Einon authored
Adding some basic ethtool ops and supporting functionality using a phy device. Signed-off-by:
Mark Einon <mark.einon@gmail.com> Signed-off-by:
-
Mark Einon authored
Manual setting of speed/duplex will be achieved using ethtool. Remove the driver specific module_param that also does this. Signed-off-by:
-
Mark Einon authored
A mechanism used to set the phy in loopback mode is not present in the driver, making associated checks and variables redundant. Removing them. Signed-off-by:
-
Mark Einon authored
xcvr_id holds the phy ID which is stored but never used in the driver. Signed-off-by:
-
Mark Einon authored
Adding myself as a maintainer for this driver, as I appear to have been the only interested party for some time. Not sure if Olaf Hartman is still interested? So will leave it up to him to add his name to the list. Signed-off-by:
-
Mark Einon authored
* Removed unused bool variable. * Eliminated mid-function returns, used gotos instead Signed-off-by:
-
Dan Carpenter authored
There was a typo here and we changed the -ENOMEM into +ENOMEM. The error codes aren't used, so this is just a cleanup. Signed-off-by:
-
K. Y. Srinivasan authored
Fix checkpatch errors and warnings. Signed-off-by:
K. Y. Srinivasan <kys@microsoft.com> Signed-off-by:
Haiyang Zhang <haiyangz@microsoft.com> Signed-off-by:
-
K. Y. Srinivasan authored
Fix checkpatch warnings in connection.c. Signed-off-by:
-
K. Y. Srinivasan authored
Fix a checkpatch warning in ring_buffer.c Signed-off-by:
-
K. Y. Srinivasan authored
Get rid of an unnecessary check in vmbus_connect(). Signed-off-by:
-
K. Y. Srinivasan authored
Get rid of some dated/redundant comments in vmbus_drv.c Signed-off-by:
-
K. Y. Srinivasan authored
Fixup indentation in vmbus_acpi_add(). Signed-off-by:
-
K. Y. Srinivasan authored
Linux interrupt handling code generates the eoi; don't enable auto eoi. Signed-off-by:
-
K. Y. Srinivasan authored
Get rid of vmbus_on_isr() by inlining the code. Signed-off-by:
-
K. Y. Srinivasan authored
The recent checkin that add a private pointer to hv_vmbus_device_id introduced this bug in vmbus_match; fix it. Signed-off-by:
-
K. Y. Srinivasan authored
Ensure that we correctly handle racing invocations of the channel callback when the channel is being closed. We do this using the channel's inbound_lock. A side-effect of this strategy is that we avoid repeatedly picking up this lock as we drain the inbound ring-buffer. Signed-off-by:
-
K. Y. Srinivasan authored
When we close a channel, we set the corresponding callback function to NULL. Check before invoking the channel callback. Signed-off-by:
-
K. Y. Srinivasan authored
The current code was adjusting guest time in interrupt context; do this in process context since we may have to initiate cross-processor interrupts as part of setting time. Signed-off-by:
-
K. Y. Srinivasan authored
When the host requests a "shutdown", make sure we shutdown! Signed-off-by:
-
