On Fri, Mar 24, 2023 at 09:56:55AM +0100, Claudio Jeker wrote: > On Thu, Mar 23, 2023 at 05:37:05PM -0500, Scott Cheloha wrote: > > On Sat, Mar 18, 2023 at 12:17:33PM -0600, Ted Bullock wrote: > > > On 2023-03-17 12:29 p.m., Mike Larkin wrote: > > > > On Thu, Mar 16, 2023 at 12:25:15PM -0500, Scott Cheloha wrote: > > > >> This code has been dead since we switched sparc64 to clockintr several > > > >> months ago. Nobody has come forward asking for a timer(4/sparc64) > > > >> intrclock. > > > >> > > > >> As of now, you need %TICK_CMPR or %STICK_CMPR to run OpenBSD on > > > >> sparc64. The only machines maybe lacking these registers are certain > > > >> early HAL/Fujitsu models like SPARC64 I and II, and maybe SPARC64 III. > > > >> > > > >> We can remove the driver now or wait until after unlock. > > > >> > > > >> The driver implementation is mixed into sparc64/clock.c. I think I > > > >> got everything, but I'm not positive. > > > > > > > > I would just wait until after unlock. ok mlarkin for removing dead code > > > > once unlock happens. > > > > > > Is that specific to Fujitsu variants of Sparc64 or will that hit Sun > > > variants too? I use the sunblade 100, which uses has a IIe I think but > > > this one is a sun branded chip as far as I'm aware. > > > > Your SunBlade 100 is unaffected by this change. > > > > All Sun/Oracle SPARC V9 CPUs ever shipped have ASR23 (%TICK_CMPR). > > Starting with the UltaSPARC IIe, they all also have the %STICK and > > %STICK_CMPR registers. > > > > The only machines that maybe don't have %TICK_CMPR, and are possibly > > already broken by changes I made months ago, are the first HAL CPUs: > > SPARC64 I and II. I can't be sure because I can't find documentation > > for those specific CPUs online. > > > > The HAL SPARC64 III and all later HAL/Fujitsu CPUs have ASR23 (dubbed > > %TICK_MATCH in the early HAL docs), so all those CPUs are unaffected, > > too. > > HAL SPARC64 I - III are currently not supported. The TLB and IIRC cache > handling is different.
Wonderful! Nothing to worry about then. Removing this driver impacts no supported CPUs.
