[meta-intel] Next Gen Intel BSPs (GMA600 on TunnelCreek)

[Patrik Jakobsson]

On Tue, Feb 25, 2014 at 9:07 PM, Scott Garman <scott.a.garman at intel.com> wrote:
> On 02/25/2014 08:32 PM, Tom Zanussi wrote:
>>
>> On Tue, 2014-02-25 at 15:26 +0100, Scott Garman wrote:
>>>
>>> On 02/25/2014 03:20 PM, Hart, Darren wrote:
>>>>
>>>> Scott, question for you below...
>>>
>>>
>>> <snip>
>>>
>>>>>>> So the problem here is some kind of interference with the
>>>>>>
>>>>>> CONFIG_GMA600,
>>>>>>>
>>>>>>> which is now turned on by default - I'll have to either dig into find
>>>>>>> the actual problem or just turn it off for _crownbay-noegd...
>>>>>>
>>>>>>
>>>>>> Oh... Hrm... We should actually be able to use that driver now on the
>>>>>> Tunnel Creek systems as of 3.10-LTSI and 3.13+. Scott Garman tested it
>>>>>> on
>>>>>> the MinnowBoard, I haven't done so myself unfortunately. Do we specify
>>>>>> another driver in the xorg.conf or something that is causing some
>>>>>> confusion about which driver to use?
>>>>>>
>>>>>
>>>>> No, there's no special xorg.conf for crownbay-noemgd...
>>>>
>>>>
>>>> Scott, did you have to do something special to get the gma600 driver
>>>> working on the MinnowBoard? Did it require you to write an xorg.conf?
>>>
>>>
>>> Yes, you need to include the xf86-modesetting driver and set the
>>> following in your xorg.conf:
>>>
>>> Section "Device"
>>>           Identifier      "gma500"
>>>           Driver                "modesetting"
>>> EndSection
>>>
>>> Section "Screen"
>>>           Identifier      "gma500 Screen"
>>>           Device          "gma500"
>>> EndSection
>>>
>>> I think that should be all you need. Let me know if you run into
>>> problems with that.
>>>
>>
>> That's a little better but still getting:
>>
>> [1782396.836] (==) AIGLX enabled
>> [1782396.836] Loading extension GLX
>> [1782396.836] (II) LoadModule: "modesetting"
>> [1782396.845] (II) Loading
>> /usr/lib/xorg/modules/drivers/modesetting_drv.so
>> [1782396.850] (II) Module modesetting: vendor="X.Org Foundation"
>> [1782396.851]   compiled for 1.15.0, module version = 0.8.1
>> [1782396.851]   Module class: X.Org Video Driver
>> [1782396.851]   ABI class: X.Org Video Driver, version 15.0
>> [1782396.851] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
>> [1782396.851] (--) using VT number 3
>>
>> [1782397.299] (WW) Falling back to old probe method for modesetting
>> [1782397.380] (EE) Screen 0 deleted because of no matching config section.
>> [1782397.380] (II) UnloadModule: "modesetting"
>> [1782397.380] (EE) Device(s) detected, but none match those in the config
>> file.
>> [1782397.380] (EE)
>> Fatal server error:
>> [1782397.380] (EE) no screens found(EE)
>
>
> Hmmm...I'm not sure what to suggest. I'd like to re-create the setup but I
> can't do it out here. I've added Patrik Jakobsson to the cc: list - he might
> have some suggestions.
>
> Scott

Hi all,

Does the gma500_gfx driver detect the output and the modes properly?
Can you send a dmesg with drm.debug=0xfe

Cheers
Patrik