public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Dave Airlie <airlied@gmail.com>
Cc: Alan Cox <alan@linux.intel.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gma500: Intel GMA500 staging driver
Date: Wed, 23 Feb 2011 16:01:55 -0800	[thread overview]
Message-ID: <20110224000155.GA32282@kroah.com> (raw)
In-Reply-To: <AANLkTimPpr+OugTiPpYxNyS78vqActuURw-tnxJVxi18@mail.gmail.com>

On Thu, Feb 24, 2011 at 09:51:04AM +1000, Dave Airlie wrote:
> On Tue, Feb 22, 2011 at 10:17 PM, Alan Cox <alan@linux.intel.com> wrote:
> > This is an initial staging driver for the GMA500. It's been stripped out
> > of the PVR drivers and crunched together from various bits of code and
> > different kernels.
> >
> > Currently it's unaccelerated but still pretty snappy even compositing with
> > the frame buffer X server.
> >
> > Lots of work is needed to rework the ttm and bo interfaces from being
> > ripped out and then 2D acceleration wants putting back for framebuffer and
> > somehow eventually via DRM.
> >
> > There is no support for the parts without open source userspace (video
> > accelerators, 3D) as per kernel policy.
> >
> > I'm not a DRM expert so if there is anyone with a GMA500 who actually knows
> > something about DRI internals then help would be most welcome.
> >
> 
> 
> Okay I'm okay with this going into staging but we should work out a
> plan for it going forward.

Good as I just added it to the staging-next tree a few hours ago :)

> I don't have any poulsbo hw but if some were to appear I could
> probably expend effort on this.
> 
> So where do we want to go my opinion is
> 
> a) remove all userspace interfaces and simplify ttm memory management usage.
> b) add support to hook this up to the dumb ioctl so we can do trivial
> generic front buffer allocation, so then a libkms + dumb kms
> modesetting driver can work on it.
> c) figure out how to add interface for acceleration users. Whether TTM
> fence interfaces are required etc.

That all sounds reasonable to me.  Patches now gladly accepted.

thanks,

greg k-h

  reply	other threads:[~2011-02-24  0:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-22 12:17 [PATCH] gma500: Intel GMA500 staging driver Alan Cox
2011-02-22 14:44 ` Greg KH
2011-02-22 14:51   ` Alan Cox
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 [this message]
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=20110224000155.GA32282@kroah.com \
    --to=greg@kroah.com \
    --cc=airlied@gmail.com \
    --cc=alan@linux.intel.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