I just sent patches to fix it. Sorry my internet service has been out all day. I'm just catching up now. Alex From: Marek Olšák [mailto:maraeo@xxxxxxxxx] Sent: Monday, July 10, 2017 10:08 AM To: Deucher, Alexander Cc: Alex Deucher; amd-gfx mailing list Subject: Re: [PATCH 1/3] drm/amdgpu/atom: fix atom_fw check On Mon, Jul 10, 2017 at 3:49 PM, Deucher, Alexander <Alexander.Deucher at amd.com<mailto:Alexander.Deucher at amd.com>> wrote: > -----Original Message----- > From: Marek Olšák [mailto:maraeo at gmail.com<mailto:maraeo at gmail.com>] > Sent: Saturday, July 08, 2017 7:08 PM > To: Alex Deucher > Cc: amd-gfx mailing list; Deucher, Alexander > Subject: Re: [PATCH 1/3] drm/amdgpu/atom: fix atom_fw check > > Hi Alex, > > This commit causes that clock_crystal_freq is 0 on Raven, demoting > OpenGL support from 4.5 to 3.2. Can I revert? The problem is, it's just reading garbage right now. It would be better to just hardcode the reference clock until I can figure out where the reference clock is in atomfirmware. OK. I'll find a way to work around it in Mesa. Marek -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/amd-gfx/attachments/20170710/091666fc/attachment.html>
