From: Patrick Boettcher <patrick.boettcher@desy.de>
To: Johannes Stezenbach <js@linuxtv.org>
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:52:41 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.64.0511151747050.29360@pub3.ifh.de> (raw)
In-Reply-To: <20051115164321.GA4331@linuxtv.org>
On Tue, 15 Nov 2005, Johannes Stezenbach wrote:
>> 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?
Actually, that was the summary :). He said, it should be more generally
done, I suggested him to look into dvbdev.c, then he said is too busy.
In one email he explained his mechanism to me, but you can understand it
also by looking at his cinergy-patch, I think.
Patrick.
prev parent reply other threads:[~2005-11-15 16:53 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 ` [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
2005-11-15 16:52 ` Patrick Boettcher [this message]
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.0511151747050.29360@pub3.ifh.de \
--to=patrick.boettcher@desy.de \
--cc=brigad@rpi.edu \
--cc=deti@fliegl.de \
--cc=js@linuxtv.org \
--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®