Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751674Ab2FLNzw (ORCPT ); Tue, 12 Jun 2012 09:55:52 -0400 Received: from mail-pb0-f46.google.com ([209.85.160.46]:62732 "EHLO mail-pb0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750961Ab2FLNzu (ORCPT ); Tue, 12 Jun 2012 09:55:50 -0400 MIME-Version: 1.0 In-Reply-To: <20120612132736.642a4a5a@pyramind.ukuu.org.uk> References: <20120612132736.642a4a5a@pyramind.ukuu.org.uk> Date: Tue, 12 Jun 2012 15:55:50 +0200 Message-ID: Subject: Re: gma500: Cannot find any crtc or sizes - going 1024x768 From: Patrik Jakobsson To: Alan Cox Cc: Christian Gmeiner , linux-kernel@vger.kernel.org, Greg Kroah-Hartman Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1222 Lines: 36 On Tue, Jun 12, 2012 at 2:27 PM, Alan Cox wrote: >> Works much better with this patch applied - I see a linux desktop on >> the panel :) > > Yay.. > >> Is there a way to overwrite the found modeline? > > You can set modelines via the video interfaces and also by passing it as > a boot parameter. The mode setting X server will also let you set modes. > > > video=640x400@60 > > or similar should work - you can set all kinds of bits this way. > > > If there is a way to identify the platform and that is needed to get it > right then we can also hardcode a DMI match or similar for the device > eventually. Was there a special reason for 0x4108 to be left out in the IS_MRST macro? To me it looks like the bitmask should have been updated in commit: gma500: Add the E6xx PCI identifier we are missing 56125db1eecf8d34d84f7925686110d90724edf0 If this is the case, I'll send a proper patch since this also applies to stable 3.3.x and 3.4.x Patrik -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/