| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
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
|
|
|
|
|
|
|
| |
Add in missing case for i845G in the attach routine. I'll MFC this
with the rest of the change after the 4.10 codefreeze lifts.
Reviewed By: Doug Rabson
|
|
|
|
|
| |
Submitted by: Mark Santcroos <marks@ripe.net>
Reviewed by: imp, dfr, bde
|
|
|
|
|
|
|
|
|
|
|
|
| |
attach/detach time.
Assigning the default behaviour to this particular device is
incorrect, corrupting the video BIOS aperture, and breaking
VESA support in the kernel and XFree86.
Reviewed By: dfr
MFC after: 1 week
PR: kern/62906
|
|
|
|
|
|
|
|
| |
Introduce d_version field in struct cdevsw, this must always be
initialized to D_VERSION.
Flip sense of D_NOGIANT flag to D_NEEDGIANT, this involves removing
four D_NOGIANT flags and adding 145 D_NEEDGIANT flags.
|
|
|
|
|
|
|
| |
Free approx 86 major numbers with a mostly automatically generated patch.
A number of strategic drivers have been left behind by caution, and a few
because they still (ab)use their major number.
|
| |
|
|
|
|
|
|
|
|
|
| |
- Fail in agp_alloc_gatt if the aperture size is 0 instead of panicing in
contigmalloc.
Reported by: Bjoern Fischer <bfischer@Techfak.Uni-Bielefeld.DE>
Reviewed by: jhb
MFC after: 1 week
|
|
|
|
|
|
|
|
| |
part of the support is that it still assumes one master and one target
where as AGP 3.0 actually supports multiple devices on the bus.
Submitted by: Keith Whitwell <keith@tungstengraphics.com>
Sponsored by: The Weather Channel
|
|
|
|
|
|
| |
code to use to see if the onboard video has been disabled or not.
Submitted by: Keith Whitwell <keith@tungstengraphics.com>
|
|
|
|
|
|
| |
to by the DRM for i8xx devices.
Submitted by: Keith Whitwell <keith@tungstengraphics.com>
|
|
|
|
|
| |
PR: kern/56297
Submitted by: Dan Angelescu <mrhsaacdoh@yahoo.com>
|
| |
|
| |
|
|
|
|
|
| |
tree for two or more years now), except in a few places where there's
code to be compatible with older versions of FreeBSD.
|
| |
|
|
|
|
|
| |
PR: kern/46983
Submitted by: David Holm <david@realityrift.com>
|
|
|
|
|
| |
PR: i386/53136, i386/51802
Submitted by: Kyunghwan Kim <redjade@atropos.snu.ac.kr>, Norikatsu Shigemura <nork@FreeBSD.org>
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
865. The APSIZE register has a variable-sized field of enabled bits.
To figure out how many bits a specific host bridge supports, write the
maximum width and see how many bits are set in the hardware. We then
use this mask for setting and getting the aperture size. Prior to this,
the agp(4) driver would treat an aperture size of 256 MB as 128 MB and
would not allocate enough physical memory for the GART as a result.
MFC after: 3 days
Sponsored by: The Weather Channel
Approved by: re (rwatson)
|
|
|
|
|
|
|
|
| |
commits.
Reported by: Lukas Ertl <l.ertl@univie.ac.at>
With hat: re
Pointy hat to: jhb
|