Date: Tue, 10 Jan 2017 10:04:36 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 205458] 11.0-CURRENT/10-STABLE powerpc64: a PowerMac G5 specific sys/powerpc/ofw/ofw_machdep.c change for reliable PowerMac G5 booting (with lots of RAM) Message-ID: <bug-205458-8-JMoD1OAEL2@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-205458-8@https.bugs.freebsd.org/bugzilla/> References: <bug-205458-8@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D205458 --- Comment #9 from Mark Millard <markmi@dsl-only.net> --- (In reply to Nathan Whitehorn from comment #4) There seems to have been no activity for this since comment #6 reported the patch failed on a PowerMac 7,3 . So it has been sitting in the In Progress state for about 4 months (2016-Sep-13 to 2017-Jan-10) as I write this. Comment 6 basically reports that some of the special purpose register(s) do need to be saved and restored, just not all of them. Nathan's patch had completely disabled ofw_sprg_prepare and its matching restore for __powerpc64__ . Unfortunately for now I've only access to a PowerMac 11,2 (a so-called "Quad Core" PowerMac G5) so for now I could only test the context that Nathan found to be working for his 2016-Sep patch. I should eventually have access to a PowerMac 7,2 form of G5 again. Still I wonder about 205458 showing "In Progress" for long periods. It might get lost with folks thinking it is being worked on when other higher priority things may have displaced its activity for a long time (even starting from now). However, closing the defect seems wrong as well. Going back to new would seem better. But as it shows to me such is not an option: closed is the only alternative to In Progress. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-205458-8-JMoD1OAEL2>