"bd295e68" (history) in projects: freebsd

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched hist:bd295e68 (Results 1 – 1 of 1) sorted by relevance

/freebsd/sys/dev/my/
H A D	if_my.c	bd295e68 Wed Aug 10 20:21:29 GMT 2005 John Baldwin <jhb@FreeBSD.org> - Remove pre-new-bus code under #if 0 and some other rotted code under #if 0. - Use pci_enable_busmaster() to enable busmastering instead of frobbing the command register directly. - Don't check to see if memory or I/O can be enabled by writing to the command register. The PCI bus driver's bus_alloc_resource() method already checks this and will fail if it can't enable the bit. bd295e68 Wed Aug 10 20:21:29 GMT 2005 John Baldwin <jhb@FreeBSD.org> - Remove pre-new-bus code under #if 0 and some other rotted code under #if 0. - Use pci_enable_busmaster() to enable busmastering instead of frobbing the command register directly. - Don't check to see if memory or I/O can be enabled by writing to the command register. The PCI bus driver's bus_alloc_resource() method already checks this and will fail if it can't enable the bit. bd295e68 Wed Aug 10 20:21:29 GMT 2005 John Baldwin <jhb@FreeBSD.org> - Remove pre-new-bus code under #if 0 and some other rotted code under #if 0. - Use pci_enable_busmaster() to enable busmastering instead of frobbing the command register directly. - Don't check to see if memory or I/O can be enabled by writing to the command register. The PCI bus driver's bus_alloc_resource() method already checks this and will fail if it can't enable the bit. bd295e68 Wed Aug 10 20:21:29 GMT 2005 John Baldwin <jhb@FreeBSD.org> - Remove pre-new-bus code under #if 0 and some other rotted code under #if 0. - Use pci_enable_busmaster() to enable busmastering instead of frobbing the command register directly. - Don't check to see if memory or I/O can be enabled by writing to the command register. The PCI bus driver's bus_alloc_resource() method already checks this and will fail if it can't enable the bit. bd295e68 Wed Aug 10 20:21:29 GMT 2005 John Baldwin <jhb@FreeBSD.org> - Remove pre-new-bus code under #if 0 and some other rotted code under #if 0. - Use pci_enable_busmaster() to enable busmastering instead of frobbing the command register directly. - Don't check to see if memory or I/O can be enabled by writing to the command register. The PCI bus driver's bus_alloc_resource() method already checks this and will fail if it can't enable the bit. bd295e68 Wed Aug 10 20:21:29 GMT 2005 John Baldwin <jhb@FreeBSD.org> - Remove pre-new-bus code under #if 0 and some other rotted code under #if 0. - Use pci_enable_busmaster() to enable busmastering instead of frobbing the command register directly. - Don't check to see if memory or I/O can be enabled by writing to the command register. The PCI bus driver's bus_alloc_resource() method already checks this and will fail if it can't enable the bit. bd295e68 Wed Aug 10 20:21:29 GMT 2005 John Baldwin <jhb@FreeBSD.org> - Remove pre-new-bus code under #if 0 and some other rotted code under #if 0. - Use pci_enable_busmaster() to enable busmastering instead of frobbing the command register directly. - Don't check to see if memory or I/O can be enabled by writing to the command register. The PCI bus driver's bus_alloc_resource() method already checks this and will fail if it can't enable the bit. bd295e68 Wed Aug 10 20:21:29 GMT 2005 John Baldwin <jhb@FreeBSD.org> - Remove pre-new-bus code under #if 0 and some other rotted code under #if 0. - Use pci_enable_busmaster() to enable busmastering instead of frobbing the command register directly. - Don't check to see if memory or I/O can be enabled by writing to the command register. The PCI bus driver's bus_alloc_resource() method already checks this and will fail if it can't enable the bit.