http://bugme.osdl.org/show_bug.cgi?id=2754
--- Additional Comments From [EMAIL PROTECTED] 2004-07-20 00:48 ---
Yes, this is exactly the problem now.
OK.
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.
Okay my final attempt :-) is now checked in...
the last issue that register_chrdev returns a 0 when the fops is the same
caused your last problem.. hopefully this work..
if you can load/unload this module and see if it works... then I'll add
the couple of lines to hopefully avoid using the secon
On Mon, 19 Jul 2004 15:08:11 -0400
Alex Deucher <[EMAIL PROTECTED]> wrote:
> On 19 Jul 2004 19:34:19 +0200, Juliusz Chroboczek <[EMAIL PROTECTED]> wrote:
[snip]
> >
> > There are just two minor issues. I've managed to get it to lockup
> > twice (X server frozen with 100% cpu, the system can be r
I know we spoke of this before and a big bunch of these just appeared in
the mainline tree and I want to merge them back into CVS...
For now my thinking is BSD doesn't use __user so we just go ahead and use
it and if later it stars being used for something else on another platform
we can search/r
> > > The other issue is more annoying: there is visual noise whenever there
> > > is significant OpenGL activity in a full-screen window
Transient noisy bars two or three pixel wide. What surprises me is
that I've seen them both vertical and horizontal.
> TwisterK has a lower memory bandwidth.
I have a working direct rendering mechanism in my 64-bit userland. However,
32-bit software running in a 32-bit chroot environment cannot operate with the
64-bit drm. I get the following error when executing the 32-bit glxinfo inside
the chroot:
# /usr/X11R6/bin/glxinfo
name of display: :0.0
libGL
ATI Rage 128 and Radeon DRM unconditionally depend on PCI
Signed-off-by: Geert Uytterhoeven <[EMAIL PROTECTED]>
--- linux-2.6.8-rc2/drivers/char/drm/Kconfig2004-07-15 23:14:12.0 +0200
+++ linux-m68k-2.6.8-rc2/drivers/char/drm/Kconfig 2004-07-19 18:15:58.0
+0200
@@ -31,7
Dave Airlie wrote:
> Okay my final attempt :-) is now checked in...
>
> the last issue that register_chrdev returns a 0 when the fops is the same
> caused your last problem.. hopefully this work..
>
> if you can load/unload this module and see if it works... then I'll add
> the couple of lines to
