On Sat, Dec 11, 2021 at 12:41:46PM +0100, Mark Kettenis wrote: > > Date: Fri, 10 Dec 2021 17:24:58 -0700 > > From: Ted Bullock <tbull...@comlore.com> > > > > On 2021-12-10 12:53 a.m., Jonathan Gray wrote: > > > On Thu, Dec 09, 2021 at 10:01:30PM -0700, Ted Bullock wrote: > > >> Thoughts folks? This is clearly going to impact all big endian + radeon > > >> gear. > > >> > > >> Actually, I bet that the macppc platform has the same problem too. > > > > > > sparc64 maps pci little endian, I don't think macppc does > > > > > > can you try the following? > > > > Yeah that did resolve the bios warning; X is yellow still though. > > So the real problem is: > > > [drm] *ERROR* radeon: ring test failed (scratch(0x15E4)=0xCAFEDEAD) > > [drm] *ERROR* radeon: cp isn't working (-22). > > drm:pid0:r100_startup *ERROR* failed initializing CP (-22). > > drm:pid0:r100_init *ERROR* Disabling GPU acceleration > > [drm] *ERROR* Wait for CP idle timeout, shutting down CP. > > Failed to wait GUI idle while programming pipes. Bad things might happen. > > as a result of this GPU acceleration is disabled and software > rendering is used. Which obviously has endian-ness issues. > > I believe the XVR-300 doesn't hit these errors and still (mostly) > works. But you can't plug one of those into a blade100. > > The sad truth is that most of us don't have much time to test older > hardware and we tend to favor making new hardware work correctly over > keeping the really old stuff working. But help is appreciated and we > certainly won't outright reject any fixes you discover.
I test on old r100 and i915 hardware but on i386 not sparc64. > > That said I think Jonathan said that support for the R100 is going to > be removed from Mesa, which would probably mean the end of GPU > acceleration support for that hardware. In Mesa git (and >= 22.0) the non-gallium 'classic' drivers are removed. https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10153 For radeon r100/r200 are removed. For intel i915 (gen 2-3), i965 (gen 4-7) For i965 there is a new replacement gallium driver (crocus) The proposed way of supporting older hardware is building the 'amber' branch based on 21.3 in addition to building a newer release, with the nvidia libglvnd acting as libGL calling different Mesa versions. I don't think we'd want to go that route. I have a Mesa 21.3 update in the works which still has the classic drivers but that is on hold for now as it expects the kernel drm to implement android sync file interfaces in at least the intel vulkan driver.
