All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephan von Krawczynski <skraw@ithnet.com>
To: jarausch@belgacom.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.13-pre6 breaks Nvidia's kernel module, or not?
Date: Mon, 22 Oct 2001 21:53:35 +0200	[thread overview]
Message-ID: <20011022215335.18a31d9d.skraw@ithnet.com> (raw)
In-Reply-To: <200110221846.f9MIkE416013@riker.skynet.be>
In-Reply-To: <200110221846.f9MIkE416013@riker.skynet.be>

On Mon, 22 Oct 2001 20:45:22 +0200 (CEST) jarausch@belgacom.net wrote:

> [...]
> Running pre6 I get
> (==) NVIDIA(0): Write-combining range (0xf0000000,0x2000000)
> (EE) NVIDIA(0): Failed to allocate LUT context DMA
> (EE) NVIDIA(0):  *** Aborting ***

Probably you should do additional checks. I run a GeForce II MX here with
exactly this driver and pre6 - and have no problem at all. I tried both driver
version 1251 and 1541, and both work.

Of course I do not back the manufacturers' religion "we don't wanna show people
how we managed to make a kernel driver 800kB of size". Only I believe this is
no real loss, as nobody wants to follow this god anyway.

:-)

Regards,
Stephan



  parent reply	other threads:[~2001-10-22 19:53 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-22 18:45 2.4.13-pre6 breaks Nvidia's kernel module jarausch
2001-10-22 18:51 ` Benjamin LaHaise
2001-10-22 18:51 ` Alexander Viro
2001-10-22 19:35 ` Rik van Riel
2001-10-22 19:46   ` Christopher Friesen
2001-10-22 19:53     ` Daniel T. Chen
2001-10-22 19:53 ` Stephan von Krawczynski [this message]
2001-10-22 20:24 ` Alan Cox
2001-10-22 22:27   ` drevil
2001-10-22 22:43     ` Charles Cazabon
2001-10-22 22:46     ` Doug McNaught
2001-10-22 22:50     ` Alan Cox
2001-10-23  1:31       ` drevil
2001-10-23  1:43         ` Michael H. Warfield
2001-10-23  2:16           ` drevil
2001-10-23  4:44             ` Nicholas Knight
2001-10-23  5:06               ` Cort Dougan
2001-10-23 11:36                 ` Rik van Riel
2001-10-23 16:13                 ` Alan Cox
2001-10-23  5:08               ` drevil
2001-10-23  5:18                 ` J Sloan
2001-10-23  5:59                 ` Nicholas Knight
2001-10-23  7:21                 ` Helge Hafting
2001-10-23  5:35           ` Matt D. Robinson
2001-10-23 16:16             ` Alan Cox
2001-10-23  9:50           ` David Woodhouse
2001-10-23 23:45             ` Ragnar Hojland Espinosa
2001-10-23  7:57         ` Alan Cox
2001-10-23 14:18           ` drevil
2001-10-23 16:01         ` Geert Uytterhoeven
2001-10-22 23:48     ` Jeff Golds
2001-10-22 23:53 ` Horst von Brand
2001-10-23  9:05 ` Jesper Juhl
2001-10-23 18:07   ` Josh McKinney
2001-10-23 22:51     ` J . A . Magallon
2001-10-24 21:06       ` Reid Hekman
2001-10-25  0:19         ` J . A . Magallon

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=20011022215335.18a31d9d.skraw@ithnet.com \
    --to=skraw@ithnet.com \
    --cc=jarausch@belgacom.net \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.