From: Greg KH <greg@kroah.com>
To: airlied@linux.ie
Cc: linux-kernel@vger.kernel.org
Subject: Re: gpu sharing layer for kernel
Date: Wed, 24 Jan 2007 13:46:54 -0800 [thread overview]
Message-ID: <20070124214654.GA30634@kroah.com> (raw)
In-Reply-To: <1169637623985-git-send-email-airlied@linux.ie>
On Wed, Jan 24, 2007 at 10:20:18PM +1100, airlied@linux.ie wrote:
> This patch series contains the gpu sharing layer for kernel that I've
> mentioned before. It should apply against Linus's git tree.
Yeah!
> Why do we want this?
>
> Currently the kernel cannot provide both the fb and drm drivers with
> access to the device model and this means the drm cannot get any
> suspend/resume callbacks. This layer attempts to fix this problem by
> adding a bus for the gpu drivers to attach to. Currently a lowlevel
> binding driver is needed along with optional fb and drm components.
If we were to allow this kind of "sharing" for all PCI devices would
that work out instead? Or would this layer still be needed?
thanks,
greg k-h
next prev parent reply other threads:[~2007-01-24 21:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-24 11:20 gpu sharing layer for kernel airlied
2007-01-24 11:20 ` [PATCH] gpu: Initial gpu layer addition airlied
2007-01-24 11:20 ` [PATCH] gpu/radeon: add a radeon lowlevel GPU driver airlied
2007-01-24 11:20 ` [PATCH] gpu/radeonfb: add GPU support to radeonfb airlied
2007-01-24 11:20 ` [PATCH] gpu/drm: Add GPU layer support to generic DRM airlied
2007-01-24 11:20 ` [PATCH] drm/gpu/radeon: Add radeon DRM support to use GPU layer airlied
2007-01-25 0:07 ` [PATCH] gpu/radeonfb: add GPU support to radeonfb Benjamin Herrenschmidt
2007-01-30 19:50 ` Dave Airlie
2007-01-24 21:46 ` Greg KH [this message]
2007-01-24 22:39 ` gpu sharing layer for kernel Dave Airlie
2007-01-25 22:06 ` Greg KH
2007-01-28 21:16 ` Dave Jones
2007-02-07 18:42 ` James Simmons
2007-02-06 19:40 ` James Simmons
2007-01-25 7:56 ` Paul Collins
2007-01-30 19:49 ` 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=20070124214654.GA30634@kroah.com \
--to=greg@kroah.com \
--cc=airlied@linux.ie \
--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