mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Patrick Boettcher <patrick.boettcher@desy.de>
To: Chris Rankin <rankincj@yahoo.com>
Cc: David Brigada <brigad@rpi.edu>,
	linux-dvb-maintainer@linuxtv.org, linux-kernel@vger.kernel.org
Subject: Re: [linux-dvb-maintainer] Re: [OOPS] Linux 2.6.14.2 and DVB USB
Date: Tue, 15 Nov 2005 10:00:50 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.64.0511150939010.18517@pub3.ifh.de> (raw)
In-Reply-To: <20051114235102.64514.qmail@web52912.mail.yahoo.com>

Hi,

On Mon, 14 Nov 2005, Chris Rankin wrote:
> This sounds contrary to the entire concept of hotplugging to me. And I don't think that a typical
> desktop user would be happy to be told that s/he needs to become root and unload kernel modules
> before s/he can unplug a USB device.

Unfortunately the dvb-core is currently not able to handle hotplugging 
while a dvb application is accessing a dvb-dev-node. This applies 
for every dvb-device, not only for dvb-usb devices, but no one ever tried 
to unplug a DVB PCI card while using it, yet.

Before unplugging a device, you can check if the module is removable to 
make sure that really no application is currently using it. (You will get 
"module in use" then).

We already thought about that problem and we think that dvbdev.c is the 
correct place to start implementing that, but I don't have enough 
knowledge (and time) to do that now, sorry.

regards,
Patrick.

  reply	other threads:[~2005-11-15  9:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-14 21:05 Chris Rankin
2005-11-14 23:39 ` David Brigada
2005-11-14 23:51   ` Chris Rankin
2005-11-15  9:00     ` Patrick Boettcher [this message]
2005-11-15 15:28       ` [linux-dvb-maintainer] " Johannes Stezenbach
2005-11-15 15:46         ` Patrick Boettcher
2005-11-15 16:43           ` Johannes Stezenbach
2005-11-15 16:52             ` Patrick Boettcher

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=Pine.LNX.4.64.0511150939010.18517@pub3.ifh.de \
    --to=patrick.boettcher@desy.de \
    --cc=brigad@rpi.edu \
    --cc=linux-dvb-maintainer@linuxtv.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rankincj@yahoo.com \
    /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

all inboxes | Powered by JetHome®