From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753457Ab2FLQAi (ORCPT ); Tue, 12 Jun 2012 12:00:38 -0400 Received: from lxorguk.ukuu.org.uk ([81.2.110.251]:54361 "EHLO lxorguk.ukuu.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752773Ab2FLQAh (ORCPT ); Tue, 12 Jun 2012 12:00:37 -0400 Date: Tue, 12 Jun 2012 17:04:12 +0100 From: Alan Cox To: Patrik Jakobsson Cc: Christian Gmeiner , linux-kernel@vger.kernel.org, Greg Kroah-Hartman Subject: Re: gma500: Cannot find any crtc or sizes - going 1024x768 Message-ID: <20120612170412.359967ec@pyramind.ukuu.org.uk> In-Reply-To: References: <20120612132736.642a4a5a@pyramind.ukuu.org.uk> X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.8; x86_64-redhat-linux-gnu) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAFVBMVEWysKsSBQMIAwIZCwj///8wIhxoRDXH9QHCAAABeUlEQVQ4jaXTvW7DIBAAYCQTzz2hdq+rdg494ZmBeE5KYHZjm/d/hJ6NfzBJpp5kRb5PHJwvMPMk2L9As5Y9AmYRBL+HAyJKeOU5aHRhsAAvORQ+UEgAvgddj/lwAXndw2laEDqA4x6KEBhjYRCg9tBFCOuJFxg2OKegbWjbsRTk8PPhKPD7HcRxB7cqhgBRp9Dcqs+B8v4CQvFdqeot3Kov6hBUn0AJitrzY+sgUuiA8i0r7+B3AfqKcN6t8M6HtqQ+AOoELCikgQSbgabKaJW3kn5lBs47JSGDhhLKDUh1UMipwwinMYPTBuIBjEclSaGZUk9hDlTb5sUTYN2SFFQuPe4Gox1X0FZOufjgBiV1Vls7b+GvK3SU4wfmcGo9rPPQzgIabfj4TYQo15k3bTHX9RIw/kniir5YbtJF4jkFG+dsDK1IgE413zAthU/vR2HVMmFUPIHTvF6jWCpFaGw/A3qWgnbxpSm9MSmY5b3pM1gvNc/gQfwBsGwF0VCtxZgAAAAASUVORK5CYII= Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > 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 Firstly it should never matter - there are no Moorestown devices in circulation. E600T is very similar to Oaktrail. So the real question here seems to be why does the IS_MRST macro matter. What weird firmware is involved here ? Alan