On Wed, Jul 6, 2011 at 7:30 PM,  <reimth at googlemail.com> wrote:
> From: Thomas Reim <rdratlos at yahoo.co.uk>
>
> ? ?Log PCI subsystem vendor and subsystem device ID in addition to
> ? ?PCI vendor and device ID during kernel mode initialisation. This helps
> ? ?to better identify radeon devices of third-party vendors, e. g. for
> ? ?bug analysis.
>
> ? ?Tested for kernel 2.35, 2.38 and 3.0 on Asus M2A-VM HDMI board
>
> Signed-off-by: Thomas Reim <rdratlos at yahoo.co.uk>

Reviewed-by: Alex Deucher <alexdeucher at gmail.com>

> ---
> ?drivers/gpu/drm/radeon/radeon_device.c | ? ?5 +++--
> ?1 files changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/radeon/radeon_device.c 
> b/drivers/gpu/drm/radeon/radeon_device.c
> index 7cfaa7e..440e6ec 100644
> --- a/drivers/gpu/drm/radeon/radeon_device.c
> +++ b/drivers/gpu/drm/radeon/radeon_device.c
> @@ -704,8 +704,9 @@ int radeon_device_init(struct radeon_device *rdev,
> ? ? ? ?rdev->gpu_lockup = false;
> ? ? ? ?rdev->accel_working = false;
>
> - ? ? ? DRM_INFO("initializing kernel modesetting (%s 0x%04X:0x%04X).\n",
> - ? ? ? ? ? ? ? radeon_family_name[rdev->family], pdev->vendor, pdev->device);
> + ? ? ? DRM_INFO("initializing kernel modesetting (%s 0x%04X:0x%04X 
> 0x%04X:0x%04X).\n",
> + ? ? ? ? ? ? ? radeon_family_name[rdev->family], pdev->vendor, pdev->device,
> + ? ? ? ? ? ? ? pdev->subsystem_vendor, pdev->subsystem_device);
>
> ? ? ? ?/* mutex initialization are all done here so we
> ? ? ? ? * can recall function without having locking issues */
> --
> 1.7.1
>
>

Reply via email to