From: Michael Krufky <mkrufky@gmail.com>
To: Johannes Stezenbach <js@linuxtv.org>,
Prakash Punnoor <prakash@punnoor.de>,
Michael Krufky <mkrufky@gmail.com>,
linux-dvb-maintainer@linuxtv.org, linux-kernel@vger.kernel.org
Subject: Re: [linux-dvb-maintainer] Re: [PATCH] b2c2: make front-ends selectable and include noob option
Date: Tue, 6 Dec 2005 17:20:00 -0500 [thread overview]
Message-ID: <37219a840512061420j6dc6a0bdy71cc817706dcd0ef@mail.gmail.com> (raw)
In-Reply-To: <20051206215610.GA18247@linuxtv.org>
On 12/6/05, Johannes Stezenbach <js@linuxtv.org> wrote:
> On Tue, Dec 06, 2005, Prakash Punnoor wrote:
> > Am Dienstag Dezember 6 2005 21:20 schrieb Michael Krufky:
> > > On 12/6/05, Prakash Punnoor <prakash@punnoor.de> wrote:
> > > > this patch probably needs some touch-up but mainly I am sking the dvb
> > > > guys why
> > > > don't they do something like this. Current situation:
> > >
> > > NACK.
> > >
> > > You are going to run into some problems with this patch... For instance,
> > > What if the user chooses to compile the b2c2-flexcop driver in-kernel, but
> > > only compiles the frontend drivers as modules... Then, the frontend
> > > support will be built into the flexcop driver, but the module will not yet
> > > be available at the time when the kernel is looking for it...
> >
> > Well, I said it needed touch up. ;-) After all I didn't seriously believe it
> > gets merged in current state (and yes, I didn't think about the module issue,
> > but you're right , of course). But it simply didn't seem like dvb guys are
> > caring about the problem. I once (probably half a year ago already) mailed to
> > linux-dvb and got zero response. That told me everything.
>
> I make it a point to ignore postings which ignore
> the recent mailing list history ;-)
>
> This had been discussed on linux-dvb and the consensus was that
> no one wants to invest time to maintain an #ifdef mess
> just so that people can save a few KB in their kernel.
>
> Also, most users don't know and don't care what demodulator
> their card has, the dependency on all of them, plus the
> implied auto probing saves them some headaches and us a lot of
> newbie questions.
>
> > Personally I won't invest more time in perfecting the patch. I just wanted to
> > get some attention to this problem and will use the patch privately for my
> > own happiness...
>
> The b2c2-flexcop-pci driver could certainly use some fixing. Your
> patch just hides the driver problems by deselecting functionality
> that _you_ don't need.
>
Johannes -
If you approve of the method that I used to implement compile-time
frontend selection in cx88-dvb and saa7134-dvb, then I would be happy
to implement this into the flexcop driver as well. I understand why
developers might not want to invest the time into this, but I see the
benefits to it, and I am willing to work on it. Of course, this
wouldnt be sent to the kernel until 2.6.16 (or maybe 2.6.17)
I have the bcm3510-based board in my possesion right now, and both the
nxt2002 and lgdt3303 versions are in the mail to me as I type this
email. (I plan to use the nxt2002 version to test and fix the nxt200x
driver for this use.)
OTOH, if there are other reasons to stay away from this idea, say the
word, and I'll send a revert patch to Andrew for the cx88 and saa7134
stuff... It is working well -- Gene reported a bug and I fixed it,
already in Linus' tree.
What do you think?
-Michael
next prev parent reply other threads:[~2005-12-06 22:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-06 19:52 Prakash Punnoor
2005-12-06 20:28 ` Michael Krufky
[not found] ` <37219a840512061220w17388551jd54c189973e23355@mail.gmail.com>
2005-12-06 20:39 ` Prakash Punnoor
2005-12-06 20:42 ` Michael Krufky
2005-12-06 21:56 ` [linux-dvb-maintainer] " Johannes Stezenbach
2005-12-06 22:20 ` Michael Krufky [this message]
2005-12-07 0:29 ` Johannes Stezenbach
2005-12-07 7:56 ` Patrick Boettcher
2005-12-07 8:25 ` Prakash Punnoor
2005-12-07 7:29 ` Prakash Punnoor
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=37219a840512061420j6dc6a0bdy71cc817706dcd0ef@mail.gmail.com \
--to=mkrufky@gmail.com \
--cc=js@linuxtv.org \
--cc=linux-dvb-maintainer@linuxtv.org \
--cc=linux-kernel@vger.kernel.org \
--cc=prakash@punnoor.de \
/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®