Hi Bryan, since nobody else answered, and even though i don't know that much about hardware support: I don't think your patch should be committed.
https://www.openbsd.org/socppc.html says: The OpenBSD/socppc port was discontinued after the 5.8 release. In that sense, the 6.1 release does not retire socppc. It was already gone before. Yours, Ingo Bryan Vyhmeister wrote on Mon, Mar 13, 2017 at 07:04:22PM -0700: > I am not sure what happened to the patch tj@ committed but it is not > there for 61.html. Perhaps it was clobbered by another commit or was > this not left in because socppc was essentially retired after 5.8 since > there was no 5.9 or 6.0 release? > > For reference: > > http://marc.info/?l=openbsd-cvs&m=148890947117155&w=2 > > http://marc.info/?l=openbsd-cvs&m=148899205909012&w=2 > > Bryan > > > > Index: 61.html > =================================================================== > RCS file: /cvs/www/61.html,v > retrieving revision 1.37 > diff -u -p -r1.37 61.html > --- 61.html 11 Mar 2017 16:33:30 -0000 1.37 > +++ 61.html 14 Mar 2017 01:54:24 -0000 > @@ -69,6 +69,7 @@ to 6.1. > <li>... > <li>The following platforms were retired: > <a href="https://www.openbsd.org/armish.html";>armish</a>, > + <a href="https://www.openbsd.org/socppc.html";>socppc</a>, > <a href="https://www.openbsd.org/sparc.html";>sparc</a>, > <a href="https://www.openbsd.org/zaurus.html";>zaurus</a> > <li>... >
