From: Vassilis Virvilis <vasvir@iit.demokritos.gr>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev and FB
Date: Tue, 16 May 2006 16:05:05 +0000 [thread overview]
Message-ID: <4469F831.5040107@iit.demokritos.gr> (raw)
In-Reply-To: <446972CB.6090909@iit.demokritos.gr>
Alexander E. Patrakov wrote:
>
> You overooked this:
>
> patrakov@home:~$ cat /etc/modprobe.d/display_class
> # This directive blacklists all devices which are members of the display
> class.
> # It has the main effect of stopping the udev/modprobe from loading the
> # fb drivers.
>
> # vendor, device, subsystem_vendor, subsystem_device, class, class, class
> install pci:v*d*sv*sd*bc03sc*i* /bin/true
>
Doh, indeed. However that means that udev calls modprobe and the modprobe
decides to not load the module right?
What I meant was that I looked at udev/etc/udev/debian/ of the udev src distribution.
I am doing embedded development and I don't have this file (directory actually).
Shouldn't it autoload the module in such a case?
Thanks anyway.
.bill
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x120709&bid&3057&dat\x121642
_______________________________________________
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:[~2006-05-16 16:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-16 6:35 udev and FB Vassilis Virvilis
2006-05-16 15:29 ` Alexander E. Patrakov
2006-05-16 15:33 ` Marco d'Itri
2006-05-16 16:05 ` Vassilis Virvilis [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=4469F831.5040107@iit.demokritos.gr \
--to=vasvir@iit.demokritos.gr \
--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).