linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vassilis Virvilis <vasvir@iit.demokritos.gr>
To: linux-hotplug@vger.kernel.org
Subject: udev and FB
Date: Tue, 16 May 2006 06:35:55 +0000	[thread overview]
Message-ID: <446972CB.6090909@iit.demokritos.gr> (raw)

Hi,

although I watch this list rather closely, I have never seen mentioned
the FB subsystem. Is udev supposed to autoload it? I certainly understand
this is not desirable in most cases but it is in my case.

I looked around the debian rules and didn't find anything that blacklists
FB devices. So I am guessing that it requires rules in order to autoload it.
Is that true? Any other pointers to the right direction, for example similar
rules that happen to work ok for other type of hardware?

The rest of my hardware is correctly initialized, modules are autoloaded
and devices not are created.

     .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

             reply	other threads:[~2006-05-16  6:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-16  6:35 Vassilis Virvilis [this message]
2006-05-16 15:29 ` udev and FB Alexander E. Patrakov
2006-05-16 15:33 ` Marco d'Itri
2006-05-16 16:05 ` Vassilis Virvilis

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=446972CB.6090909@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).