Re: How are the DC patches tested?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Dear Daniel,


Am 09.05.22 um 17:21 schrieb Wheeler, Daniel:

I've made some edits to my cover letter to hopefully make it clearer
with what is being done.
Thank you.
		Hi all,
This week this patchset was tested on the following systems: HP Envy 360, with Ryzen 5 4500U
		Lenovo Thinkpad T14s Gen2, with AMD Ryzen 5 5650U
		Sapphire Pulse RX5700XT
		Reference AMD RX6800
		Engineering board with Ryzen 9 5900H

		These systems were tested on the following display types:
		eDP, (1080p 60hz [4500U, 5650U, 5900H])
		VGA and DVI (1680x1050 60HZ [DP to VGA/DVI, USB-C to DVI/VGA])
		DP/HDMI/USB-C (1440p 170hz, 4k 60hz, 4k 144hz [Includes USB-C to DP/HDMI adapters])

		MST tested with Startech MST14DP123DP and 2x 4k 60Hz displays
		DSC tested with Cable Matters 101075 (DP to 3x DP), and 201375 (USB-C to 3x DP) with 3x 4k60 displays
The testing is a mix of automated and manual tests. Manual testing includes (but is not limited to):
		Changing display configurations and settings
		Benchmark testing
		Feature testing (Freesync, etc.)

		Automated testing includes (but is not limited to):
		Script testing (scripts to automate some of the manual checks)
		IGT testing

		The patchset consists of the most recent amd-staging-drm-next branch with a selection of patches added on top of it. This goes for both Ubuntu testing and Chrome 	OS testing.

Please mention the commit hash of the commit at the top of amd-staging-drm-next.


		Tested on Ubuntu 22.04 and Chrome OS

I still do not see the Chrome OS version and devices listed. I think, that information would be valuable.

Tested-by: Daniel Wheeler <daniel.wheeler@xxxxxxx>

Kind regards,

Paul



[Index of Archives]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux