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 08:46:30 +0000 [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
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2004-02-02 8:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-26 21:50 [ANNOUNCE] udev 015 release Greg KH
2004-01-26 23:56 ` Greg KH
2004-01-27 5:52 ` Chris Friesen
2004-01-27 22:22 ` Greg KH
[not found] ` <1075351964.7680.12.camel@nosferatu.lan>
2004-01-29 21:54 ` Greg KH
[not found] ` <1075395125.7680.21.camel@nosferatu.lan>
2004-01-29 21:55 ` Greg KH
2004-01-31 3:17 ` Kay Sievers
[not found] ` <1075571697.7232.11.camel@nosferatu.lan>
2004-01-31 18:15 ` Kay Sievers
[not found] ` <1075573621.7232.14.camel@nosferatu.lan>
2004-01-31 18:39 ` Kay Sievers
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
[not found] ` <1075649046.24826.8.camel@nosferatu.lan>
2004-02-02 8:46 ` Prakash K. Cheemplavam [this message]
2004-02-01 22:52 ` hal daemon and ide-floppy J.A. Magallon
2004-02-02 3:16 ` Greg KH
2004-02-02 7:35 ` reflex
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-02 23:08 ` [ANNOUNCE] udev 015 release Prakash K. Cheemplavam
2004-02-02 23:11 ` Greg KH
[not found] ` <1075401020.7680.25.camel@nosferatu.lan>
2004-02-02 23:32 ` 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;
as well as URLs for NNTP newsgroup(s).