linux.git/drivers/gpu/drm/Kconfig, branch v2.6.29

fbdev/drm: fix Kconfig submenu mess in "Graphics support"

2009-02-18T23:37:56+00:00

Submenus of the graphics support "Support for frame buffer devices" and
"Direct Rendering Manager (XFree86 4.1.0 and higher DRI support)" are
broken in half after latest changes for Intel 915 mode setting support.

The DRM subsection is broken because one option is put outside the choice
section it depends on.

The frame buffers part is broken then due to circular dependency.  Fix
this by make Intel frame buffers depend on CONFIG_INTEL_AGP.

Kconfigs are broken by d2f59357700487a8b944f4f7777d1e97cf5ea2ed
("drm/i915: select framebuffer support automatically").

This is probably not only way to fix this.

Signed-off-by: Krzysztof Helt 
Cc: Ingo Molnar 
Cc: Dave Airlie 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

drm/i915: select framebuffer support automatically

2009-02-08T11:53:05+00:00

Migration helper.

The i915 driver recently added a 'depends on FB' rule to its
Kconfig entry - which silently turns off DRM_I915 if someone
has a working config but no CONFIG_FB selected, and upgrades
to the latest upstream kernel.

Norbert Preining reported this problem:

   Bug-Entry   : http://bugzilla.kernel.org/show_bug.cgi?id=12599
   Subject     : dri /dev node disappeared with 2.6.29-rc1

So change it to "select FB", which auto-selects framebuffer
support. This way the driver keeps working, regardless of
whether FB was enabled before or not.

Kconfig select's of interactive options can be problematic to
dependencies and can cause build breakages - but in this case
it's safe because it's a leaf entry with no dependencies of its
own.

( There is some minor circular dependency fallout as FB_I810
  and FB_INTEL also used 'depends on FB' constructs - update
  those to "select FB" too. )

Reported-by: Norbert Preining 
Signed-off-by: Ingo Molnar 
Signed-off-by: Dave Airlie

drm: kconfig have drm core select i2c for kms

2008-12-29T07:47:24+00:00

Signed-off-by: Dave Airlie

drm/i915: Register module dependencies for the modesetting code.

2008-12-29T07:47:23+00:00

Signed-off-by: Eric Anholt 
Signed-off-by: Dave Airlie

DRM: i915: add mode setting support

2008-12-29T07:47:23+00:00

This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported.  HDMI, DisplayPort and additional SDVO output support will
follow.

Support for the mode setting code is controlled by the new 'modeset'
module option.  A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.

Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing.  So use caution when
enabling this code; be sure your user level code supports the new
interfaces.

A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.

Co-authors: Dave Airlie , Hong Liu 

Signed-off-by: Jesse Barnes 
Signed-off-by: Eric Anholt 
Signed-off-by: Dave Airlie

Export tiny shmem_file_setup for DRM-GEM

2008-10-20T23:17:42+00:00

We're trying to keep the !CONFIG_SHMEM tiny-shmem.c (using ramfs without
swap) in synch with CONFIG_SHMEM shmem.c (and mpm is preparing patches
to combine them).  I was glad to see EXPORT_SYMBOL_GPL(shmem_file_setup)
go into shmem.c, but why not support DRM-GEM when !CONFIG_SHMEM too?
But caution says still depend on MMU, since !CONFIG_MMU is.. different.

Signed-off-by: Hugh Dickins 
Acked-by: Matt Mackall 
Acked-by: Dave Airlie 
Signed-off-by: Linus Torvalds

drm: make CONFIG_DRM depend on CONFIG_SHMEM.

2008-10-17T21:10:54+00:00

This can be removed later when DRM doesn't depend on shmem.

Signed-off-by: Dave Airlie

FB_SIS=m, DRM_SIS=y is not a legal configuration.

2008-10-17T21:10:11+00:00

Reported-by: Randy Dunlap 
Signed-off-by: Adrian Bunk 
Signed-off-by: Dave Airlie

drm: reorganise drm tree to be more future proof.

2008-07-14T00:45:01+00:00

With the coming of kernel based modesetting and the memory manager stuff,
the everything in one directory approach was getting very ugly and
starting to be unmanageable.

This restructures the drm along the lines of other kernel components.

It creates a drivers/gpu/drm directory and moves the hw drivers into
subdirectores. It moves the includes into an include/drm, and
sets up the unifdef for the userspace headers we should be exporting.

Signed-off-by: Dave Airlie