From: Alex Deucher <alexdeucher@gmail.com>
To: reimth@googlemail.com
Cc: Dave Airlie <airlied@redhat.com>,
Mario Kleiner <mario.kleiner@tuebingen.mpg.de>,
Jean Delvare <khali@linux-fr.org>,
Tyson Whitehead <twhitehead@gmail.com>,
Jason Wessel <jason.wessel@windriver.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
stable@kernel.org, Thomas Reim <rdratlos@yahoo.co.uk>
Subject: Re: [PATCH 3/3] drm/radeon: Log Subsystem Vendor and Device Information
Date: Thu, 7 Jul 2011 09:56:36 -0400 [thread overview]
Message-ID: <CADnq5_MnvwFWB5x0UYdkj0Upc5REK5dnQGj5K15yFH+_MbFTsg@mail.gmail.com> (raw)
In-Reply-To: <1309995012-5873-2-git-send-email-reimth@gmail.com>
On Wed, Jul 6, 2011 at 7:30 PM, <reimth@googlemail.com> wrote:
> From: Thomas Reim <rdratlos@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@yahoo.co.uk>
Reviewed-by: Alex Deucher <alexdeucher@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
>
>
next prev parent reply other threads:[~2011-07-07 13:56 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-21 15:31 [PATCH 1/1] drm/radeon: Fix Asus M2A-VM HDMI EDID error flooding problem Thomas Reim
2011-06-21 15:37 ` Alex Deucher
2011-06-21 18:03 ` Thomas Reim
2011-06-21 19:27 ` Jean Delvare
2011-06-22 1:11 ` Thomas Reim
2011-06-22 13:53 ` Jean Delvare
2011-06-22 1:20 ` reimth
2011-06-22 1:28 ` Alex Deucher
2011-06-22 15:17 ` Thomas Reim
2011-06-22 15:41 ` Alex Deucher
2011-06-22 15:45 ` Alex Deucher
2011-06-23 21:57 ` Thomas Reim
2011-06-23 22:05 ` [PATCH] " reimth
2011-06-23 22:55 ` Alex Deucher
2011-06-24 4:02 ` Thomas Reim
2011-06-24 13:36 ` Alex Deucher
2011-06-27 12:14 ` Jean Delvare
2011-07-06 9:35 ` Thomas Reim
2011-07-06 10:09 ` reimth
2011-07-06 12:26 ` Thomas Reim
2011-07-06 15:39 ` Alex Deucher
2011-07-06 15:42 ` Alex Deucher
2011-07-06 23:30 ` [PATCH 0/3] " reimth
2011-07-20 8:34 ` [PATCH] drm/radeon: Fix ECS A740GM-M DVI-D " reimth
2011-07-20 22:18 ` Thomas Reim
2011-07-26 13:05 ` Alex Deucher
2011-07-06 23:30 ` [PATCH 3/3] drm/radeon: Log Subsystem Vendor and Device Information reimth
2011-07-07 13:56 ` Alex Deucher [this message]
2011-07-06 23:30 ` [PATCH 2/3] drm/radeon: Fix Asus M2A-VM HDMI EDID error flooding problem reimth
2011-07-07 14:01 ` Alex Deucher
2011-07-26 13:20 ` Dave Airlie
2011-07-26 14:52 ` Alex Deucher
2011-07-26 14:55 ` Alex Deucher
2011-07-06 23:30 ` [PATCH 1/3] drm: Separate EDID Header Check from EDID Block Check reimth
2011-07-06 23:56 ` [stable] " Greg KH
2011-07-07 13:57 ` Alex Deucher
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADnq5_MnvwFWB5x0UYdkj0Upc5REK5dnQGj5K15yFH+_MbFTsg@mail.gmail.com \
--to=alexdeucher@gmail.com \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jason.wessel@windriver.com \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.kleiner@tuebingen.mpg.de \
--cc=rdratlos@yahoo.co.uk \
--cc=reimth@googlemail.com \
--cc=stable@kernel.org \
--cc=twhitehead@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).