From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Patrik Jakobsson <patrik.r.jakobsson@gmail.com>
Cc: Christian Gmeiner <christian.gmeiner@gmail.com>,
linux-kernel@vger.kernel.org, Greg Kroah-Hartman <greg@kroah.com>
Subject: Re: gma500: Cannot find any crtc or sizes - going 1024x768
Date: Tue, 12 Jun 2012 17:04:12 +0100 [thread overview]
Message-ID: <20120612170412.359967ec@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <CAMeQTsZZ0ay7YqkzUzkhe6D6FNsQXaDKHfJKB6_6icd=4VemrA@mail.gmail.com>
> 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
next prev parent reply other threads:[~2012-06-12 16:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-11 14:16 Christian Gmeiner
2012-06-11 22:40 ` Patrik Jakobsson
2012-06-12 8:59 ` Christian Gmeiner
2012-06-12 11:06 ` Patrik Jakobsson
2012-06-12 11:15 ` Alan Cox
2012-06-12 11:37 ` Christian Gmeiner
2012-06-12 12:27 ` Alan Cox
2012-06-12 13:55 ` Patrik Jakobsson
2012-06-12 16:04 ` Alan Cox [this message]
2012-06-12 19:09 ` Patrik Jakobsson
2012-06-12 20:23 ` Alan Cox
2012-06-12 21:58 ` Christian Gmeiner
2012-06-13 9:25 ` Christian Gmeiner
2012-06-13 10:27 ` Alan Cox
2012-06-13 10:31 ` Alan Cox
2012-06-13 12:26 ` Christian Gmeiner
2012-06-13 19:50 ` Patrik Jakobsson
2012-06-21 8:55 ` Christian Gmeiner
2012-06-21 8:54 ` Christian Gmeiner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120612170412.359967ec@pyramind.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=christian.gmeiner@gmail.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patrik.r.jakobsson@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®