From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: framebuffer node and whatnot...
Date: Thu, 18 Mar 2004 01:19:06 +0000 [thread overview]
Message-ID: <20040318011906.GE26257@kroah.com> (raw)
In-Reply-To: <BAY2-F60SMVK4IZZOjv0002b9e9@hotmail.com>
On Wed, Mar 17, 2004 at 01:26:50AM -0500, Alexander Zapatka wrote:
> just wondering what the status of the frambuffer device node problem is...
The fb driver authors have not finished implementing this yet. When
they finally get there, udev will work with it.
Sorry about this, but it's not a udev issue.
> also, lirc is working on udev support... if the lirc people add sysfs stuff
> to their patch, should udev work out of the box? or does udev need info
> for creating a device like lirc0 ?
Once the sysfs support is in the kernel, udev will just work out of the
box and assign the kernel names to the devices. If you want to move
them to a subdirectory, or rename them, then you will need to create a
udev rule for it.
thanks,
greg k-h
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&op=click
_______________________________________________
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
prev parent reply other threads:[~2004-03-18 1:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-17 6:26 framebuffer node and whatnot Alexander Zapatka
2004-03-18 1:19 ` Greg KH [this message]
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=20040318011906.GE26257@kroah.com \
--to=greg@kroah.com \
--cc=linux-hotplug@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).