Julien Cristau wrote:
> On Mon, Jan 25, 2010 at 00:27:48 +, Ben Hutchings wrote:
>
> > What about my suggestion of removing the MODULE_DEVICE_TABLE
> > declarations from fb modules, so they do not appear in modules.pcimap
> > etc? Did you see any problem with that?
> >
> Dropping those and u
On Mon, Jan 25, 2010 at 00:27:48 +, Ben Hutchings wrote:
> What about my suggestion of removing the MODULE_DEVICE_TABLE
> declarations from fb modules, so they do not appear in modules.pcimap
> etc? Did you see any problem with that?
>
Dropping those and udev's blacklist would be fine as far
On Mon, 2010-01-25 at 00:56 +0100, Julien Cristau wrote:
> On Tue, Jan 12, 2010 at 01:34:45 +0100, Marco d'Itri wrote:
>
> > On Jan 12, Julien Cristau wrote:
> >
> > > Marco, what do you think of switching to this, or at least using its fb
> > > part?
> > I do not mind explicitly blacklisting ea
On Tue, Jan 12, 2010 at 01:34:45 +0100, Marco d'Itri wrote:
> On Jan 12, Julien Cristau wrote:
>
> > Marco, what do you think of switching to this, or at least using its fb
> > part?
> I do not mind explicitly blacklisting each fb driver, but I would like
> to have a way to semi-automatically ge
On Tue, 2010-01-12 at 00:43 +, Julien Cristau wrote:
> On Tue, Jan 12, 2010 at 00:36:49 +, Julien Cristau wrote:
>
> > On Tue, Jan 12, 2010 at 00:31:53 +, Julien Cristau wrote:
> >
> > > I tried to look at how other distributions handle this, and this
> > > /etc/modprobe.d/blacklist.c
On Tue, Jan 12, 2010 at 01:34:45AM +0100, Marco d'Itri wrote:
> I do not mind explicitly blacklisting each fb driver, but I would like
> to have a way to semi-automatically generate the list. Is there any?
Sure, the kernel build have all necessary informations.
Bastian
--
We Klingons believe as
On Tue, Jan 12, 2010 at 00:36:49 +, Julien Cristau wrote:
> On Tue, Jan 12, 2010 at 00:31:53 +, Julien Cristau wrote:
>
> > I tried to look at how other distributions handle this, and this
> > /etc/modprobe.d/blacklist.conf file seems to be a Debianism. From what
> > I can tell (looking
On Tue, Jan 12, 2010 at 00:31:53 +, Julien Cristau wrote:
> I tried to look at how other distributions handle this, and this
> /etc/modprobe.d/blacklist.conf file seems to be a Debianism. From what
> I can tell (looking at the ubuntu archive and a fedora 10 box) other
> distros have a /etc/mo
On Jan 12, Julien Cristau wrote:
> Marco, what do you think of switching to this, or at least using its fb
> part?
I do not mind explicitly blacklisting each fb driver, but I would like
to have a way to semi-automatically generate the list. Is there any?
BTW, I am not sure why the watchdog drive
On Thu, Dec 31, 2009 at 18:24:56 +, Julien Cristau wrote:
> One issue that showed up is that i915 isn't getting loaded by udev,
> because /etc/modprobe.d/blacklist.conf contains:
>
> # This directive blacklists all devices which are members of the display
> class.
> # It has the main effect
On Thu, 2009-12-31 at 18:24 +, Julien Cristau wrote:
[...]
> One possible way to fix this, I guess, would be to replace this
> blacklist entry with a list of blacklisted fb drivers, to allow i915
> (and later radeon and nouveau) being loaded automatically on boot. Is
> this feasible? Are ther
On Tue, Dec 22, 2009 at 20:33:00 +0100, Julien Cristau wrote:
> On Sun, Dec 20, 2009 at 16:50:22 +, Ben Hutchings wrote:
>
> > > > The X packages will be able to use modprobe
> > > > config files to enable KMS at run time as required.
> >
> > This is not for the kernel team to do.
> >
> FWI
12 matches
Mail list logo
