src/sys/dev/pst, branch stable/10

Update PCI drivers to no longer look at the MEMIO-enabled bit in the PCI

2013-08-12T23:30:01+00:00

command register.  The lazy BAR allocation code in FreeBSD sometimes
disables this bit when it detects a range conflict, and will re-enable
it on demand when a driver allocates the BAR.  Thus, the bit is no longer
a reliable indication of capability, and should not be checked.  This
results in the elimination of a lot of code from drivers, and also gives
the opportunity to simplify a lot of drivers to use a helper API to set
the busmaster enable bit.

This changes fixes some recent reports of disk controllers and their
associated drives/enclosures disappearing during boot.

Submitted by:	jhb
Reviewed by:	jfv, marius, achadd, achim
MFC after:	1 day

Convert files to UTF-8

2012-01-15T13:23:18+00:00

Pass the arguments to mtx_init() in the correct order. There should be

2012-01-11T21:38:05+00:00

no change to the binary because the value of MTX_DEF is zero and there
is a visible function prototype.

MFC after:	1 week

Temporarily revert the new-bus locking for 8.0 release. It will be

2009-08-20T19:17:53+00:00

reintroduced after HEAD is reopened for commits by re@.

Approved by:	re (kib), attilio

Make the newbus subsystem Giant free by adding the new newbus sxlock.

2009-08-02T14:28:40+00:00

The newbus lock is responsible for protecting newbus internIal structures,
device states and devclass flags. It is necessary to hold it when all
such datas are accessed. For the other operations, softc locking should
ensure enough protection to avoid races.

Newbus lock is automatically held when virtual operations on the device
and bus are invoked when loading the driver or when the suspend/resume
take place. For other 'spourious' operations trying to access/modify
the newbus topology, newbus lock needs to be automatically acquired and
dropped.

For the moment Giant is also acquired in some key point (modules subsystem)
in order to avoid problems before the 8.0 release as module handlers could
make assumptions about it. This Giant locking should go just after
the release happens.

Please keep in mind that the public interface can be expanded in order
to provide more support, if there are really necessities at some point
and also some bugs could arise as long as the patch needs a bit of
further testing.

Bump __FreeBSD_version in order to reflect the newbus lock introduction.

Reviewed by:    ed, hps, jhb, imp, mav, scottl
No answer by:   ariff, thompsa, yongari
Tested by:      pho,
                G. Trematerra ,
                Brandon Gooch 
Sponsored by:   Yahoo! Incorporated
Approved by:	re (ksmith)

o break newbus api: add a new argument of type driver_filter_t to

2007-02-23T12:19:07+00:00

  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@

Use BUS_PROBE_DEFAULT for pci probe return value

2005-03-05T18:10:49+00:00

Use the correct type for iop_attach().

2004-10-03T16:06:46+00:00

Flush the queue of minor fixes to pst.

2004-09-15T15:39:28+00:00

Convert callers to the new bus_alloc_resource_any(9) API.

2004-03-17T17:50:55+00:00

Submitted by:	Mark Santcroos 
Reviewed by:	imp, dfr, bde