<feed xmlns='http://www.w3.org/2005/Atom'>
<title>src/sys/dev/mlx, branch stable/9</title>
<subtitle>FreeBSD source tree</subtitle>
<id>https://cgit-dev.freebsd.org/src/atom?h=stable%2F9</id>
<link rel='self' href='https://cgit-dev.freebsd.org/src/atom?h=stable%2F9'/>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/'/>
<updated>2015-04-21T11:29:07Z</updated>
<entry>
<title>MFC r280347: Remove MAXBSIZE use from drivers where it has nothing to do.</title>
<updated>2015-04-21T11:29:07Z</updated>
<author>
<name>Alexander Motin</name>
<email>mav@FreeBSD.org</email>
</author>
<published>2015-04-21T11:29:07Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=0bd48c2f5a092c5e62c4556cf2d527d2699a4bc0'/>
<id>urn:sha1:0bd48c2f5a092c5e62c4556cf2d527d2699a4bc0</id>
<content type='text'>
In some cases limits are just not needed, in others -- DFLTPHYS is the
right constant to use instead.
</content>
</entry>
<entry>
<title>Merge r254263:</title>
<updated>2013-08-13T22:05:50Z</updated>
<author>
<name>Scott Long</name>
<email>scottl@FreeBSD.org</email>
</author>
<published>2013-08-13T22:05:50Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=cffe159b0e61cee6bce082f4bd05a4f06a1d53a9'/>
<id>urn:sha1:cffe159b0e61cee6bce082f4bd05a4f06a1d53a9</id>
<content type='text'>
Update PCI drivers to no longer look at the MEMIO-enabled bit in the PCI
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.

Candidate for 9.2

Submitted by:	jhb
Reviewed by:	jfv, marius, adrian, achim
</content>
</entry>
<entry>
<title>MFC r238997:</title>
<updated>2012-08-20T18:01:17Z</updated>
<author>
<name>Xin LI</name>
<email>delphij@FreeBSD.org</email>
</author>
<published>2012-08-20T18:01:17Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=a420611b200d01b926a62412e8f01493b08c3cb6'/>
<id>urn:sha1:a420611b200d01b926a62412e8f01493b08c3cb6</id>
<content type='text'>
Correct a typo.

Reported by:	Sascha Wildner &lt;swildner dragonflybsd org&gt;
Reviewed by:	scottl
</content>
</entry>
<entry>
<title>MFC 232854,232874,232882,232883,232886 for bus_get_dma_tag()</title>
<updated>2012-03-16T08:46:58Z</updated>
<author>
<name>Scott Long</name>
<email>scottl@FreeBSD.org</email>
</author>
<published>2012-03-16T08:46:58Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=03f15131ec6a584935fd83d33e1a1dc1500c3880'/>
<id>urn:sha1:03f15131ec6a584935fd83d33e1a1dc1500c3880</id>
<content type='text'>
</content>
</entry>
<entry>
<title>MFC r226173, r227843, r227848 and r227908:</title>
<updated>2011-12-31T14:12:12Z</updated>
<author>
<name>Hans Petter Selasky</name>
<email>hselasky@FreeBSD.org</email>
</author>
<published>2011-12-31T14:12:12Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=0105e7b57ec82d3d157edb9f4322f29f05d54f6e'/>
<id>urn:sha1:0105e7b57ec82d3d157edb9f4322f29f05d54f6e</id>
<content type='text'>
Use DEVMETHOD_END to mark end of device methods.
Remove superfluous device methods.
Add some missing __FBSBID() macros.
</content>
</entry>
<entry>
<title>Temporarily revert the new-bus locking for 8.0 release.  It will be</title>
<updated>2009-08-20T19:17:53Z</updated>
<author>
<name>John Baldwin</name>
<email>jhb@FreeBSD.org</email>
</author>
<published>2009-08-20T19:17:53Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=a56fe095f0d5fb20fc70b784acb0cd2d367d3e79'/>
<id>urn:sha1:a56fe095f0d5fb20fc70b784acb0cd2d367d3e79</id>
<content type='text'>
reintroduced after HEAD is reopened for commits by re@.

Approved by:	re (kib), attilio
</content>
</entry>
<entry>
<title>Make the newbus subsystem Giant free by adding the new newbus sxlock.</title>
<updated>2009-08-02T14:28:40Z</updated>
<author>
<name>Attilio Rao</name>
<email>attilio@FreeBSD.org</email>
</author>
<published>2009-08-02T14:28:40Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=444b91868b5294e3a2151fffa3b063763a562448'/>
<id>urn:sha1:444b91868b5294e3a2151fffa3b063763a562448</id>
<content type='text'>
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 &lt;giovanni dot trematerra at gmail dot com&gt;,
                Brandon Gooch &lt;jamesbrandongooch at gmail dot com&gt;
