garbled 17ca05a76f 1) Modify pnpbus attachment code to properly decode pnp memory range packets. ... 2) Modify pnpbus attachment code to record the chipid of the device if it has one. 3) Change the clock probes to use the chipid, rather than relying on potentially untrustworthy subtype and interface. 4) Add decoding of memory ranges to the RESIDUAL_DUMP code. 5) Add a we@pnpbus device to allow netbooting and root device detection from an IBM we ethernet. (it will only work if your firmware detects it) 6) Because I moved the pnpbus probe to occur prior to pci and isa, it screwed up the root device detection and firmware path building code. Completely rewrite the fw-path detection code to deal with this.		2006-06-23 03:08:41 +00:00
..
if_we_pnpbus.c	1) Modify pnpbus attachment code to properly decode pnp memory range packets.	2006-06-23 03:08:41 +00:00
mcclock_pnpbus.c	1) Modify pnpbus attachment code to properly decode pnp memory range packets.	2006-06-23 03:08:41 +00:00
mkclock_pnpbus.c	1) Modify pnpbus attachment code to properly decode pnp memory range packets.	2006-06-23 03:08:41 +00:00
nvram_pnpbus.c	A bit of clock rototill. It's safer to detect things known by the	2006-06-15 18:15:32 +00:00
pnpbus.c	1) Modify pnpbus attachment code to properly decode pnp memory range packets.	2006-06-23 03:08:41 +00:00
pnpbusvar.h	1) Modify pnpbus attachment code to properly decode pnp memory range packets.	2006-06-23 03:08:41 +00:00
wdc_pnpbus.c	A bit of clock rototill. It's safer to detect things known by the	2006-06-15 18:15:32 +00:00