From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Kristoffer Ericson <kristoffer.ericson@gmail.com>
Cc: patrik.r.jakobsson@gmail.com, linux-kernel@vger.kernel.org,
greg@kroah.com
Subject: Re: GMA500 support
Date: Wed, 23 Nov 2011 11:28:47 +0000 [thread overview]
Message-ID: <20111123112847.57c20f8f@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20111121182910.GA2856@Boggieman>
On Mon, 21 Nov 2011 19:29:10 +0100
Kristoffer Ericson <kristoffer.ericson@gmail.com> wrote:
> Greetings,
>
> Im syncing my gma500 tree to all the patches I see pass through the kernel mailinglist and
> its progressing well.
> However, It would be nice with an todo list or a more practical this-works list. I know
> its not a priority but would simplify alot for end users.
If you configure it in the following should work on GMA500/600
- internal laptop displays including backlight
- external svga
- mode setting via KMS
- framebuffer console
- the framebuffer X server (and once out generally Dave Airlie's generic
KMS X server)
- suspend/resume
The following I know don't work
- Huge external displays so large they won't fit in 8MB at init time
(causes a crash)
- Using the vesa X server with it - this confuses stuff and isn't
fixable, it's a "wrong user configuration"
Unsupported
- 2D hardware acceleration except console scrolling (as it seems to be
too slow to be useful). I may add some 2D bits later where they do help
(eg back to front blitting may be worth it just about)
- 3D engine (no public documentation)
- Video playback acceleration. In theory there is enough info in the
VAAPI code for GMA500/600 that has been published and in the old
'binary X/source kernel' driver to do this but someone will have to
work on it if they want it
- Dell Mini HDMI port. This seems to be some kind of external bridge
chip. Being a TV luddite I don't yet own an HDMI capable display to
test.
And I'm sure we have a few bugs left !
Alan
next prev parent reply other threads:[~2011-11-23 11:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-21 18:29 Kristoffer Ericson
2011-11-23 11:28 ` Alan Cox [this message]
2011-11-23 15:50 ` Patrik Jakobsson
2011-11-24 16:20 ` Kristoffer Ericson
2011-11-24 21:23 ` Alan Cox
2011-12-02 17:23 ` Alan Cox
2011-12-03 10:03 ` Patrik Jakobsson
2011-12-05 17:43 ` Alan Cox
2011-12-01 20:29 ` Kristoffer Ericson
2011-12-01 21:17 ` Alan Cox
2012-03-28 13:28 ` Thierry Reding
2012-03-28 14:53 ` Alan Cox
2012-03-28 15:02 ` Thierry Reding
2011-11-23 15:53 ` Patrik Jakobsson
2011-11-24 16:22 ` Kristoffer Ericson
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=20111123112847.57c20f8f@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=greg@kroah.com \
--cc=kristoffer.ericson@gmail.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®