linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Reid Hekman <reid.hekman@ndsu.nodak.edu>
To: linux-kernel@vger.kernel.org
Cc: Dan Maas <dmaas@dcine.com>, jamagallon@able.es
Subject: Re: 2.4.13-pre6 breaks Nvidia's kernel module
Date: Wed, 24 Oct 2001 23:15:02 -0500	[thread overview]
Message-ID: <3BD791C6.70200@ndsu.nodak.edu> (raw)
In-Reply-To: <fa.fm7f5dv.1cn8eg6@ifi.uio.no> <fa.hbvlhav.v369au@ifi.uio.no> <023001c15cf4$4fd5ecc0$1a01a8c0@allyourbase>

Dan Maas wrote:

>>As I see it, that is exactly what should not be done. Lets suppose you are
>>running 2.4.12. You want to upgrade. So you unpack 2.4.13 and build it.
>>If you go now to build nVidia drivers, with the shipped Makefile they
>>still build and install against 2.4.12.
>>
> 
> You don't have to reboot into the new kernel, just do as the README says:
> 
>     If you want to build NVdriver for a system other than the compiling
>     system, then you'll need to run the make as:
> 
>         $ make SYSINCLUDE=/src/kern/my-smp-kernel/include
> 
>     to generate an NVdriver that will work on the kernel whose include
>     files are in /src/kern/my-smp-kernel/include.  This kernel must
>     have been completely configured (make menuconfig dep).
> 
> So you still only need to reboot once when upgrading your kernel.
> 
> The only thing I find annoying is that the kernel's 'make modules_install'
> wipes out /lib/modules/<version>, so when I'm in the compile/debug cycle on
> my own driver I have to keep reinstalling NVdriver.
> 
> Regards,
> Dan


Thanks for the info. I hadn't looked at the makefile myself, but now 
that you mention it do remember the SYSINCLUDE directive from before.

For me personally, I've always booted in runlevel 3, so it's no problem 
for me to recompile NVdriver after the reboot. To each his own I guess.

Regards,
Reid


       reply	other threads:[~2001-10-25  4:17 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.fm7f5dv.1cn8eg6@ifi.uio.no>
     [not found] ` <fa.hbvlhav.v369au@ifi.uio.no>
     [not found]   ` <023001c15cf4$4fd5ecc0$1a01a8c0@allyourbase>
2001-10-25  4:15     ` Reid Hekman [this message]
2001-10-23 12:37 2.4.13-pre6 breaks Nvidia's kernel module Jesse Pollard
  -- strict thread matches above, loose matches on Subject: below --
2001-10-23  9:52 PVotruba
2001-10-23  1:50 BH
2001-10-22 18:45 jarausch
2001-10-22 18:45 jarausch
2001-10-22 18:45 jarausch
2005-01-13 16:19 ` Arjan van de Ven
2005-01-13 16:50 ` Valdis.Kletnieks
2005-01-13 17:25 ` Zan Lynx
2005-01-13 17:38 ` Zwane Mwaikambo
2001-10-22 18:45 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 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=3BD791C6.70200@ndsu.nodak.edu \
    --to=reid.hekman@ndsu.nodak.edu \
    --cc=dmaas@dcine.com \
    --cc=jamagallon@able.es \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).