Juli Mallett 9a264080b5 Remove OCTEON1-32. Since moving to the Cavium SDK, we've lost our support for ... running an o32 kernel safely, and would have to add interrupt disabling and reenabling to a bunch of macros in the Simple Executive sources to support it. The only reason one would run an o32 kernel on Octeon would be to run o32 world, which is better worked towards by adding o32 binary compatibility to n64 kernels along with, eventually, supporting multilib systems so o32 binaries can run alongside n32 and n64 ones. Discussed with: imp		2011-01-04 19:09:05 +00:00
..
adm5120	- dump_avail layout should be sequence of [start, end)	2010-12-09 07:47:40 +00:00
alchemy	- dump_avail layout should be sequence of [start, end)	2010-12-09 07:47:40 +00:00
atheros	- Populate dump_avail with proper values from phys_avail	2010-12-09 07:01:03 +00:00
cavium	o) Add MIPS_COP_0_EXC_PC accessors to <machine/cpufunc.h>.	2011-01-04 02:33:48 +00:00
compile
conf	Remove OCTEON1-32. Since moving to the Cavium SDK, we've lost our support for	2011-01-04 19:09:05 +00:00
idt	- dump_avail layout should be sequence of [start, end)	2010-12-09 07:47:40 +00:00
include	o) Add MIPS_COP_0_EXC_PC accessors to <machine/cpufunc.h>.	2011-01-04 02:33:48 +00:00
malta	- dump_avail layout should be sequence of [start, end)	2010-12-09 07:47:40 +00:00
mips	o) When trying to determine whether the pcpu pointer is a managed address, check	2011-01-01 00:20:14 +00:00
rmi	Updates for I2C devices on XLR engg boards.	2010-12-13 17:53:38 +00:00
sentry5	- dump_avail layout should be sequence of [start, end)	2010-12-09 07:47:40 +00:00
sibyte	- dump_avail layout should be sequence of [start, end)	2010-12-09 07:47:40 +00:00