FreeBSD source tree https://cgit-dev.freebsd.org/src-test2/atom?h=release%2F8.0.0_cvs 2009-11-21T06:13:29Z 2009-11-21T06:13:29Z Ken Smith kensmith@FreeBSD.org 2009-11-21T06:13:29Z urn:sha1:a4d3b78df842614c46b116fc5a6f470be637dccd Approved by: re (implicit) This commit was manufactured to restore the state of the 8.0-RELEASE image. 2008-08-05T17:39:37Z John Baldwin jhb@FreeBSD.org 2008-08-05T17:39:37Z urn:sha1:9e58d59f4166a9fad46bb4587bf4807c8a7f2e93 of having duplicate versions in each bus attachment. - Add a DRIVER_MODULE() instance so that the iicbus(4) driver will actually attach to pcf(4) driver instances. - Fix compile of envctrl.c. Pointy hat: jhb (3) 2008-08-04T20:46:15Z John Baldwin jhb@FreeBSD.org 2008-08-04T20:46:15Z urn:sha1:13e3657b7b30a7605e51c19d8341b2fbbf1bdfee - Just grab Giant in the ixp425_iic(4) driver since this driver uses a shared address/data register window pair to access the actual I2C registers. None of the other ixp425 drivers lock access to these shared address/data registers yet and that would need to be done before this could use any meaningful locking. - Add locking to the interrupt handler and 'iicbus_reset' methods of the at91_twi(4) driver. - Add locking to the pcf(4) driver. Other pcf(4) fixes include: - Don't needlessly zero the softc. - Use bus_foo rather than bus_space_foo and remove bus space tag and handle from softc. - The lpbb(4) driver just grabs Giant for now. This will be refined later when ppbus(4) is locked. - As was done with smbus earlier, move the DRIVER_MODULE() lines to match the bus driver (either iicbus or iicbb) to the bridge driver into the bridge drivers. Tested by: sam (arm/ixp425) 2007-03-21T03:38:37Z Yoshihiro Takahashi nyan@FreeBSD.org 2007-03-21T03:38:37Z urn:sha1:41f5bd0f6dc8a92fde5135b6c674e35d4b96501e bus_release_resource(). This is needed for pc98 by upcoming nexus related change. 2007-02-23T12:19:07Z Paolo Pisati piso@FreeBSD.org 2007-02-23T12:19:07Z urn:sha1:ef544f631226436ef590825881e7a28369df82f6 bus_setup_intr() o add an int return code to all fast handlers o retire INTR_FAST/IH_FAST For more info: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=465712+0+current/freebsd-current Reviewed by: many Approved by: re@ 2006-02-22T18:16:26Z John Baldwin jhb@FreeBSD.org 2006-02-22T18:16:26Z urn:sha1:57fb5e60974fbb2770aa12b4a72114660228c236 interrupt handlers rather than BUS_SETUP_INTR() and BUS_TEARDOWN_INTR(). Uses of the BUS_*() versions in the implementation of foo_intr methods in bus drivers were not changed. Mostly this just means that some drivers might start printing diagnostic messages like [FAST] when appropriate as well as honoring mpsafenet=0. - Fix two more of the ppbus drivers' identify routines to function correctly in the mythical case of a machine with more than one ppbus. 2005-06-04T20:29:28Z Marius Strobl marius@FreeBSD.org 2005-06-04T20:29:28Z urn:sha1:fcff6919708c873df54baa527935a8ace0883c7a since ebus.c rev. 1.22. 2004-08-12T17:41:33Z Marius Strobl marius@FreeBSD.org 2004-08-12T17:41:33Z urn:sha1:26280d88d76716790cf28f23fdb0bda56533e9b6 subset ("compatible", "device_type", "model" and "name") of the standard properties in drivers for devices on Open Firmware supported busses. The standard properties "reg", "interrupts" und "address" are not covered by this interface because they are only of interest in the respective bridge code. There's a remaining standard property "status" which is unclear how to support properly but which also isn't used in FreeBSD at present. This ofw_bus kobj-interface allows to replace the various (ebus_get_node(), ofw_pci_get_node(), etc.) and partially inconsistent (central_get_type() vs. sbus_get_device_type(), etc.) existing IVAR ones with a common one. This in turn allows to simplify and remove code-duplication in drivers for devices that can hang off of more than one OFW supported bus. - Convert the sparc64 Central, EBus, FHC, PCI and SBus bus drivers and the drivers for their children to use the ofw_bus kobj-interface. The IVAR- interfaces of the Central, EBus and FHC are entirely replaced by this. The PCI bus driver used its own kobj-interface and now also uses the ofw_bus one. The IVARs special to the SBus, e.g. for retrieving the burst size, remain. Beware: this causes an ABI-breakage for modules of drivers which used the IVAR-interfaces, i.e. esp(4), hme(4), isp(4) and uart(4), which need to be recompiled. The style-inconsistencies introduced in some of the bus drivers will be fixed by tmm@ in a generic clean-up of the respective drivers later (he requested to add the changes in the "new" style). - Convert the powerpc MacIO bus driver and the drivers for its children to use the ofw_bus kobj-interface. This invloves removing the IVARs related to the "reg" property which were unused and a leftover from the NetBSD origini of the code. There's no ABI-breakage caused by this because none of these driver are currently built as modules. There are other powerpc bus drivers which can be converted to the ofw_bus kobj-interface, e.g. the PCI bus driver, which should be done together with converting powerpc to use the OFW PCI code from sparc64. - Make the SBus and FHC front-end of zs(4) and the sparc64 eeprom(4) take advantage of the ofw_bus kobj-interface and simplify them a bit. Reviewed by: grehan, tmm Approved by: re (scottl) Discussed with: tmm Tested with: Sun AX1105, AXe, Ultra 2, Ultra 60; PPC cross-build on i386 2004-08-11T21:19:31Z Marius Strobl marius@FreeBSD.org 2004-08-11T21:19:31Z urn:sha1:490a46bf68d240953b091232c755ed5526e931b9 Sun AXe board. 2004-06-10T21:53:04Z Marius Strobl marius@FreeBSD.org 2004-06-10T21:53:04Z urn:sha1:a9f012c75d5e7ce18cb7245baa5be731cdb29bac - Use "envctrl" as the name when registering this module rather than "pcf"; we can't have "pcf" as the name for all pcf(4) front-ends or we would get conflicts. OK'ed by: joerg