From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Greg KH <greg@kroah.com>
Cc: Alan Cox <alan@linux.intel.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gma500: Intel GMA500 staging driver
Date: Tue, 22 Feb 2011 14:51:31 +0000 [thread overview]
Message-ID: <20110222145131.00860d4a@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20110222144426.GA1232@kroah.com>
> > Currently it's unaccelerated but still pretty snappy even compositing with
> > the frame buffer X server.
>
> So that's all that is needed on the userspace side? Or is there a
> driver for X that also goes along with this patch that is available
> somewhere?
That's all that is needed.
There is an open source 2D X server but it relies upon the ttm working
an ancient libdrm and some chunks of the PVR driver blob. The actual 2D
command issue code is quite simple fortunately so the challenge is the
ttm/bo stuff.
> Can I also get a TODO file for this directory that lists what needs to
> be done to move it out of the staging tree, as well as an email to
> contact for patches and questions?
Ah I forgot to stg add that ;) it does exist.. Will send an updated
version.
>
> > --- a/drivers/staging/Makefile
> > +++ b/drivers/staging/Makefile
> > @@ -62,12 +62,13 @@ obj-$(CONFIG_SOLO6X10) += solo6x10/
> > obj-$(CONFIG_TIDSPBRIDGE) += tidspbridge/
> > obj-$(CONFIG_ACPI_QUICKSTART) += quickstart/
> > obj-$(CONFIG_WESTBRIDGE_ASTORIA) += westbridge/astoria/
> > -obj-$(CONFIG_SBE_2T3E3) += sbe-2t3e3/
> > +obj-$(CONFIG_SBE_2T3E3) += sbe-2t3e3/
> > obj-$(CONFIG_ATH6K_LEGACY) += ath6kl/
> > obj-$(CONFIG_USB_ENESTORAGE) += keucr/
> > -obj-$(CONFIG_BCM_WIMAX) += bcm/
> > +obj-$(CONFIG_BCM_WIMAX) += bcm/
> > obj-$(CONFIG_FT1000) += ft1000/
> > -obj-$(CONFIG_SND_INTEL_SST) += intel_sst/
> > -obj-$(CONFIG_SPEAKUP) += speakup/
> > +obj-$(CONFIG_SND_INTEL_SST) += intel_sst/
> > +obj-$(CONFIG_SPEAKUP) += speakup/
> > obj-$(CONFIG_TOUCHSCREEN_CLEARPAD_TM1217) += cptm1217/
> > obj-$(CONFIG_TOUCHSCREEN_SYNAPTICS_I2C_RMI4) += ste_rmi4/
> > +obj-$(CONFIG_DRM_PSB) += gma500/
>
> What's with the formatting changes to this file?
It used to be all nicely lined up and was degrading so as I was touching
the end of it I thought I'd stop the rot.
next prev parent reply other threads:[~2011-02-22 14:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-22 12:17 Alan Cox
2011-02-22 14:44 ` Greg KH
2011-02-22 14:51 ` Alan Cox [this message]
2011-02-22 15:40 ` Matthew Garrett
2011-02-22 16:17 ` Alan Cox
2011-02-22 22:59 ` Patrik Jakobsson
2011-02-22 17:09 ` Arnd Bergmann
2011-02-22 17:43 ` Alan Cox
2011-02-23 23:51 ` Dave Airlie
2011-02-24 0:01 ` Greg KH
2011-02-24 12:10 ` Alan Cox
2011-03-01 3:40 ` Dave Airlie
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=20110222145131.00860d4a@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=alan@linux.intel.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.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 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®