On Sat, 2005-03-12 at 22:55 -0500, Vladimir Dergachev wrote:
> Hi Ben,
>
>Hopefully simple question:
>
>If you were able to change configured aperture size - would you like to ?
> I could possibly imaging situation where this is used to regular access to
> the video memory, but you are
On Sat, 2005-03-12 at 22:22 -0500, Jon Smirl wrote:
> What about using the overlapped mode and dividing memory into four regions
>
> FB0
> PCI visible free mem
> FB1
> APER_SIZE
> non-visible free mem
>
> This way setting the mode on FB0 doesn't always bump into FB1.
I think we don't really have
What about using the overlapped mode and dividing memory into four regions
FB0
PCI visible free mem
FB1
APER_SIZE
non-visible free mem
This way setting the mode on FB0 doesn't always bump into FB1.
The DRM could do this:
FB0
back0
depth0
aux0, etc
PCI visible free mem - textures priority 2
aux1,
Hi Ben,
Hopefully simple question:
If you were able to change configured aperture size - would you like to ?
I could possibly imaging situation where this is used to regular access to
the video memory, but you are the driver author..
thank you !
Was it always shared with the USB controller? Can you try changing that?
Some more info for both of you...
I remarked, in an earlier e-mail, that glxgears wouldn't cause the
lockups. That's not true. For whatever reason, it doesn't seem to
cause the lockups if I load the drm module with de
Hi !
I'm currently rewriting radeonfb to implement support for dual head, and
ultimately, to make it more friendly to be hooked on DRM for mesa-solo
style setups.
I have some issues however related to the way memory is mapped and
dealing with apertures. Here is the story, suggestions welcome:
Th
Dave Airlie wrote:
Odd. This is now happening, as well, with the drm from the 2.6.11 kernel.
The card works fine with the drivers from XiG, however, so it doesn't appear
to be a hardware problem.
wierd.. can you boot without X, and modprobe drm debug=1 then modprobe
radeon then start X? and s
Michel DÃnzer wrote:
On Sat, 2005-03-12 at 14:30 -0500, Adam K Kirchhoff wrote:
When trying neverputt:
[drm] Loading R200 Microcode
[drm:radeon_cp_reset] *ERROR* radeon_cp_reset called without lock held,
held 0
owner da0fcd80 d2809b80
Weird, does this only happen when running a 3D client,
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=2516
--- Additional Comments From [EMAIL PROTECTED] 2005-03-12 16:30 ---
(In r
On Sat, 2005-03-12 at 23:52 +0100, Jerome Glisse wrote:
> > Sounds like there could be problems with Paul's texture upload changes.
>
> Paul patch doesn't make its way to 2.6.11 ? Because Adam says he
> gots the same prob with 2.6.11 right ?
You removed the context this was referring to:
> > [..
>
> Odd. This is now happening, as well, with the drm from the 2.6.11 kernel.
> The card works fine with the drivers from XiG, however, so it doesn't appear
> to be a hardware problem.
>
wierd.. can you boot without X, and modprobe drm debug=1 then modprobe
radeon then start X? and send me on th
> Sounds like there could be problems with Paul's texture upload changes.
Paul patch doesn't make its way to 2.6.11 ? Because Adam says he
gots the same prob with 2.6.11 right ?
Jerome Glisse
---
SF email is sponsored by - The IT Product Guide
On Sat, 2005-03-12 at 14:30 -0500, Adam K Kirchhoff wrote:
>
> When trying neverputt:
>
> [drm] Loading R200 Microcode
> [drm:radeon_cp_reset] *ERROR* radeon_cp_reset called without lock held,
> held 0
> owner da0fcd80 d2809b80
Weird, does this only happen when running a 3D client, or also wit
Odd. This is now happening, as well, with the drm from the 2.6.11
kernel. The card works fine with the drivers from XiG, however, so it
doesn't appear to be a hardware problem.
Adam
Adam K Kirchhoff wrote:
On Friday I finally decided to reinstall debian on my box.. I started
with a fresh ins
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=2516
--- Additional Comments From [EMAIL PROTECTED] 2005-03-12 12:25 ---
Sorry
On Friday I finally decided to reinstall debian on my box.. I started
with a fresh install, and then upgraded to Xorg cvs... I grabbed the
latest Mesa from cvs, as well as the latest drm.
[drm] Initialized drm 1.0.0 20040925
[drm] Initialized radeon 1.15.0 20050208 on minor 0: ATI Technologies
16 matches
Mail list logo
