From: Jerome Glisse <glisse@freedesktop.org>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: Jerome Glisse <jglisse@redhat.com>,
airlied@gmail.com, linux-kernel@vger.kernel.org,
dri-devel@lists.sf.net
Subject: Re: [PATCH 3/3] drm/radeon/kms: Add range pinning to crtc/cursor bo
Date: Fri, 20 Nov 2009 19:04:45 +0100 [thread overview]
Message-ID: <20091120180445.GB3467@localhost.localdomain> (raw)
In-Reply-To: <a728f9f90911200847g68311ddbx4a5fa652588504ab@mail.gmail.com>
On Fri, Nov 20, 2009 at 11:47:22AM -0500, Alex Deucher wrote:
> On Fri, Nov 20, 2009 at 8:29 AM, Jerome Glisse <jglisse@redhat.com> wrote:
> > We force the crtc & cursor bo to be in the first 64M, this
> > will help on legacy modesetting hw where the offset of
> > scanout buffer and cursor are relative to a base address.
>
> This limitation only applies to pre-avivo (r1xx-r4xx) chips, there's
> no need on newer hardware. Also the cursor and crtc have to be within
> 128 MB of each other, so you could bump the limits to 128 MB. Another
> thing to consider down the road might be to treat memory over 128 MB
> as "invisible" on these pre-avivo chips (once we support that in
> general) then we no longer need this limit.
>
> Alex
>
I choosed 64M in hope to disminish VRAM fragmentation a little,
this is also why i did not bother to make this conditional for
legacy modesetting hw. For supporting non visible vram see my
other ttm thread. I am working on adding this knowledge to ttm.
Cheers,
Jerome
next prev parent reply other threads:[~2009-11-20 18:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-20 13:29 Jerome Glisse
2009-11-20 13:29 ` [PATCH 1/3] drm/ttm: Add range validation function Jerome Glisse
2009-11-20 13:29 ` [PATCH 2/3] drm/radeon/kms: Rework radeon object handling Jerome Glisse
2009-11-20 13:29 ` [PATCH 3/3] drm/radeon/kms: Add range pinning to crtc/cursor bo Jerome Glisse
2009-11-20 16:47 ` Alex Deucher
2009-11-20 18:04 ` Jerome Glisse [this message]
2009-12-04 0:10 ` [PATCH 2/3] drm/radeon/kms: Rework radeon object handling Dave Airlie
2009-12-02 10:04 ` [PATCH 1/3] drm/ttm: Add range validation function Thomas Hellström
2009-12-01 23:53 ` Dave Airlie
2009-12-02 7:17 ` Re: Thomas Hellstrom
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=20091120180445.GB3467@localhost.localdomain \
--to=glisse@freedesktop.org \
--cc=airlied@gmail.com \
--cc=alexdeucher@gmail.com \
--cc=dri-devel@lists.sf.net \
--cc=jglisse@redhat.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 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.