Re: [arch-general] [arch-dev-public] [signoff] udev 118-4

2008-03-10 Thread Aaron Griffin
On Sun, Mar 9, 2008 at 6:36 PM, Michal Soltys <[EMAIL PROTECTED]> wrote: > Aaron Griffin wrote: > > On Sun, Mar 9, 2008 at 3:05 AM, Michal Soltys <[EMAIL PROTECTED]> wrote: > >> ENV{MODALIAS}=="modaliases #1", OPTION="ignore_device" > >> ENV{MODALIAS}=="modaliases #2", OPTION="ignore_device" >

Re: [arch-general] [arch-dev-public] [signoff] udev 118-4

2008-03-09 Thread Michal Soltys
Aaron Griffin wrote: On Sun, Mar 9, 2008 at 3:05 AM, Michal Soltys <[EMAIL PROTECTED]> wrote: ENV{MODALIAS}=="modaliases #1", OPTION="ignore_device" ENV{MODALIAS}=="modaliases #2", OPTION="ignore_device" This is way more complex than you think it is. Let me explain. A typical module exposes

Re: [arch-general] [arch-dev-public] [signoff] udev 118-4

2008-03-09 Thread Aaron Griffin
On Sun, Mar 9, 2008 at 3:05 AM, Michal Soltys <[EMAIL PROTECTED]> wrote: > ENV{MODALIAS}=="modaliases #1", OPTION="ignore_device" > ENV{MODALIAS}=="modaliases #2", OPTION="ignore_device" This is way more complex than you think it is. Let me explain. A typical module exposes it's aliases WITH wil

Re: [arch-general] [arch-dev-public] [signoff] udev 118-4

2008-03-09 Thread Xavier
On Sun, Mar 09, 2008 at 10:05:04AM +0100, Michal Soltys wrote: > Btw - is there any reason why fbcon is built into kernel, instead of being > left as a module (also, fbcon never loads automatically) ? Consoles are not > taken until fbcon is activated - so maybe it would solve the issue with > bi

Re: [arch-general] [arch-dev-public] [signoff] udev 118-4

2008-03-09 Thread Michal Soltys
You can block frambuffer in udev, but you have to block the driver by its modalias or other attributes (similary as if you tried to block sound through udev). For example, following rule would do the thing in my case, on one of my machines (that has some old ati card): SUBSYSTEM=="pci", ATTR{ven