The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Johannes Stezenbach <js@linuxtv.org>
To: Patrick Boettcher <patrick.boettcher@desy.de>
Cc: Chris Rankin <rankincj@yahoo.com>,
	linux-dvb-maintainer@linuxtv.org, David Brigada <brigad@rpi.edu>,
	linux-kernel@vger.kernel.org, Deti Fliegl <deti@fliegl.de>
Subject: Re: [linux-dvb-maintainer] Re: [OOPS] Linux 2.6.14.2 and DVB USB
Date: Tue, 15 Nov 2005 17:43:21 +0100	[thread overview]
Message-ID: <20051115164321.GA4331@linuxtv.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0511151633490.29360@pub3.ifh.de>

Patrick Boettcher wrote:
> On Tue, 15 Nov 2005, Johannes Stezenbach wrote:
> > Patrick Boettcher wrote:
> >>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.
> >
> >I thought someone sent a patch which fixes it for the cinergyT2
> >recently? Wouldn't the same approach work for dvb-usb?
> >(But I haven't had a chance to test the cinergyT2 patch yet.)
> 
> Once Deti Fliegl created that patch I had a look at it to figure out if it 
> can easily be adapted to dvb-usb. This is was my answer:
> 
> http://www.linuxtv.org/pipermail/linux-dvb/2005-October/005333.html
> 
> After that mail I had some private mails with Deti, but he is currently 
> too busy to adapt his mechanism to dvbdev.c and I'm too stupid.

The advantage of keeping development stuff on the lists is that
someone else might actually write a patch to address the issue...

> The cinergy-driver handles the frontend in a different way and that's 
> why it is possible to fix it like Deti does it.
> 
> If I could fix it in in dvb-usb, then it would be again only fixed for a 
> small amount of devices. For DVB-PCMCIA-cards using the default 
> fe-architecture will also cause Oopses like that, when unplugging while 
> having the device in use. That's why, IMHO, the dvb-core should be made 
> hotplug-safe, not a single driver. Even worse: it's not just the 
> frontend-device-nodes, but also the demux-nodes (and I think the other 
> onces too).

I agree. Could you post a summary of your conversation with Deti to
linux-dvb so someone else could start working on it?

Thanks,
Johannes

  reply	other threads:[~2005-11-15 16:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-14 21:05 [OOPS] Linux 2.6.14.2 and DVB USB Chris Rankin
2005-11-14 23:39 ` David Brigada
2005-11-14 23:51   ` Chris Rankin
2005-11-15  9:00     ` [linux-dvb-maintainer] " Patrick Boettcher
2005-11-15 15:28       ` Johannes Stezenbach
2005-11-15 15:46         ` Patrick Boettcher
2005-11-15 16:43           ` Johannes Stezenbach [this message]
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=20051115164321.GA4331@linuxtv.org \
    --to=js@linuxtv.org \
    --cc=brigad@rpi.edu \
    --cc=deti@fliegl.de \
    --cc=linux-dvb-maintainer@linuxtv.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patrick.boettcher@desy.de \
    --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