Bug 15714 - PROBLEM: intelfb driver causes trace
PROBLEM: intelfb driver causes trace
Status: CLOSED INSUFFICIENT_DATA
Product: Drivers
Classification: Unclassified
Component: Console/Framebuffers
All Linux
: P1 normal
Assigned To: James Simmons
:
Depends on:
Blocks: 14885
  Show dependency treegraph
 
Reported: 2010-04-07 20:34 UTC by Maciej Rutecki
Modified: 2012-03-14 11:29 UTC (History)
5 users (show)

See Also:
Kernel Version: 2.6.33.1
Tree: Mainline
Regression: Yes


Attachments

Description Maciej Rutecki 2010-04-07 20:34:31 UTC
Subject    : PROBLEM: intelfb driver causes trace
Submitter  : "Troilo, Domenic" <Domenic.Troilo@gwl.ca>
Date       : 2010-04-01 14:52
Message-ID : CBF11783AA883E41A86C009F3AE5D47F0CAE08C1@GWCORPMAIL4.gwl.bz
References : http://marc.info/?l=linux-kernel&m=127013359722664&w=2

This entry is being used for tracking a regression from 2.6.32.  Please don't
close it until the problem is fixed in the mainline.
Comment 1 Florian Mickler 2010-12-08 08:15:49 UTC
It shouldn't be possible to compile both, i915 and intelfb module. They don't work together. 


drivers/video/Kconfig:

1157 config FB_INTEL
1158         tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965     GM support (EXPERIMENTAL)"
1159         depends on EXPERIMENTAL && FB && PCI && X86 && AGP_INTEL && EMBEDDE     D
1160         select FB_MODE_HELPERS
1161         select FB_CFB_FILLRECT
1162         select FB_CFB_COPYAREA
1163         select FB_CFB_IMAGEBLIT
1164         select FB_BOOT_VESA_SUPPORT if FB_INTEL = y
1165         depends on !DRM_I915

Doesn't this prevent the intelfb module from being compiled when i915 is selected?
Comment 2 Florian Mickler 2012-03-13 23:22:28 UTC
I guess this has been solved in the meantime. Anyhow, please post a note if this is still a problem.
Comment 3 Domenic Troilo 2012-03-14 11:29:41 UTC
(In reply to comment #2)
> I guess this has been solved in the meantime. Anyhow, please post a note if
> this is still a problem.

This is no longer a problem.  Thanks

Note You need to log in before you can comment on or make changes to this bug.