The question is, can we start ripping it out now, or will there be a
xfree86 4.5 and 4.6, etc.
Alex
--- Ian Romanick <[EMAIL PROTECTED]> wrote:
> Jens Owen wrote:
>
> > We can definitely remove the xf86drmCompat layer for XFree86 5.0.
> I
> > believe it's well understood that major version cha
In the Radeon driver, TCL is currently enabled by default. However, it seems
like there is no guarantee that the same set of vertices will be transformed
equally twice, so you get Z buffer artifacts when doing multipass rendering.
I am told that the DRI developers believes this is not a bug, be
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
[EMAIL PROTECTED] changed:
What|Removed |Added
---
On Fri, Oct 24, 2003 at 09:44:38AM -0700, Linus Torvalds wrote:
>
> On Thu, 23 Oct 2003, Jeff Garzik wrote:
>
> > /* Assign space for ROM resource if not already assigned. Ugly. */
> > if (!pci_resource_start(dev, PCI_ROM_RESOURCE))
> > if (pci_assign_resource(dev, PCI_R
I saw a few references to "dri-solo" on the mesa list, but didnt get to
read much on what it actually is.
What is it supposed to be?
I grepped through some of the recent dri-devel IRC logs, but didnt see
anything there either.
---
This SF.net
On Fri, Oct 24, 2003 at 11:34:04AM -0700, Jon Smirl wrote:
> PCI ROM enabale/disable has come up before on LKML. Russell made this comment
> about making the code more portable.
>
> --- Russell King <[EMAIL PROTECTED]> wrote:
> > You should use pcibios_resource_to_bus() to convert a resource to a
On Fri, Oct 24, 2003 at 06:57:18PM +0200, Petr Vandrovec wrote:
> We need something more sophisticated. Matrox's hardware has bits
> 31-16 readable/writable only if bit 0 is set to 1 (ROM enabled; you can
> (obviously) set bits 31-16 & 0 in one write). When ROM is disabled,
> bits 31-1 are always
On Fri, 2003-10-24 at 23:39, Mike A. Harris wrote:
> On Fri, 24 Oct 2003, Alex Deucher wrote:
>
> >Unless anyone says otherwise, I'm going to remove this code. All it
> >has done is generate complaints from MergedFB users. Apparently it
> >doesn't hurt anything (ie. cause a crash) to leave direc
On Fri, 2003-10-24 at 16:15, Alex Deucher wrote:
> The question is, can we start ripping it out now, or will there be a
> xfree86 4.5 and 4.6, etc.
Until there's an official roadmap for 5.x, I'd assume the next release
to be 4.x.
--
Earthling Michel Dänzer \ Debian (powerpc), XFree86 and DRI
I'll give keith's suggestion a shot, but I don't really understand how
it's supposed to work. I'm not really much of an expert when it comes
to the 3D driver. If someone could give me some pointers as to where
to look and maybe a 500 foot description of how it should work, I'll
see what I can com
Linus Torvalds writes:
> > could lead to problems with hotplug. XFree is also mapping PCI ROMs in without
> > informing the kernel and that can definitely cause problems.
>
> Absolutely. Changing PCI configurations without telling the kernel _will_
> cause problems. Especially for hotplug s
On Sat, 25 Oct 2003, Egbert Eich wrote:
>
> Speaking of XFree86: when I developed the PCI resource stuff in
> XFree86 I was trying to get support from kernel folks to get the
> appropriate user space interfaces into the kernel. When I got
> nowhere I decided to do everything myself.
There wo
I am unable to get direct 3d rendering working.
Not sure what info would help but...
I am running the 2.6.0-test8 kernel, and XFree86 4.3.99.14.
I have tried it with both the 2.6.0-test8 drm module and the one from
xfree86 4.3.99.14
System: Dual Athlon-XP 2000+ on a Tyan Tiger MPX S2466N-4M mot
--- Linus Torvalds <[EMAIL PROTECTED]> wrote:
> Quite frankly, I'd much rather see a low-level graphics driver that does
> _two_ things, and those things only:
>
> - basic hardware enumeration and setup (and no, "basic setup" does not
>mean "mode switching": it literally means things like doi
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] 2003-25-10 17:32 ---
I realize this may not
> Face it, a good graphics driver needs more than just "set up the ROM". It
> needs DMA access, and the ability to use interrupts. It needs a real
> driver.
>
> It basically needs something like what the DRI modules tend to do.
>
> I'd be really happy to have real graphics drivers in the kernel,
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] 2003-23-10 11:50 ---
I have done some some
17 matches
Mail list logo
