public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Erik Andersen <andersen@codepoet.org>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Mitch@0Bits.COM,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	hch@lst.de
Subject: Re: Linux 2.4.22-pre10-ac1 DRI doesn't work with
Date: Thu, 7 Aug 2003 13:23:01 -0600	[thread overview]
Message-ID: <20030807192301.GA9494@codepoet.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0308071023040.6818-200000@logos.cnet>

On Thu Aug 07, 2003 at 10:27:03AM -0300, Marcelo Tosatti wrote:
> > That doesn't seem a 2.4.22 candidate thing to me. If vmap broke the DRI
> > then the vmap patch wants reverting for 2.4.22 IMHO, and looking at for
> > 2.4.23.
> 
> I dont understand how the vmap change can break DRM. 
> 
> The vmap patch only changes internal mm/vmalloc.c code (vmalloc() call
> acts exactly the same way as before AFAICS).
> 
> Anyway, Mitch (or Erik who's seeing the problem), can please revert the
> vmap() change to check if its causing the mentioned problem? 
> 
> The patch is attached. Apply it with -R.

Reverting this patch has no effect on the problem....

    $ glxgears 
    Illegal instruction

same as before,

As a guess, the "Unknown" in the drm detection below could
be related to my problem....  As could the fact I have 2 GB
ram installed.  Or the fact I'm running SMP.  dunno.


Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 1919M
agpgart: Detected Intel(R) 865G chipset
agpgart: AGP aperture is 64M @ 0xf8000000
[----------snip-----------]
[drm] AGP 0.99 on Unknown @ 0xf8000000 64MB
[drm] Initialized radeon 1.1.1 20010405 on minor 0



00:01.0 PCI bridge: Intel Corp. 82865G/PE/P Processor to AGP Controller (rev 02) (prog-if 00 [Normal decode])
        Flags: bus master, 66Mhz, fast devsel, latency 64
        Bus: primary=00, secondary=01, subordinate=01, sec-latency=64
        I/O behind bridge: 0000c000-0000cfff
        Memory behind bridge: fe800000-fe8fffff
        Prefetchable memory behind bridge: e7e00000-f7dfffff

01:00.0 VGA compatible controller: ATI Technologies Inc Radeon RV100 QY [Radeon 7000/VE] (prog-if 00 [VGA])
        Subsystem: PC Partner Limited RV100 QY [Sapphire Radeon VE 7000]
        Flags: bus master, stepping, 66Mhz, medium devsel, latency 64, IRQ 16
        Memory at e8000000 (32-bit, prefetchable) [size=128M]
        I/O ports at c000 [size=256]
        Memory at fe8f0000 (32-bit, non-prefetchable) [size=64K]
        Expansion ROM at fe8c0000 [disabled] [size=128K]
        Capabilities: [58] AGP version 2.0
        Capabilities: [50] Power Management version 2


 -Erik

--
Erik B. Andersen             http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--

  parent reply	other threads:[~2003-08-07 19:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-06 14:38 Linux 2.4.22-pre10-ac1 DRI doesn't work with Mitch
2003-08-07 11:44 ` Alan Cox
2003-08-07 13:27   ` Marcelo Tosatti
2003-08-07 14:26     ` Christoph Hellwig
2003-08-07 14:27       ` Alan Cox
2003-08-07 14:47       ` Marcelo Tosatti
2003-08-07 15:37         ` Christoph Hellwig
2003-08-07 17:23       ` Kernel 2.6.0-test2 vs 2.2.12 -- Some observations J.C. Wren
2003-08-07 17:34         ` Andrew Morton
2003-08-07 18:44           ` J.C. Wren
2003-08-08 12:16         ` Alan Cox
2003-08-07 19:23     ` Erik Andersen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-08-07 19:34 Linux 2.4.22-pre10-ac1 DRI doesn't work with Mitch
2003-08-05 19:37 Mitch
2003-08-05 20:36 ` Erik Andersen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030807192301.GA9494@codepoet.org \
    --to=andersen@codepoet.org \
    --cc=Mitch@0Bits.COM \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox