public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Dave Airlie <airlied@linux.ie>
Cc: Jeff Garzik <jeff@garzik.org>,
	linux-kernel@vger.kernel.org, vojtech@suse.cz
Subject: Re: [RFC] GPU device layer patchset (00/07)
Date: Mon, 31 Jul 2006 14:42:48 +0200	[thread overview]
Message-ID: <20060731124248.GA3257@elf.ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.64.0607221753390.5320@skynet.skynet.ie>

Hi!

> >Where can I find more info on why this might be nice?
> >Or simply more info on what this actually does for me?
> 
> It does nothing for you yet, it is just step one for getting the DRM and 
> framebuffer drivers to co-exist in the driver model world, with the next 
> step being allowing a channel of communication between the two layers with 
> a view that later I can ask the DRM to disable fbdev or pass info to it..
> 
> Why do we not want fbdev and DRM in one driver? as it would break way too 
> many existing systems..
> 
> It also allows DRM to get called at suspend/resume time.

Looks good to me. I guess I should get DRM working...

I actually tried a bit, and got some reasonably-recent Xserver here,
but now I get

root@amd:/home/pavel# glxinfo
name of display: :0.0

ERROR!  sizeof(I830DRIRec) does not match passed size from device
driver
libGL warning: 3D driver returned no fbconfigs.
libGL error: InitDriver failed
libGL error: reverting to (slow) indirect rendering
display: :0  screen: 0
direct rendering: No
server glx vendor string: SGI
server glx version string: 1.2
server glx extensions:

:-(
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2006-07-31 12:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-22 15:38 [RFC] GPU device layer patchset (00/07) Dave Airlie
2006-07-22 15:38 ` [PATCH] drm: remove local copies of pci bus/slot/func (01/07) Dave Airlie
2006-07-22 15:38   ` [PATCH] drm: remove pci domain local copy (02/07) Dave Airlie
2006-07-22 15:38     ` [PATCH] gpu: Initial GPU layer addition. (03/07) Dave Airlie
2006-07-22 15:38       ` [PATCH] gpu/radeon: add a radeon lowlevel GPU driver (04/07) Dave Airlie
2006-07-22 15:38         ` [PATCH] gpu/radeonfb: add GPU support to radeonfb (05/07) Dave Airlie
2006-07-22 15:38           ` [PATCH] gpu/drm: Add GPU layer support to generic DRM (06/07) Dave Airlie
2006-07-22 15:38             ` [PATCH] drm/gpu/radeon: Add radeon DRM support to use GPU layer (07/07) Dave Airlie
2006-07-22 19:54       ` [PATCH] gpu: Initial GPU layer addition. (03/07) Jesse Barnes
2006-07-22 21:04       ` Nix
2006-07-23 20:04       ` Luca
2006-07-22 16:34     ` [PATCH] drm: remove pci domain local copy (02/07) Jeff Garzik
2006-07-22 16:53       ` Dave Airlie
2006-07-22 16:35 ` [RFC] GPU device layer patchset (00/07) Jeff Garzik
2006-07-22 17:00   ` Dave Airlie
2006-07-31 12:42     ` Pavel Machek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-07-22 19:40 Louis E Garcia II

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=20060731124248.GA3257@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=airlied@linux.ie \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vojtech@suse.cz \
    /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