public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Boris Cuber <me@boris64.net>
To: linux-media@vger.kernel.org
Cc: "'cyber.bogh'" <cyber.bogh@gmx.de>,
	"'Matthias Schwarzott'" <zzam@gentoo.org>
Subject: Re: [GIT PATCHES for 2.6.31] V4L/DVB fixes
Date: Mon, 13 Jul 2009 17:12:21 +0200	[thread overview]
Message-ID: <200907131712.26909.me@boris64.net> (raw)
In-Reply-To: <200907131529.25786.cyber.bogh@gmx.de>

[-- Attachment #1: Type: Text/Plain, Size: 3987 bytes --]

Am Montag, 13. Juli 2009 schrieben Sie:
> Am Montag 13 Juli 2009 14:13:50 schrieben Sie:
> > On Sonntag, 12. Juli 2009, Boris Cuber wrote:
> > > Hi kernel folks!
> > >
> > > Problem:
> > > Since kernel-2.6.31-rc* my dvb-s adapter (Technisat SkyStar2 DVB card)
> > > refuses to work (worked fine in every kernel up to 2.6.30.1).
> > > So anything pulled into the new kernel seems to have broken
> > > something (at least for me :/).
> > >
> > > I opened a detailed bug report here:
> > > http://bugzilla.kernel.org/show_bug.cgi?id=13709
> > > Please let me know if i can help in finding a solution
> > > or testing a patch /whatever.
> >
> > This looks like it is related to this patch:
> >
> > commit d66b94b4aa2f40e134f8c07c58ae74ef3d523ee0
> > Author: Patrick Boettcher <pb@linuxtv.org>
> > Date:   Wed May 20 05:08:26 2009 -0300
> >
> >     V4L/DVB (11829): Rewrote frontend-attach mechanism to gain noise-less
> > deactivation of submodules
> >
> >     This patch is reorganizing the frontend-attach mechanism in order to
> >     gain noise-less (superflous prints) deactivation of submodules.
> >
> >     Credits go to Uwe Bugla for helping to clean and test the code.
> >
> >     Signed-off-by: Uwe Bugla <uwe.bugla@gmx.de>
> >     Signed-off-by: Patrick Boettcher <pb@linuxtv.org>
> >     Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
> >
> >
> >
> > All frontend-attach related code is wrapped by ifdefs like this:
> > #if defined(CONFIG_DVB_MT312_MODULE) ||
> > defined(CONFIG_DVB_STV0299_MODULE) <CODE>
> > #endif
> >
> > So this code will only be compiled if one of the two drivers is compiled
> > as a module, having them compiled in will omit this code.

Hi Matthias

thank you for your help. I manually edited 
those #ifdefs to temporary get around my problem.
My dvb adapter is working again ;)


>
> Yes. And that's exactly the way things were planned and should also stay,
> even if there exist a thousands of "Boris64" who do not have the slightest
> idea about what kernel compilation is or could be.....

Well, i always thought compiling your own kernel is about choice.
And _my_ choice always was:
I don't want use modules, because booting a monolithic 
kernel on my computer is slightly faster.


>
> No matter if we're talking about the main module, the frontend, the backend
> or whatever other part of not only a DVB driver:
> None of them is permanently needed while the machine is running. So kmod
> can kick them out of the memory if they aren't needed, if they were
> compiled as module.
>
> But if you compile them into the kernel you are wasting system resources
> because the main kernel becomes too big (I'd call that a "Windoze-effect").
>
> So compiling those drivers a module is gold, and any other choice is simply
> nonsense.
>
> > Trent Piepho seems to already have a patch for this, but it is not yet
> > merged into the kernel.
>
> May Trent Piepho do whatever he likes. I do not think that any further
> patch is necessary for that driver section.
>
> It would rather be necessary for some quirky users to enlarge their limited
> brain and understand what kernel compilation means and is here for.
>
> > Regards
> > Matthias
>
> CU
>
> cyber.bogh
>
> P. S.: The other part that really makes me utmost angry about the "Boris's"
> in that world:
>
> If you're doing really hard for months to enhance things, and you urgently
> need testers to help and invest brain those Boris's aren't visible at all.
> Nowhere!

Those "Boris's" can't remember that anyone ever asked'em to help.
And "they" didn't subscribe to this list until "their" dvb card(s) didn't
work anymore for some reason.


>
> Once things are done they come back and all they have got to do then is to
> complain for stupid nonsense...
>
> How did Lou Reed say?
> "Stick a fork in their ass, turn it over and they're done!"
>

Have a nice day,
regards, Boris

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2009-07-13 15:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-12 13:50 [GIT PATCHES for 2.6.31] V4L/DVB fixes Boris Cuber
2009-07-13 12:13 ` Matthias Schwarzott
2009-07-13 13:29   ` cyber.bogh
2009-07-13 13:46     ` AW: " Jesko Schwarzer
2009-07-13 15:12     ` Boris Cuber [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-08-31  5:33 Mauro Carvalho Chehab
2009-08-31  6:37 ` Jean-Francois Moine
2009-08-31 14:20 ` Mauro Carvalho Chehab
2009-08-12 22:05 Mauro Carvalho Chehab
2009-08-13 18:13 ` Linus Torvalds
2009-08-14  2:53   ` Mauro Carvalho Chehab
2009-07-24 17:40 Mauro Carvalho Chehab
2009-07-24 20:50 ` Greg KH
2009-07-24 21:32   ` Devin Heitmueller
2009-07-24 21:48     ` Greg KH
2009-07-05 22:37 Mauro Carvalho Chehab

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=200907131712.26909.me@boris64.net \
    --to=me@boris64.net \
    --cc=cyber.bogh@gmx.de \
    --cc=linux-media@vger.kernel.org \
    --cc=zzam@gentoo.org \
    /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