Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter your comments there.
http://bugs.xfree86.org/show_bug.cgi?id=314
--- Additional Comments From [EMAIL PROTECTED] 2004-04-19 03:12 ---
I have uploaded
Dave Airlie wrote:
Okay I've come up with a method for generating the pci ids stuff for the
DRM for Linux and BSD,
put a txt file in shared or the format
[cardname]
vendid devid namestring
have two scripts in the scripts directory ones to create a linux
drm_pciids.h file of the format
#define
These PCI changes duplicate things that are in framebuffer. Shouldn't we be
having a giant argument about them? I would think that is worse that DRM is is
duplicating something in FB. The two IOCTLs I needed for reset don't exist in
either FB or DRM. Anyway I think these changes need to go in. The
Jon Smirl wrote:
These PCI changes duplicate things that are in framebuffer. Shouldn't we be
having a giant argument about them? I would think that is worse that DRM is is
Heh...you sure do like to start fights, don't you? :)
duplicating something in FB. The two IOCTLs I needed for reset don't
Am 2004.04.19 00:51:16 +0200 schrieb(en) Michel Dänzer:
On Mon, 2004-04-19 at 00:29, Andreas Stenglein wrote:
After setting tcl_mode to 0, glxgears and quake3 didnt work as expected.
glxgears looks like http://penguinppc.org/~daenzer/DRI/glxgears.png
here; if I press the cursor keys, the
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
4:00PM EST or 1:00PM PST, if you prefer).
Time zone conversion available at:
http://www.timezoneconverter.com/cgi-bin/tzc.tzc
Logs of previous
Keith Whitwell wrote:
Ian Romanick wrote:
This is what I have done so far to convert the R200 driver to use
t_vertex. It is only a conversion for SW TCL, and it's not quite
complete. I've managed to clean up all the crashes that I could find,
but I've only tested with gears, geartrain, and
Ian Romanick wrote:
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
4:00PM EST or 1:00PM PST, if you prefer).
Gak! My brain must be serious dysfunctional...5:00PM PDT or 2:00PM PDT.
Time zone
On Llu, 2004-04-19 at 17:00, Jon Smirl wrote:
These PCI changes duplicate things that are in framebuffer. Shouldn't we be
having a giant argument about them? I would think that is worse that DRM is is
duplicating something in FB. The two IOCTLs I needed for reset don't exist in
either FB or
--- Ian Romanick [EMAIL PROTECTED] wrote:
Can you elaborate? I'm not super familiar with this part of the DRM, so
I just need a clarification. We're just talking about device
initialization (i.e., PCI mapping) that the X-server currently does, right?
I'm not proprosing bringing any family
--- Alan Cox [EMAIL PROTECTED] wrote:
For the 2D side I don't think its an ioctl problem as it is driven
by the power management hooks. For 3D I can see it being relevant since
you may want to reset the 3D engine from user space when the X server
decides we have a failure, either by doing the
--- Ian Romanick [EMAIL PROTECTED] wrote:
Jon Smirl wrote:
These PCI changes duplicate things that are in framebuffer. Shouldn't
we be
having a giant argument about them? I would think that is worse that
DRM is is
Heh...you sure do like to start fights, don't you? :)
duplicating
Am 2004.04.19 20:09:29 +0200 schrieb(en) Keith Whitwell:
Andreas Stenglein wrote:
[...]
it's almost the same here on x86: only the colors look a bit different.
red corners, blue ring, black middle
If you change the shape of the glxgears-window to widescreen
you will see something
--- Alan Cox [EMAIL PROTECTED] wrote:
If they are needed then probably the basic video restore for fb modes
belongs in the FB driver, and the 3D engine restore in the dri driver.
That way users get the pieces they need. In time once we have a
consistent video layer it will tidy up.
Do you
On Mon, 2004-04-19 at 18:00, Jon Smirl wrote:
These PCI changes duplicate things that are in framebuffer. Shouldn't we be
having a giant argument about them? I would think that is worse that DRM is is
duplicating something in FB. The two IOCTLs I needed for reset don't exist in
either FB or
These PCI changes duplicate things that are in framebuffer. Shouldn't we be
having a giant argument about them? I would think that is worse that DRM is is
duplicating something in FB. The two IOCTLs I needed for reset don't exist in
either FB or DRM. Anyway I think these changes need to go
All drivers except savage emit the Direct rendering disabled message as an
informational message; savage makes it an error. Technically it's not an
error, since the server can continue, but it should probably be at least a
warning. This would make troubleshooting easier, because users know to
On Tue, 2004-04-20 at 02:13, ajax wrote:
All drivers except savage emit the Direct rendering disabled message as an
informational message; savage makes it an error. Technically it's not an
error, since the server can continue, but it should probably be at least a
warning. This would make
--- Dave Airlie [EMAIL PROTECTED] wrote:
the Linux probe failed did I fallback to the manual scheme. A parallel
method
could be used on BSD. The only reason you need the manual scheme is if FB is
already loaded and has the PCI ID registered.
You want to use the kernel probe scheme
already loaded and has the PCI ID registered.
You want to use the kernel probe scheme first. If the kernel probe suceeds
it
will mark the hardware in use. The fallback scheme is a trick to use the
hardware without informing the kernel.
yes but it is also the current behaviour
--- Dave Airlie [EMAIL PROTECTED] wrote:
simple behaviour is different, no idea if anyone relies on it ..
modprobe radeon
modprobe radeonfb
will not longer work the same with the new system, be it stupid/broken
etc,, there is potential difference in a stable kernel series, what
happens
i finally got dri working, but... i'm using 2.6.5 on x86 (dual opteron
mobo with a single cpu). i have an agp 9200 and i'm using xfree 4.3.0.
whenever i scroll or sometimes when inputing text, i get these white
horizontal lines that appear in random spots for a split second. this
happens in the
22 matches
Mail list logo
