src-test2/sys/dev/puc, branch release/6.0.0_cvs

This commit was manufactured by cvs2svn to create tag

2005-11-03T00:35:26Z

'RELENG_6_0_0_RELEASE'. This commit was manufactured to restore the state of the 6.0-RELEASE image.

Account for ebus(4) defaulting to SYS_RES_MEMORY for memory resources

2005-06-04T20:29:28Z

since ebus.c rev. 1.22.

Sort Oxford Semi entires. Add entry for OXCB950, a PCI/CardBus

2005-04-22T07:49:35Z

16C950. Adding it here doesn't unlock any of the cool 16C950 features (like the 128 byte fifo, the different prescalor, etc), but it does seem to get it working for me in light testing. Card Provided by: Ihsan Dogan

Use BUS_PROBE_DEFAULT for pci probe return value

2005-03-05T18:10:49Z

- sparc64/fhc/fhc.c:

2005-03-04T22:23:21Z

Change fhc(4) to use IRQ numbers instead of RIDs for allocating the IRQs of children. This works similar to e.g. sbus(4), i.e. add the IRQ resources as fully specified to the resource lists of the children, allocate them like normal. When establishing the interrupt search the interrupt maps of the children for a matching INO to determine which map we need to write the fully specified interrupt number to and to enable the mapping (before the RID was used to indicate which interrupt map to use). - dev/puc/puc.c: Revert rev. 1.38, with the above change fhc(4) no longer needs special treatment for allocating IRQs. Thanks to: joerg for providing access to an E3500

Declare the sbus(4) front-end of puc(4) also for fhc(4), allowing

2005-02-26T00:25:43Z

uart(4) to support the Zilog 8530 SCCs which hang off of a FireHose bus on Sun E4000/E5000 class machines. Beside the fact that a puc_fhc.c would just be a copy of puc_sbus.c with s,sbus,fhc,g the reason why the declaration for fhc(4) was sticked into puc_sbus.c is that both of these front-ends for puc(4) will go away once there is a scc(4). Discussed with: marcel Tested by: hrs, kris MFC after: 3 days

Add a stopgap allowing puc(4) to allocate IRQs on fhc(4). Given that

2005-02-26T00:22:52Z

both a scc(4) is under way and fhc(4) will be change to use INOs this shouldn't stay in HEAD for too long but we need a MFC-able solution for FreeBSD 5.4. Discussed with: marcel Tested by: hrs, kris MFC after: 3 days

Remove duplicate FBSDID.

2005-02-26T00:21:25Z

fail gracefully rather than using an invalid array index if unable

2005-02-25T19:47:18Z

to allocate a bar; it's unclear whether this can happen in practice Noticed by: Coverity Prevent analysis tool Discussed with: marcel

add support for NetMos NM9805 1284 Printer port

2005-02-09T18:38:28Z

Submitted by: Willy Offermans MFC after: 2 weeks