Hi, Dave.
Dave Airlie wrote:
AllowInsecureDRI is less secure than forcing users to run things as root
or fix the code. And we want that code in kernel and causing pain in
order to make people fix it 8)
I'm really with Keiths don't let them do anything until someone fixes it
On Mon, 2004-10-11 at 13:12, Dieter Nützel wrote:
> Am Montag, 11. Oktober 2004 14:36 schrieb Marcello Maggioni:
> > On Sun, 10 Oct 2004 23:27:38 +0200, Dieter Nützel
> > <[EMAIL PROTECTED]> wrote:
>
> > > UT2003
> > > Some broken textures on the walls and floors (Temple of Anubis).
> > > 'shock r
On Mon, 2004-10-11 at 18:37 -0700, Ian Romanick wrote:
> I was trying to test the latest version of my ReadPixels work to make
> sure I didn't break anything on big-endian. However, it seems someone
> beat me to it in the Rage128 driver. :) In a nutshell, I can get one
> frame of gears, and th
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://freedesktop.org/bugzilla/show_bug.cgi?id=1220
--- Additional Comments From [EMAIL PROTECTED] 2004-10-11 21:17 ---
This really
I just split out heads as a separate data structure from drm_device. I
gave this a couple of hours of testing in different configurations but
I may have missed something. Please let me know.
I probably haven't figured out all of the variables that need to be
moved from drm_device to drm_head. If a
Dave Airlie wrote:
An issue raised by DRM people with the new drm core is how to stop users
shotting themselves in the foot when upgrading drm modules from CVS and
mixing up cores and drivers...
This patch (against DRM CVS) proposes a simple internal version that gets
passed from the module to the
I was trying to test the latest version of my ReadPixels work to make
sure I didn't break anything on big-endian. However, it seems someone
beat me to it in the Rage128 driver. :) In a nutshell, I can get one
frame of gears, and then the 3D engine is toast. After that frame is
drawn, gears i
VGA_DDC_CLK_OUT_EN is defined in linux/include/video/radeon.h
It should be part of the normal kernel build environment.
--
Jon Smirl
[EMAIL PROTECTED]
---
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products
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://freedesktop.org/bugzilla/show_bug.cgi?id=1220
[EMAIL PROTECTED] changed:
What|Removed |Added
Hi, me again :)
I've reached some further steps now (thanks Karl and Felix), but I've
run into a new error (well, 4 actually).
[EMAIL PROTECTED]:/home/steven/Downloads/DRI/drm/linux-2.6# make
LINUXDIR=/usr/src/linux-2.6.2 DRM_MODULES="r200 radeon"
/home/steven/Downloads/DRI/drm/linux-2.6/radeon
(II) RADEON(0): [drm] added 1 reserved context for kernel
(EE) RADEON(0): [dri] RADEONDRIScreenInit failed because of a version mismatch.
[dri] radeon.o kernel module version is 1.11.0 but version 1.11.1 or newer is needed.
[dri] Disabling DRI.
[...]
Is there a patch for FreeBSD's /sys/dev/drm some
>
> AllowInsecureDRI is less secure than forcing users to run things as root
> or fix the code. And we want that code in kernel and causing pain in
> order to make people fix it 8)
>
I'm really with Keiths don't let them do anything until someone fixes it
.. makes life easier.. I don't think havin
> I was poking through the code for i915 DRM, trying to find the source of the
> resume failure. It looks like the i915_resume function can't be called by
> anything -- am I wrong about this? If I'm right, how should it be enabled?
I think Keith will have to answer this one .. there was a suspici
On Sun, 10 Oct 2004 22:19:18 -0400
Adam Jackson <[EMAIL PROTECTED]> wrote:
> On Sunday 10 October 2004 17:45, Felix Kühling wrote:
> > On Sun, 10 Oct 2004 22:01:30 +0200 David <[EMAIL PROTECTED]> wrote:
> >
> > [snip]
> >
> > > > They are forwards compatible but not backwards compatible. 4.4 modu
Hey,
I was poking through the code for i915 DRM, trying to find the source of
the resume failure. It looks like the i915_resume function can't be
called by anything -- am I wrong about this? If I'm right, how should it
be enabled?
Regardless, I have some doubts about the allocation made using
On Mon, 11 Oct 2004 14:54:07 -0400 (EDT)
Karl Rasche <[EMAIL PROTECTED]> wrote:
>
> > shader/arbprogparse.c:3630: stray '\240' in program
>
> I think this stems from the line
>
> #define ARB_DRAW_BUFFERS ï0x80
>
> around line 175-ish. It looks like, at least in the CVS browsing, that
> there
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://freedesktop.org/bugzilla/show_bug.cgi?id=1220
--- Additional Comments From [EMAIL PROTECTED] 2004-10-11 14:04 ---
The patch i
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://freedesktop.org/bugzilla/show_bug.cgi?id=1220
--- Additional Comments From [EMAIL PROTECTED] 2004-10-11 13:39 ---
can anyone
On Mon, 11 Oct 2004 22:12:25 +0200, Dieter Nützel
<[EMAIL PROTECTED]> wrote:
> Am Montag, 11. Oktober 2004 14:36 schrieb Marcello Maggioni:
> > On Sun, 10 Oct 2004 23:27:38 +0200, Dieter Nützel
> > <[EMAIL PROTECTED]> wrote:
>
> > > UT2003
> > > Some broken textures on the walls and floors (Temple
Am Montag, 11. Oktober 2004 14:36 schrieb Marcello Maggioni:
> On Sun, 10 Oct 2004 23:27:38 +0200, Dieter Nützel
> <[EMAIL PROTECTED]> wrote:
> > UT2003
> > Some broken textures on the walls and floors (Temple of Anubis).
> > 'shock rifle' is OK
> > 'Exit' dito.
-> Exit IS broken.
> > UT2004
> >
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://freedesktop.org/bugzilla/show_bug.cgi?id=1220
--- Additional Comments From [EMAIL PROTECTED] 2004-10-11 13:05 ---
*** Bug 159
> On Fri, 8 Oct 2004, Eric Anholt wrote:
>
> > On Fri, 2004-10-08 at 11:17, Mikhail Teterin wrote:
> >> Hi, Eric!
> >>
> >> Can this be assigned back to you? I have another pair of PCI IDs,
> >> BTW, and I am sure, there are people with shiny new Radeon-9800 out
> >> there too... Yours,
> >
> > Th
Hi,
1-bit fields should be unsigned (i.e., no sign bit).
Sparse also complains about them, as in:
drivers/char/drm/sis_ds.h:88:12: warning: dubious one-bit signed bitfield
drivers/char/drm/sis_ds.h:89:16: warning: dubious one-bit signed bitfield
Is current linux-2.6.9-bk tree anything close to DRM
> shader/arbprogparse.c:3630: stray '\240' in program
I think this stems from the line
#define ARB_DRAW_BUFFERS ï0x80
around line 175-ish. It looks like, at least in the CVS browsing, that
there is a bunch of odd crap between the end of ..._BUFFERS and 0x80.
Karl
-
Hi,
I've got an error while building the DRI. It happens when I want to
build the Mesa 3D drivers for Linux (I'm following this page:
http://dri.sourceforge.net/cgi-bin/moin.cgi/Building).
[EMAIL PROTECTED]:~/Downloads/DRI/Mesa$ make linux-dri-x86
gcc -c -I../../include -I../../src/mesa -I../..
This is just a friendly reminder that the weekly dri-devel IRC meeting will
be starting in the #dri-devel channel on irc.freenode.net at 2100 UTC (or
5:00PM EDT or 2:00PM PDT, if you prefer).
Time zone conversion available at:
http://www.timezoneconverter.com/cgi-bin/tzc.tzc
Logs of previous IR
On Mon, 11 Oct 2004 11:56:27 +0100, José Fonseca
<[EMAIL PROTECTED]> wrote:
> I've checked on another machine, with the same kernel but different
> hardware and kernel configuration, and it does works fint. I don't
> suppose any processor-specific assembly was added to the *-core, so I'm
> inclined
On Llu, 2004-10-11 at 09:42, Thomas HellstrÃm wrote:
> So what is your actual suggestion?
> Export read-write as default or, as proposed, export read-write when
> "AllowInsecureDRI" is enabled in the X server config?
AllowInsecureDRI is less secure than forcing users to run things as root
or fix t
On Mon, 11 Oct 2004 11:44:52 +0800, Bill Gou <[EMAIL PROTECTED]> wrote:
> after a software suspend/resume cycle, running glxgears emits the following error
> msgs and
> quits:
With the semi-exception of the radeon driver, none of the 3d drivers
support suspend/resume.
Alex
>
> libGL warning:
On Sun, 10 Oct 2004 23:27:38 +0200, Dieter Nützel
<[EMAIL PROTECTED]> wrote:
ì
> GREAT progress.
>
> DOOM3 is working with TCL, little to dark, but...;-)
>
> Celestia 'Earth'->'ISS' have light in the windows, now.
> But some flickering on the sun paddels left.
>
> Quake3
> quake3.x86 and quake3-
On Wed, Oct 06, 2004 at 05:51:41PM -0400, Jon Smirl wrote:
> For debug info:
> insmod ./drm.ko drm_opts=debug:on
> insmod ./radeon.ko drm_opts=debug:on
>
> I haven't fully writen the code for the new parameters yet. When it is
> finished the message will disappear.
>
> Make sure you don't have
Thomas Hellström wrote:
Hi, Keith!
Thomas Hellström wrote:
Hi!
Sorry for the double posting. This is a thing that needs to be discussed
in both communities.
The via DRM has started it's journey into the linus kernel, but the 3D
driver / DDX still suffers
from a security flaw:
When the MMIO area is
Hi, Keith!
> Thomas Hellström wrote:
>> Hi!
>>
>> Sorry for the double posting. This is a thing that needs to be discussed
>> in both communities.
>>
>> The via DRM has started it's journey into the linus kernel, but the 3D
>> driver / DDX still suffers
>> from a security flaw:
>>
>> When the MMIO
Thomas Hellström wrote:
Hi!
Sorry for the double posting. This is a thing that needs to be discussed
in both communities.
The via DRM has started it's journey into the linus kernel, but the 3D
driver / DDX still suffers
from a security flaw:
When the MMIO area is exported read-write it is assum
Bill Gou wrote:
after a software suspend/resume cycle, running glxgears emits the following error msgs
and
quits:
libGL warning: 3D driver claims to not support visual 0x22
libGL warning: 3D driver claims to not support visual 0x23
libGL warning: 3D driver claims to not support visual 0x26
libGL w
35 matches
Mail list logo
