public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Krufky <mkrufky@m1k.net>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: Andrew Morton <akpm@osdl.org>,
	Mauro Carvalho Chehab <mchehab@brturbo.com.br>,
	linux-kernel@vger.kernel.org, video4linux-list@redhat.com
Subject: Re: [PATCH -rc2-mm2] BUG FIX - v4l broken hybrid dvb inclusion
Date: Tue, 12 Jul 2005 13:19:32 -0400	[thread overview]
Message-ID: <42D3FBA4.3050501@m1k.net> (raw)
In-Reply-To: <200507122107.51907.adobriyan@gmail.com>

Alexey Dobriyan wrote:

>On Tuesday 12 July 2005 19:06, Michael Krufky wrote:
>  
>
>>v4l-saa7134-hybrid-dvb.patch
>>v4l-cx88-update.patch
>>
>>The specific change that caused this problem is:
>>
>>- Let Kconfig decide whether to include frontend-specific code.
>>
>>I had tested this change against 2.6.13-rc2-mm1, and it worked perfectly as
>>expected, but it caused problems in today's 2.6.13-rc2-mm2 release.  For
>>some reason, the symbols don't get set properly.
>>    
>>
>What symbols? What error messages do you see?
>
Alexey-

Maybe symbols was the wrong terminology... What I meant was the 
CONFIG_DVB_LGDT3302 , etc flags

Previous patch removed the #define's that you see below... This should 
have worked, since these should be set instead from kconfig, but it 
didn't work as expected (even though the modules ARE selected by 
kconfig), and the #ifdef's return false.... (I don't know why it worked 
in my test against 2.6.13-rc2-mm1, but it doesn't work in -mm2, and it 
must be fixed) Breaks all hybrid v4l/dvb boards.

>>--- linux-2.6.13-rc2-mm2.orig/drivers/media/video/cx88/cx88-dvb.c
>>+++ linux/drivers/media/video/cx88/cx88-dvb.c
>>    
>>
>>+#define CONFIG_DVB_MT352 1
>>+#define CONFIG_DVB_CX22702 1
>>+#define CONFIG_DVB_OR51132 1
>>+#define CONFIG_DVB_LGDT3302 1
>>    
>>
>>--- linux-2.6.13-rc2-mm2.orig/drivers/media/video/saa7134/saa7134-dvb.c
>>+++ linux/drivers/media/video/saa7134/saa7134-dvb.c
>>    
>>
>>+#define CONFIG_DVB_MT352 1
>>+#define CONFIG_DVB_TDA1004X 1
>>    
>>
>
>Looks band-aidly.
>  
>
Yes, it does LOOK like a band-aid, but this is actually only reverting a 
previous change.  I admit that something better needs to be done.  Gerd 
Korr says to remove the #ifdef's alltogether.  Instead, I just returned 
the #define's .....  We can remove the #ifdef's in a future patch, but I 
want to discuss this with the other v4l developers before I would make a 
change like that.  THIS patch, however, is safe to apply, and I've 
already committed it into video4linux cvs.

Andrew, please apply this and don't merge the 
[v4l-saa7134-hybrid-dvb.patch & v4l-cx88-update.patch] patches to Linus' 
tree without this patch as well.

Thank you.

-- 
Michael Krufky



  reply	other threads:[~2005-07-12 17:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-12 15:06 [PATCH -rc2-mm2] BUG FIX - v4l broken hybrid dvb inclusion Michael Krufky
2005-07-12 17:07 ` Alexey Dobriyan
2005-07-12 17:19   ` Michael Krufky [this message]
2005-07-12 18:18     ` Alexey Dobriyan
2005-07-12 18:24       ` Michael Krufky
2005-07-12 22:36 ` Johannes Stezenbach

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=42D3FBA4.3050501@m1k.net \
    --to=mkrufky@m1k.net \
    --cc=adobriyan@gmail.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@brturbo.com.br \
    --cc=video4linux-list@redhat.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