All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Linux Fbdev development list <linux-fbdev-devel@lists.sourceforge.net>
Cc: "Antonino A. Daplas" <adaplas@hotpop.com>,
	Andrew Morton <akpm@osdl.org>,
	Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: [PATCH] Resource management for fbdev.
Date: Fri, 08 Apr 2005 11:52:51 +1000	[thread overview]
Message-ID: <1112925171.9517.358.camel@gaston> (raw)
In-Reply-To: <Pine.LNX.4.56.0503260019020.20306@pentafluge.infradead.org>

On Sat, 2005-03-26 at 00:34 +0000, James Simmons wrote:
> I have a new resource management for testing. Its is a clenaup of the 
> handling the drawing plane and the cursor. I have tested it on 
> 
> New NVIDIA fbdev driver.
> NeoMagic
> ATY Mach64
> Radeon
> Vesa
> 
> Please try it out. The patch is over 40K so grab it from the below link
> 
> http://www.infradead.org/~jsimmons/resource.diff

I had a quick look, and I'm fairly confused. That patch introduces a lot
of changes all over the place without any comment or explanation, in
code that has proven in the past to be fragile and prone to side
effects. Also, I see no explanation of the rationale for the resource
manager and it's API. At a minimum, the patch should be split into

 - implementation of the resource manager with appropriate explanations
and documentation
 - driver updates

Have you worked at all with the DRM folks ? We have a bad need to merge
DRM and fbdev as soon as possible and we need while doing so to impement
some kind of efficient memory manager for the card video RAM. I'm not
sure your proposal fits into this picture.

Also, we need to properly deal with the fact that real soon now, not all
of the video memory will be accessible from the CPU (not only from the
kernel, but from the CPU in general). There are already cards whose PCI
aperture is too small to enclose the entire video memory, and some funky
issues with aperture control on radeons might make me also limit the
amount of video memory accessible.

Ben.
 



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

  reply	other threads:[~2005-04-08  1:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-26  0:34 [PATCH] Resource management for fbdev James Simmons
2005-04-08  1:52 ` Benjamin Herrenschmidt [this message]
2005-04-08  7:04   ` Miles Lane
2005-04-08  8:10   ` Geert Uytterhoeven
2005-05-02 19:28   ` James Simmons

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=1112925171.9517.358.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=adaplas@hotpop.com \
    --cc=akpm@osdl.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /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.