From: Thomas Hellstrom <thomas@shipmail.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 01/12] gma500: Move the basic driver out of staging
Date: Thu, 03 Nov 2011 21:18:39 +0100 [thread overview]
Message-ID: <4EB2F71F.5050906@shipmail.org> (raw)
In-Reply-To: <20111103182046.29503.60288.stgit@bob.linux.org.uk>
On 11/03/2011 07:20 PM, Alan Cox wrote:
> From: Alan Cox<alan@linux.intel.com>
>
> This driver supports unaccelerated KMS display, and accelerated console
> handling on the Intel Poulsbo, Oaktrail, Cedarview and Medfield hardware.
>
> For the initial merge Medfield will be left out as it needs considerable
> further work to reach a decent standard
>
> Begin by adding the Makefiles and Kconfig. These are not yet plumbed into
> the DRM layer so will have no effect on their own
>
> Signed-off-by: Alan Cox<alan@linux.intel.com>
> ---
>
Alan,
Good to see some of this old code being used.
I haven't followed this work closely, but I have a question:
The first poulsbos used to crash badly when attempting to map the GTT
write-combined, and IIRC it didn't even advertise write-combining
capabilities on the PCI BAR. Has this been improved on lately or how is
this handled currently?
Thanks,
Thomas
next prev parent reply other threads:[~2011-11-03 20:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-03 18:20 [PATCH 01/12] gma500: Move the basic driver out of staging Alan Cox
2011-11-03 18:20 ` [PATCH 02/12] gma500: GEM and GEM glue Alan Cox
2011-11-03 19:27 ` Daniel Vetter
2011-11-03 18:21 ` [PATCH 03/12] gma500: introduce the GTT and MMU handling logic Alan Cox
2011-11-03 20:12 ` Daniel Vetter
2011-11-03 22:25 ` Alan Cox
2011-11-03 22:32 ` Daniel Vetter
2011-11-03 18:21 ` [PATCH 04/12] gma500: introduce the framebuffer support code Alan Cox
2011-11-03 18:21 ` [PATCH 05/12] gma500: Add device framework Alan Cox
2011-11-03 18:21 ` [PATCH 06/12] gma500: Add the glue to the various BIOS and firmware interfaces Alan Cox
2011-11-03 18:21 ` [PATCH 07/12] gma500: Add the i2c bus support Alan Cox
2011-11-03 18:22 ` [PATCH 08/12] gma500: Add the core DRM files and headers Alan Cox
2011-11-16 12:04 ` Dave Airlie
2011-11-16 14:47 ` Alan Cox
2011-11-03 18:22 ` [PATCH 09/12] gma500: Add Poulsbo support Alan Cox
2011-11-03 18:22 ` [PATCH 10/12] gma500: Add Oaktrail support Alan Cox
2011-11-03 18:22 ` [PATCH 11/12] gma500: Add support for Cedarview Alan Cox
2011-11-03 18:22 ` [PATCH 12/12] gma500: Now connect up to the DRM build to finish the job Alan Cox
2011-11-03 20:18 ` Thomas Hellstrom [this message]
2011-11-03 22:27 ` [PATCH 01/12] gma500: Move the basic driver out of staging Alan Cox
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=4EB2F71F.5050906@shipmail.org \
--to=thomas@shipmail.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dri-devel@lists.freedesktop.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.