public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Prakash K. Cheemplavam" <PrakashKC@gmx.de>
To: Martin Schlemmer <azarah@gentoo.org>
Cc: Linux Kernel Mailing Lists <linux-kernel@vger.kernel.org>,
	Sam Ravnborg <sam@ravnborg.org>,
	linux-hotplug-devel@lists.sourceforge.net,
	Greg KH <greg@kroah.com>,
	zander@mail.minion.de
Subject: Re: [ANNOUNCE] udev 015 release
Date: Mon, 02 Feb 2004 09:46:30 +0100	[thread overview]
Message-ID: <401E0E66.4040905@gmx.de> (raw)
In-Reply-To: <1075649046.24826.8.camel@nosferatu.lan>

Martin Schlemmer wrote:
> On Fri, 2004-01-30 at 19:23, Greg KH wrote:
> 
>>On Fri, Jan 30, 2004 at 05:45:41PM +0100, Prakash K. Cheemplavam wrote:
>>
>>>Hi Greg,
>>>
>>>perhaps you remember me being a gentoo user wanting to switch to udev. 
>>>Well I did so, but am having some problems:
>>>
>>>1.) Minor one: Nodes for Nvidia (I am using binary display modules 
>>>1.0.5328) ar not created. I have to do it by hand each start-up (written 
>>>into loacal.start.):
>>>mknod /dev/nvidia0 c 195 0
>>>mknod /dev/nvidiactl c 195 255
>>
>>Heh, and you expect me to be able to modify a binary driver to work with
>>udev how?  :)
>>
>>You're on your own here...
>>
> 
> 
> No offense, but you guys sometimes really see things as too black and
> white :)
> 
> Its only the high level api calls that are in binary object files, but
> the main interface to the kernel is source that needs compiling.  I have
> a patch attached here that adds basic sysfs support via the class_simple
> functions.

I just reemerged the nvidia-kernel which seems to incorporate your 
patcxh and yes, it works nicely. :-)

Prakash

  reply	other threads:[~2004-02-02  8:46 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-26 21:50 [ANNOUNCE] udev 015 release Greg KH
2004-01-26 22:15 ` Tomasz Torcz
2004-01-27  5:52 ` Chris Friesen
2004-01-27 22:22   ` Greg KH
2004-01-29  4:52 ` Martin Schlemmer
2004-01-29 21:54   ` Greg KH
2004-01-29 16:52 ` Martin Schlemmer
2004-01-29 21:55   ` Greg KH
2004-01-31  3:17     ` Kay Sievers
2004-01-31 17:54       ` Martin Schlemmer
2004-01-31 18:15         ` Kay Sievers
2004-01-31 18:27           ` Martin Schlemmer
2004-01-31 18:39             ` Kay Sievers
2004-01-31 18:47               ` Martin Schlemmer
2004-01-29 18:30 ` Martin Schlemmer
2004-01-30  4:41   ` Martin Schlemmer
2004-02-02 23:32   ` Greg KH
2004-02-03  4:12     ` Martin Schlemmer
2004-01-30 16:45 ` Prakash K. Cheemplavam
2004-01-30 17:23   ` Greg KH
2004-01-30 17:44     ` Prakash K. Cheemplavam
2004-01-30 17:49       ` Greg KH
2004-01-30 18:17         ` Prakash K. Cheemplavam
2004-02-01 15:24     ` Martin Schlemmer
2004-02-02  8:46       ` Prakash K. Cheemplavam [this message]
2004-01-30 17:33   ` Martin Schlemmer
2004-01-30 18:03   ` Andre Noll
2004-01-30 23:06     ` Tom Rini
2004-02-02 21:43       ` Greg KH
2004-02-05  0:31         ` [2.6 patch] remove USB_SCANNER Adrian Bunk
2004-02-05  1:14           ` Greg KH
2004-02-05 17:20             ` Azog
2004-02-05 17:30               ` Greg KH
2004-02-05 17:50                 ` Stian Jordet
2004-02-05 17:57                   ` Greg KH
2004-02-05 20:24                 ` Leopold Gouverneur
2004-02-05 21:15                   ` Stian Jordet
2004-02-05 21:36                     ` Leopold Gouverneur
2004-02-06  1:15               ` Gene Heskett
2004-02-06 20:59                 ` Bill Davidsen
2004-02-06 21:04                   ` Greg KH
2004-02-01 22:52 ` hal daemon and ide-floppy J.A. Magallon
2004-02-02  3:16   ` Greg KH
2004-02-02 22:32 ` udev depends on /usr J.A. Magallon
2004-02-02 22:44   ` Greg KH
2004-02-02 23:01     ` J.A. Magallon
2004-02-03  4:10     ` Martin Schlemmer
2004-02-02 23:08 ` [ANNOUNCE] udev 015 release Prakash K. Cheemplavam
2004-02-02 23:11   ` Greg KH

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=401E0E66.4040905@gmx.de \
    --to=prakashkc@gmx.de \
    --cc=azarah@gentoo.org \
    --cc=greg@kroah.com \
    --cc=linux-hotplug-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=zander@mail.minion.de \
    /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