Sponsored by:   Yahoo! Incorporated
Approved by:	re (ksmith)
</content>
</entry>
<entry>
<title>Separate the parallel scsi knowledge out of the core of the XPT, and</title>
<updated>2009-07-10T08:18:08Z</updated>
<author>
<name>Scott Long</name>
<email>scottl@FreeBSD.org</email>
</author>
<published>2009-07-10T08:18:08Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=52c9ce25d8339ad0228be8aaf0e44b45314b38dc'/>
<id>urn:sha1:52c9ce25d8339ad0228be8aaf0e44b45314b38dc</id>
<content type='text'>
modularize it so that new transports can be created.

Add a transport for SATA

Add a periph+protocol layer for ATA

Add a driver for AHCI-compliant hardware.

Add a maxio field to CAM so that drivers can advertise their max
I/O capability.  Modify various drivers so that they are insulated
from the value of MAXPHYS.

The new ATA/SATA code supports AHCI-compliant hardware, and will override
the classic ATA driver if it is loaded as a module at boot time or compiled
into the kernel.  The stack now support NCQ (tagged queueing) for increased
performance on modern SATA drives.  It also supports port multipliers.

ATA drives are accessed via 'ada' device nodes.  ATAPI drives are
accessed via 'cd' device nodes.  They can all be enumerated and manipulated
via camcontrol, just like SCSI drives.  SCSI commands are not translated to
their ATA equivalents; ATA native commands are used throughout the entire
stack, including camcontrol.  See the camcontrol manpage for further
details.  Testing this code may require that you update your fstab, and
possibly modify your BIOS to enable AHCI functionality, if available.

This code is very experimental at the moment.  The userland ABI/API has
changed, so applications will need to be recompiled.  It may change
further in the near future.  The 'ada' device name may also change as
more infrastructure is completed in this project.  The goal is to
eventually put all CAM busses and devices until newbus, allowing for
interesting topology and management options.

Few functional changes will be seen with existing SCSI/SAS/FC drivers,
though the userland ABI has still changed.  In the future, transports
specific modules for SAS and FC may appear in order to better support
the topologies and capabilities of these technologies.

The modularization of CAM and the addition of the ATA/SATA modules is
meant to break CAM out of the mold of being specific to SCSI, letting it
grow to be a framework for arbitrary transports and protocols.  It also
allows drivers to be written to support discrete hardware without
jeopardizing the stability of non-related hardware.  While only an AHCI
driver is provided now, a Silicon Image driver is also in the works.
Drivers for ICH1-4, ICH5-6, PIIX, classic IDE, and any other hardware
is possible and encouraged.  Help with new transports is also encouraged.

Submitted by:	scottl, mav
Approved by:	re
</content>
</entry>
<entry>
<title>Convert mlx(4) and mly(4) to si_drv1 instead of dev2unit().</title>
<updated>2009-04-18T07:36:38Z</updated>
<author>
<name>Ed Schouten</name>
<email>ed@FreeBSD.org</email>
</author>
<published>2009-04-18T07:36:38Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=e78a5a3f2f90c7fa01671cc0684ef1699d312300'/>
<id>urn:sha1:e78a5a3f2f90c7fa01671cc0684ef1699d312300</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Replace all calls to minor() with dev2unit().</title>
<updated>2008-09-27T08:51:18Z</updated>
<author>
<name>Ed Schouten</name>
<email>ed@FreeBSD.org</email>
</author>
<published>2008-09-27T08:51:18Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=6bfa9a2d66dd0e00182017d6741d44e54d0b2cca'/>
<id>urn:sha1:6bfa9a2d66dd0e00182017d6741d44e54d0b2cca</id>
<content type='text'>
After I removed all the unit2minor()/minor2unit() calls from the kernel
yesterday, I realised calling minor() everywhere is quite confusing.
Character devices now only have the ability to store a unit number, not
a minor number. Remove the confusion by using dev2unit() everywhere.

This commit could also be considered as a bug fix. A lot of drivers call
minor(), while they should actually be calling dev2unit(). In -CURRENT
this isn't a problem, but it turns out we never had any problem reports
related to that issue in the past. I suspect not many people connect
more than 256 pieces of the same hardware.

Reviewed by:	kib
</content>
</entry>
</feed>
