From: Jon Smirl <jonsmirl@gmail.com>
To: "Michel Dänzer" <michel@daenzer.net>
Cc: linux-fbdev-devel@lists.sourceforge.net,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: Re: Hotplug blacklist and video devices
Date: Fri, 18 Feb 2005 18:35:49 -0500 [thread overview]
Message-ID: <9e473391050218153527cbb893@mail.gmail.com> (raw)
In-Reply-To: <1108767531.5631.29.camel@thor.asgaard.local>
On Fri, 18 Feb 2005 17:58:51 -0500, Michel Dänzer <michel@daenzer.net> wrote:
> > For example I'm looking at making changes to DRM such that DRM will
> > require the corresponding framebuffer driver to be loaded.
>
> Ignoring my suspicion that people won't like stuff getting forced down
> their throats like this (why would a DRM _require_ a framebuffer
> device?), does the hotplug blacklisting of the framebuffer devices
> matter at all if the DRM depends on them, i.e. won't they be loaded
> regardless when the DRM is loaded?
There is no mechanism for getting a hotplug remove event into a driver
like DRM that doesn't attach to the PCI device.
--
Jon Smirl
jonsmirl@gmail.com
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click
WARNING: multiple messages have this Message-ID (diff)
From: Jon Smirl <jonsmirl@gmail.com>
To: "Michel Dänzer" <michel@daenzer.net>
Cc: linux-fbdev-devel@lists.sourceforge.net,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [Linux-fbdev-devel] Re: Hotplug blacklist and video devices
Date: Fri, 18 Feb 2005 18:35:49 -0500 [thread overview]
Message-ID: <9e473391050218153527cbb893@mail.gmail.com> (raw)
In-Reply-To: <1108767531.5631.29.camel@thor.asgaard.local>
On Fri, 18 Feb 2005 17:58:51 -0500, Michel Dänzer <michel@daenzer.net> wrote:
> > For example I'm looking at making changes to DRM such that DRM will
> > require the corresponding framebuffer driver to be loaded.
>
> Ignoring my suspicion that people won't like stuff getting forced down
> their throats like this (why would a DRM _require_ a framebuffer
> device?), does the hotplug blacklisting of the framebuffer devices
> matter at all if the DRM depends on them, i.e. won't they be loaded
> regardless when the DRM is loaded?
There is no mechanism for getting a hotplug remove event into a driver
like DRM that doesn't attach to the PCI device.
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2005-02-18 23:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-18 20:51 Hotplug blacklist and video devices Jon Smirl
2005-02-18 21:08 ` Bill Nottingham
2005-02-18 21:14 ` Jon Smirl
2005-02-18 21:14 ` Jon Smirl
2005-02-18 22:58 ` Michel Dänzer
2005-02-18 22:58 ` [Linux-fbdev-devel] " Michel Dänzer
2005-02-18 23:35 ` Jon Smirl [this message]
2005-02-18 23:35 ` Jon Smirl
2005-02-19 12:29 ` Matthew Garrett
2005-02-19 15:56 ` Jon Smirl
2005-02-19 15:56 ` Jon Smirl
2005-02-19 16:51 ` Matthew Garrett
2005-02-19 19:54 ` Jeremy Fitzhardinge
2005-02-21 19:08 ` Bill Nottingham
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=9e473391050218153527cbb893@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=michel@daenzer.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.