| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
with a physical address. This is used for hardware ARGB cursor support on newer
chipsets.
|
| |
|
|
|
|
|
| |
PR: kern/91315
Submitted by: Joerg Pulz <Joerg.Pulz@frm2.tum.de>
|
|
|
|
|
|
|
| |
capability is present as not all devices supported by the agp_i810 driver
(such as i915) have the AGP capability. Instead, add an identify routine
to the agp_i810 driver that uses the PCI ID to determine if it should
create an agp child device.
|
|
|
|
| |
Reported by: Coverity (via dfr's clue-bat)
|
|
|
|
|
| |
- Axe macros used for walking PCI capabilities list. We now ask the PCI
bus to find caps for us rather than doing it in the drm and agp drivers.
|
|
|
|
|
|
|
|
|
| |
the addition of pci_find_extcap().
- Change the drm drivers to attach to vgapci. This is #ifdef'd so the
code can be shared across branches.
- Use pci_find_extcap() to look for AGP and PCIE capabilities in drm.
- GC all the drmsub stuff for i810/i830/i915. The agp and drm devices are
now both children of vgapci.
|
|
|
|
|
|
|
|
|
| |
attach to the hostb driver instead. This means that agp can now be loaded
at runtime (in theory at least). Also, the drivers no longer have to
explicity call device_verbose() to cancel out any earlier calls to
device_quiet() by the hostb(4) driver (this shows a limitation in new-bus,
drivers really shouldn't be doing device_quiet() until they know they are
going to drive that device, i.e. in attach).
|
|
|
|
| |
attached to a driver rather than always returning agp0.
|
|
|
|
|
|
|
|
| |
drivers already map sections into KVA as needed anyway. Note that this
will probably break the nvidia driver, but I will coordinate to get that
fixed.
MFC after: 2 weeks
|
|
|
|
|
|
| |
rather than afterwards.
MFC after: 1 week
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
and some fixes from Motomichi Matsuzaki. Testing involved many people, but the
final, successful testing was from rwatson who endured several rounds of "it
crashes at XYZ stage" "oh, please correct this typo and try again." The Linux
driver, and to a small extent the limited specs, were both used as a reference
for how to program the chipset.
PR: kern/80396
Submitted by: Martin Mersberger
|
| |
|
|
|
|
|
| |
the bridge. Therefore, we give the same treatment as we did for nForce3-250
and ULi chipsets. VIA AGPv3 code was copied from agp_via.c.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
control register and AGP bridge seems to be inconsistent with some BIOS.
Instead of relying on BIOS settings, we just take the initial aperture size
and encode them for both miscellaneous control register and AGP bridge.
Some idea was borrowed from agp_nvidia.c.
- Add preliminary ULi M1689 chipset support. The idea was taken from Linux
because hardware and documentation are unavailable. Not tested.
- Add more VIA chipset PCI IDs taken from Linux driver.
Approved by: anholt (mentor)
Tested by: Adam Gregoire <ebola at psychoholics dot org>
Ganael Laplanche <ganael.laplanche at martymac dot com>
K Wieland <kwieland at wustl dot edu>
|
|
|
|
|
|
|
|
|
| |
the Linux driver, since specs are unavailable. Many thanks to Adam Kirchhoff
for multiple useful testing cycles, and Ralf Wostrack for the final fix to get
it working.
PR: i386/75251
Submitted by: anholt
|
|
|
|
|
|
|
|
|
|
|
|
| |
9200 according to one responder. The primary issue was not setting some bits
to say that the entries were active, but also fix one place where some memory
wasn't being used as volatile as it should. While here, change some use of ffs
to a relatively short case statement, to make it more obvious what's going on.
PR: kern/71638, kern/72372, kern/71547?
Submitted by: Andrew J. Caines <A.J.Caines@halplant.com>,
Robin Schoonover <end@endif.cjb.net>,
Jason Henson <jason@ec.rr.com>
|
|
|
|
|
|
|
| |
X startup with DRI enabled, with a v3-capable card.
Tested by: Tom McLaughlin <tmclaugh@sdf.lonestar.org>
Approved by: re (scottl)
|
| |
|
|
|
|
|
|
| |
So move the AGP support to there.
Submitted by: Jung-uk Kim <jkim@niksun.com>
|
| |
|
|
|
|
| |
Noticed by: bde
|
| |
|
|
|
|
|
|
| |
PR: kern/76411
Submitted by: Jonathan Fosburgh, jonathan at fosburgh dot org
Obtained from: Jung-uk Kim, jkim at niksun.com
|
|
|
|
| |
do fake "generic" support.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
generic bridge support was biting us more than it helped, whenever a new chipset
came out from a vendor and misprogramming it caused strange hangs or corruption.
[2] Add a large number of PCI IDs based on what the linux drivers support.
Note that the new PCI IDs haven't been tested, they're just *likely* to work.
In particular the VIA AGP 8x chipsets are concerning, due to lack of testing,
possible issues (kern/69953), and not having a nice "does this bridge say it
would do 8x" function. However, this shouldn't make the situation worse, since
these chips would have probed in the past anyway.
|
|
|
|
| |
synchronization that one entails.
|
|
|
|
|
|
| |
two loops in agp_generic_bind_memory(). As an intended side-effect, all
of the calls to vm_page_wakeup() are now performed with the containing
vm object lock held.
|
|
|
|
| |
enabled, but not 3D.
|
|
|
|
|
| |
PR: kern/69858
Submitted by: Jacobo Arvelo <unix4all at gulic dot org>
|
|
|
|
|
|
|
|
|
| |
to check aperture size, avoiding hangs. Maintain the rest of the bits when
setting/unsetting ATTBASE. This essentially matches Linux's AGP driver as well.
PR: kern/70037
Submitted by: Mark Tinguely <tinguely at casselton dot net>
Obtained from: NetBSD
|
|
|
|
| |
follow).
|
| |
|
|
|
|
|
|
|
| |
This also applies to AMD64 HW running 'i386' OS.
Submitted by: Jung-uk Kim <jkim@niksun.com>
Integration by: obrien
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
chipsets, based on Linux's via-agp.c. On boot, the system selects which AGP
version to use based on the inserted card. If v2 was chosen, the chipset
needs to be programmed with the v2 registers still. Also included in kern/69953
are changes to make the programming of the v3 registers match linux, but that
will be left out until the need to do so is confirmed (want specs or a tester).
PR: kern/69953
Submitted by: Oleg Sharoiko <os@rsu.ru>
Tested by: Oleg Sharoiko <os@rsu.ru>, Geoff Speicher <geoff@speicher.org>
(full version from PR)
|
|
|
|
|
|
|
| |
the VIA v3 register offsets.
PR: 68545
Submitted by: Ariff Abdullah <skywizard@mybsd.org.my>
|
|
|
|
| |
Bump __FreeBSD_version accordingly.
|
| |
|
| |
|
|
|
|
|
|
|
| |
the agp mutex. We do this because vm_page_grab() called with the
VM_ALLOC_RETRY flag can sleep.
Pointed out by: alc
|
|
|
|
|
| |
since it's always acquiring the lock exclusively. This was tested
with X on an SMP box, with and without WITNESS.
|
| |
|
|
|
|
| |
Prompted by: i386/59503
|
|
|
|
|
|
|
|
|
|
|
| |
registers, so add a register offset array to the softc. We key off the
device ID to determine which set of register offsets. Currently the 8385
host bridge used on amd64 is the only bridge to use the AGP3_VIA_*
register offsets and all other bridges use the AGP_VIA_* offsets. It is
currently unclear if the AGP3_VIA_* offsets are for VIA bridges that
implement AGP 3.0 bridges or just for amd64 bridges.
Submitted by: Kenneth Culver culverk at sweetdreamsracing dot biz
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
caller to vm_page_grab(). Although this gives VM_ALLOC_ZERO a
different meaning for vm_page_grab() than for vm_page_alloc(), I feel
such change is necessary to accomplish other goals. Specifically, I
want to make the PG_ZERO flag immutable between the time it is
allocated by vm_page_alloc() and freed by vm_page_free() or
vm_page_free_zero() to avoid locking overheads. Once we gave up on
the ability to automatically recognize a zeroed page upon entry to
vm_page_free(), the ability to mutate the PG_ZERO flag became useless.
Instead, I would like to say that "Once a page becomes valid, its
PG_ZERO flag must be ignored."
|
|
|
|
|
| |
PR: 64846
Submitted by: Samy Al Bahra
|
|
|
|
|
|
| |
hint.agp.0.disabled="1"
Submitted by: jhb
|