- Apr 27, 2012
-
-
Alan Cox authored
Signed-off-by:
Alan Cox <alan@linux.intel.com> Signed-off-by:
Dave Airlie <airlied@redhat.com>
-
Alan Cox authored
The problem in console mode is lack of linear memory. We can solve that by dropping to 16bpp. The mode setting X server will allocate its own GEM framebuffer in 32bpp and all will be well. We could just do 16bpp anyway but that would be a regression on the lower modes as many distributions don't yet ship the generic mode setting KMS drivers. Signed-off-by:
-
Alan Cox authored
Introduce a panel presence check for Cedartrail. Non netbook devices don't necessarily have a panel attached. Signed-off-by:
-
Alan Cox authored
Pull in various i915 bits that we will need to begin tackling the LVDS detect and ACPI events. We try and drift towards the i915 version of the code with the long term goal that at least some of it can one day be unified. Signed-off-by:
-
Alan Cox authored
We don't want them uncached, combining will do nicely and fixes the performance problem with the generic modesetting X server. Signed-off-by:
-
Alan Cox authored
Signed-off-by: -
Alan Cox authored
We need to pull more stuff from the VBT in order to configure the clocking correctly in all cases. Add the relevant bits from the other CDV driver work. Signed-off-by:
-
Alan Cox authored
This was reported a long time ago (and I apologize to whoever it was that reported it as I've lost the original report). Signed-off-by:
-
Ian Pilcher authored
EDID vendor IDs are always 3 characters long (4 with the terminating 0). It doesn't make any sense to have a (possibly 8-byte) pointer to the ID string in the quirk structure. Signed-off-by:
Ian Pilcher <arequipeno@gmail.com> Reviewed-by:
Adam Jackson <ajax@redhat.com> Signed-off-by:
-
Adam Jackson authored
Requiring the first byte of the EDID base block header to be 0 means we don't fix up as many transfer errors as we could. Instead have the callers specify whether it's meant to be block 0 or not, and conditionally run header fixup based on that. Bugzilla: https://bugzilla.redhat.com/812890 Signed-off-by:
Alex Deucher <alexdeucher@gmail.com> Reviewed-by:
Chris Wilson <chris@chris-wilson.co.uk> Signed-off-by:
-
- Apr 24, 2012
-
-
Matthew Garrett authored
This fixes the build breakage reported by Stephen in -next when merging the drm-next tree. Signed-off-by: -
Ville Syrjälä authored
The error handling code w.r.t. idr usage looks inconsistent. In the case of drm_mode_object_get() and drm_ctxbitmap_next() the error handling is also incomplete. Unify the code to follow the same pattern always. Signed-off-by:
Ville Syrjälä <ville.syrjala@linux.intel.com> Signed-off-by:
-
Dave Airlie authored
Since Matthew's changes we have to select arbitration. Reported-by: devh on #radeon Signed-off-by: -
Matthew Garrett authored
EFI doesn't typically make use of the legacy VGA ROM, but it may still be configured to pass that through to a given video device. This may lead to an inaccurate choice of default video device. Add support to efifb to pick out the correct active video device. v2: fix if->ifdef Signed-off-by:
Matthew Garrett <mjg@redhat.com> Acked-by:
<hpa@zytor.com> Cc: matt.fleming@intel.com Signed-off-by:
-
Matthew Garrett authored
IORESOURCE_ROM_SHADOW is not necessarily an indication that the hardware is the primary device. Add support for using the vgaarb functions and fall back if nothing's set them. Signed-off-by:
-
Matthew Garrett authored
vga-switcheroo currently changes the default VGA device by fiddling with the IORESOURCE_ROM_SHADOW flag on the device. This isn't strictly accurate, since there's no guarantee that switching also changes the ROM decoding. Switch over to using the vgaarb functions for this. Signed-off-by:
-
Matthew Garrett authored
The default VGA device is a somewhat fluid concept on platforms with multiple GPUs. Add support for setting it so switching code can update things appropriately, and make sure that the sysfs code returns the right device if it's changed. v2: Updated to fix builds when __ARCH_HAS_VGA_DEFAULT_DEVICE is false. Signed-off-by:
<benh@kernel.crashing.org> Cc: airlied@redhat.com Signed-off-by:
-
Alex Deucher authored
- add support for rs6xx - add support for DCE4/5 - fixup 6xx/7xx Signed-off-by:
Alex Deucher <alexander.deucher@amd.com> Signed-off-by:
-
Alex Deucher authored
This adds register definitions for HDMI/DP audio on DCE2/3/4/5 hardware. Signed-off-by:
-
Alex Deucher authored
Improve handling of bpc (bits per color) in radeon. In most cases we want 8 except for HDMI, DP, LVDS, and eDP. v2: handle DP better. Signed-off-by:
Lennert Buytenhek <buytenh@wantstofly.org> Signed-off-by:
-
Daniel Vetter authored
This regression has been introduced in commit f56f821f Author: Daniel Vetter <daniel.vetter@ffwll.ch> Date: Sun Mar 25 19:47:41 2012 +0200 mm: extend prefault helpers to fault in more than PAGE_SIZE I have failed to notice this because x86 asm seems to happily compile things as-is. Reported-by:
Geert Uytterhoeven <geert@linux-m68k.org> Signed-off-by:
Daniel Vetter <daniel.vetter@ffwll.ch> Signed-off-by:
-
Takashi Iwai authored
The new structs added in struct detailed_data_monitor_range must be marked with packed attribute although the outer struct itself is already marked as packed. Otherwise these 7-bytes structs may be aligned, and give the wrong position and size for the data. Signed-off-by:
Takashi Iwai <tiwai@suse.de> Acked-by:
-
Takashi Iwai authored
HD panel (1366x768) found most commonly on laptops can't be represented exactly in CVT/DMT expression, which leads to 1368x768 instead, because 1366 can't be divided by 8. Add a hack to convert to 1366x768 manually as an exception. Signed-off-by:
-
- Apr 20, 2012
-
-
Jim Cromie authored
[airlied: fixed one more new one added since] Signed-off-by:
Jim Cromie <jim.cromie@gmail.com> Signed-off-by:
-
Takashi Iwai authored
Reviewed-by:
-
Adam Jackson authored
Signed-off-by:
Rodrigo Vivi <rodrigo.vivi@intel.com> Signed-off-by:
-
Adam Jackson authored
Some common sizes that don't show up in DMT. Signed-off-by:
-
Adam Jackson authored
We want the same type for extra modes inferred from ranges. Signed-off-by:
-
Adam Jackson authored
Signed-off-by:
-
Adam Jackson authored
EDID 1.4 retcons the meaning of the "GTF feature" bit to mean "is continuous frequency", and moves the set of supported timing formulas into the range descriptor itself. In any event, the range descriptor can act as a filter on the DMT list without regard to a specific timing formula. Signed-off-by:
-
Adam Jackson authored
Signed-off-by:
-
Adam Jackson authored
Copied from the list in xserver. Signed-off-by:
-
Adam Jackson authored
Slightly more honest naming. Signed-off-by:
-
Adam Jackson authored
mode_in_range() handles what this was warning about. Signed-off-by:
-
Adam Jackson authored
It won't find any, yet. Fix up callers to match: standard mode codes will look prefer r-b modes for a given size if present, EST3 mode codes will look for exactly the r-b-ness mentioned in the mode code. This might mean fewer modes matched for EST3 mode codes between now and when the DMT mode list regrows the r-b modes, but practically speaking EST3 codes don't exist in the wild. Signed-off-by:
-
Adam Jackson authored
No functional change, but will make an upcoming change clearer. Signed-off-by:
-
Adam Jackson authored
Signed-off-by:
-
Paulo Zanoni authored
CEA modes 6, 7, 8, 9, 21, 22, 23, 24, 44, 45, 50, 51, 54, 55, 58 and 59 require sending pixel data 2 times. This doesn't mean the modes will work yet, but now the drivers know they're different. Signed-off-by:
Paulo Zanoni <paulo.r.zanoni@intel.com> Reviewed-by:
-
Paulo Zanoni authored
The specification defines a VIC (Video Identification Code) for each mode. When we're browsing drm_edid_modes.h, it really helps to have the number available (otherwise we have to count...). These numbers are also used in the EDID data (by the CEA-EXT extension block). Signed-off-by:
-
Lars-Peter Clausen authored
The CEA extension block has a field which describes which YCbCr modes are supported by the device, use it to fill the drm_display_info color_formats fields. Also the existence of a CEA extension block is used as indication that the device supports RGB. Signed-off-by:
Lars-Peter Clausen <lars@metafoo.de> Reviewed-by:
Jesse Barnes <jbarnes@virtuousgeek.org> Signed-off-by:
-
