un.ifdef USB and PCI, since all our architectures (minus one) have models
which can have these busses, might as well make these distributable firmwares
available in case the drivers find devices.
ok kettenis

Retire OpenBSD/sgi.

OK deraadt@

Build firmware for usb devices on arm64.

ok patrick@

Retire zaurus, as it hasn't made the EABI jump and will be permanently broken
shortly when we use the hardware thread register in userland

armish handled some early-gen arm machines, which required tons of
workarounds. Some of them will soon stand in the way of armv7.
Off to the attic you go.

Build firmware for USB devices on octeon.

ok deraadt@

remove hppa64 port, which we never got going beyond broken single users.
hppa reverse-stack gives us a valuable test case, but most developers don't
have a 2nd one to proceed further with this.
ok kettenis

Build all the firmware for usb devices on armv7.

these will not be built for palm since it went away

Build these firmwares on loongson.

Palm: Integration into the tree

OK deraadt@

armish and zaurus too

firmware (if not store in a seeprom in the device) for the uticom(4)
this was compiled by someone from the full source code published by TI
under a surprisingly free license (which is probably not even actually
enforceable in any way, since they forgot to put the phrase Copyright
above it... where do they hire their lawyers?? anyways, everyone benefits)

Retire OpenBSD/sgi.

OK deraadt@

Build firmware for usb devices on arm64.

ok patrick@

Retire zaurus, as it hasn't made the EABI jump and will be permanently broken
shortly when we use the hardware thread register in userland

armish handled some early-gen arm machines, which required tons of
workarounds. Some of them will soon stand in the way of armv7.
Off to the attic you go.

Build firmware for USB devices on octeon.

ok deraadt@

remove hppa64 port, which we never got going beyond broken single users.
hppa reverse-stack gives us a valuable test case, but most developers don't
have a 2nd one to proceed further with this.
ok kettenis

Build all the firmware for usb devices on armv7.

these will not be built for palm since it went away

Build these firmwares on loongson.

Palm: Integration into the tree

OK deraadt@

armish and zaurus too

firmware (if not store in a seeprom in the device) for the uticom(4)
this was compiled by someone from the full source code published by TI
under a surprisingly free license (which is probably not even actually
enforceable in any way, since they forgot to put the phrase Copyright
above it... where do they hire their lawyers?? anyways, everyone benefits)

Build firmware for usb devices on arm64.

ok patrick@

Retire zaurus, as it hasn't made the EABI jump and will be permanently broken
shortly when we use the hardware thread register in userland

armish handled some early-gen arm machines, which required tons of
workarounds. Some of them will soon stand in the way of armv7.
Off to the attic you go.

Build firmware for USB devices on octeon.

ok deraadt@

remove hppa64 port, which we never got going beyond broken single users.
hppa reverse-stack gives us a valuable test case, but most developers don't
have a 2nd one to proceed further with this.
ok kettenis

Build all the firmware for usb devices on armv7.

these will not be built for palm since it went away

Build these firmwares on loongson.

Palm: Integration into the tree

OK deraadt@

armish and zaurus too

firmware (if not store in a seeprom in the device) for the uticom(4)
this was compiled by someone from the full source code published by TI
under a surprisingly free license (which is probably not even actually
enforceable in any way, since they forgot to put the phrase Copyright
above it... where do they hire their lawyers?? anyways, everyone benefits)