src/sys/dev/eisa, branch release/4.1.0

Pre 4.0 tidy up.

2000-01-14T07:14:17Z

Collect together the components of several drivers and export eisa from the i386-only area (It's not, it's on some alphas too). The code hasn't been updated to work on the Alpha yet, but that can come later. Repository copies were done a while ago. Moving these now keeps them in consistant place across the 4.x series as the newbusification progresses. Submitted by: mdodd

Remove the 'ivars' arguement to device_add_child() and

1999-12-03T08:41:24Z

device_add_child_ordered(). 'ivars' may now be set using the device_set_ivars() function. This makes it easier for us to change how arbitrary data structures are associated with a device_t. Eventually we won't be modifying device_t to add additional pointers for ivars, softc data etc. Despite my best efforts I've probably forgotten something so let me know if this breaks anything. I've been running with this change for months and its been quite involved actually isolating all the changes from the rest of the local changes in my tree. Reviewed by: peter, dfr

Delete unneeded #include

1999-10-11T14:42:33Z

Submitted by: phk

$Id$ -> $FreeBSD$

1999-08-28T01:08:13Z

I'm not sure how this wasn't in the last commit but anyhow...

1999-08-02T20:01:40Z

'int irq' -> 'struct irq_node *irq'

Move the specification of EDGE/LEVEL triggered interrupts to

1999-08-01T22:57:09Z

eisa_add_intr() which now takes an additional arguement (one of EISA_TRIGGER_LEVEL or EISA_TRIGGER_EDGE). The flag RR_SHAREABLE has no effect when passed to bus_alloc_resource(dev, SYS_RES_IRQ, ...) in an EISA device context as the eisa_alloc_resource() call (bus_alloc_resource method) now deals with this flag directly, depending on the device ivars. This change does nothing more than move all the 'shared = inb(foo + iobsse)' nonesense to the device probe methods rather than the device attach. Also, print out 'edge' or 'level' in the IRQ announcement message. Reviewed by: dfr

Restore the pre-new_bus behavior of printing out the reserved resources

1999-07-30T13:54:00Z

during device announcement. (irq, ioport, maddr) Reviewed by: dfr, peter

Alter the behavior of sys/kern/subr_bus.c:device_print_child()

1999-07-29T01:03:04Z

- device_print_child() either lets the BUS_PRINT_CHILD method produce the entire device announcement message or it prints "foo0: not found\n" Alter sys/kern/subr_bus.c:bus_generic_print_child() to take on the previous behavior of device_print_child() (printing the "foo0: " bit of the announce message.) Provide bus_print_child_header() and bus_print_child_footer() to actually print the output for bus_generic_print_child(). These functions should be used whenever possible (unless you can just use bus_generic_print_child()) The BUS_PRINT_CHILD method now returns int instead of void. Modify everything else that defines or uses a BUS_PRINT_CHILD method to comply with the above changes. - Devices are 'on' a bus, not 'at' it. - If a custom BUS_PRINT_CHILD method does the same thing as bus_generic_print_child(), use bus_generic_print_child() - Use device_get_nameunit() instead of both device_get_name() and device_get_unit() - All BUS_PRINT_CHILD methods return the number of characters output. Reviewed by: dfr, peter

Add a hook for a bus to detect child devices which didn't find drivers.

1999-07-11T13:42:37Z

This allows the bus to print an informative message about unknown devices. Submitted by: Matthew N. Dodd

Handle suspend/resume methods

1999-06-22T09:44:00Z

Obtained from: Warner Losh