Skip to contentSkip to conversation

3.5 kernel options for Hauppauge_WinTV-HVR-1250

DISCUSSION James 4 participants 13 messages Aug 1, 2012 – Aug 2, 2012 Media (V4L/DVB)

lore
Share & tools
lore
author
#2 lore raw
Quoted 12 lines · Andy Walls
Quoted 9 lines · James

I got the latest kernel from git and I can't find the kernel options for my tv card.

I have: http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-HVR-1250
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

Quoted 5 lines

/sbin/modinfo cx23885

Regards,
Andy

I don't build any modules.

In case anyone else has trouble getting to work (the kernel makes options invisible unless dependencies are met).

1. Turn on expert mode (to be able to select frontends to build). General setup/Configure standard kernel features (expert users)

2. Device Drivers/Multimedia support

3. Analog TV support

4. Digital TV support

5. Remote Controller support

6. Customize analog and hybrid tuner modules to build Customize TV tuners ---> Microtune MT2131 silicon tuner

7. V4L PCI(e) devices/Conexant cx23885 (2388x successor) support

8. DVB/ATSC adapters ---> Customise the frontend modules to build/Customise DVB Frontends/Samsung S5H1409 based

I think that is it but I did other stuff so I may be missing a step or 2.

Can I make the make menuconfig show all the options an when I select something, it selects all the dependencies?

#3 lore raw
Quoted 49 lines · James
Quoted 8 lines · Andy Walls
Quoted 6 lines · James

I got the latest kernel from git and I can't find the kernel options for my tv card.

I have: http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-HVR-1250
--
To unsubscribe from this list: send the line "unsubscribe

linux-media"

Quoted 9 lines
Quoted 3 lines

in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

/sbin/modinfo cx23885

Regards,
Andy

I don't build any modules.

In case anyone else has trouble getting to work (the kernel makes options invisible unless dependencies are met).

1. Turn on expert mode (to be able to select frontends to build). General setup/Configure standard kernel features (expert users)

2. Device Drivers/Multimedia support

3. Analog TV support

4. Digital TV support

5. Remote Controller support

6. Customize analog and hybrid tuner modules to build Customize TV tuners ---> Microtune MT2131 silicon tuner

7. V4L PCI(e) devices/Conexant cx23885 (2388x successor) support

8. DVB/ATSC adapters ---> Customise the frontend modules to build/Customise DVB Frontends/Samsung S5H1409 based

I think that is it but I did other stuff so I may be missing a step or 2.

Quoted 7 lines

Can I make the make menuconfig show all the options an when I select something, it selects all the dependencies?
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

No, the Kconfig system can't help.

You can 'grep MODULE_ drivers/media/video/cx23885/* drivers/media/video/cx25840/* ' and other relevant directories under drivers/media/{dvb, common} to find all the parameter options for all the drivers involved in making a HVR_1250 work.

Regards,
Andy

#4 lore raw
Quoted 1 line · Andy Walls

You can 'grep MODULE_ drivers/media/video/cx23885/* drivers/media/video/cx25840/* ' and other relevant directories under drivers/media/{dvb, common} to find all the parameter options for all the drivers involved in making a HVR_1250 work.

Or just build with everything enabled until you know it is working, and then optimize the list of modules later.

Also, the 1250 is broken for analog until very recently (patches went upstream for 3.5/3.6 a few days ago).

Devin

Signature · 2 lines
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com
author
#5 lore raw
Quoted 9 lines
Quoted 4 lines · Andy Walls

You can 'grep MODULE_ drivers/media/video/cx23885/* drivers/media/video/cx25840/* ' and other relevant directories under drivers/media/{dvb, common} to find all the parameter options for all the drivers involved in making a HVR_1250 work.

Or just build with everything enabled until you know it is working, and then optimize the list of modules later.

It should have been easier, select the card and it builds all the drivers it needs. :-)
Is there a script somewhere that lets me select a card and automatically modifies the kernel config?

Quoted 3 lines

Also, the 1250 is broken for analog until very recently (patches went upstream for 3.5/3.6 a few days ago).

North American OTA is all digital so I have no way to test it.

Quoted 11 lines

Devin

--
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

#6 lore raw
Quoted 4 lines · On Thu, Aug 2, 2012 at 12:34 PM, <[email protected]> wrote:

It should have been easier, select the card and it builds all the drivers it needs. :-)
Is there a script somewhere that lets me select a card and automatically modifies the kernel config?

Yeah, that isn't really practical. There are *hundreds* of boards, and having one config option isn't practical given the number of different bridge/demod/tuner combinations there are.

Heck, even for the 1250 there are eight or ten different versions, so most users wouldn't even know the right one to choose.

The reality is that the kernel config isn't optimized for this use case, and given the overhead in administration combined with the *EXTREME* unlikelihood that any real users would use it, it just isn't worth the effort.

If you're hacking the kernel config to include support for a single board as opposed to the whole media subsystem, you're 0.001% of the user base, and your use case isn't worth the developer effort that would be required.

In short, we barely have the manpower to make this stuff work at all. Wasted effort to optimize for really obscure use cases is better spent on expanding the set of supported products.

Quoted 4 lines
Quoted 2 lines

Also, the 1250 is broken for analog until very recently (patches went upstream for 3.5/3.6 a few days ago).

North American OTA is all digital so I have no way to test it.

That's fine. I was just trying to make clear that if you wanted analog functionality then you need the latest code.

Devin

Signature · 2 lines
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com
author
#7 lore raw
Quoted 3 lines

Heck, even for the 1250 there are eight or ten different versions, so most users wouldn't even know the right one to choose.

Do you mean boards that use different chips?
I hate it when manufacturers do that (ie. with routers).

#8 lore raw
Quoted 6 lines · On 08/02/2012 10:41 PM, [email protected] wrote:
Quoted 3 lines

Heck, even for the 1250 there are eight or ten different versions, so most users wouldn't even know the right one to choose.

Do you mean boards that use different chips?
I hate it when manufacturers do that (ie. with routers).

That happens quite often. Few weeks back someone sends mail saying he has got new version of Terratec Cinergy T Stick Dual RC. Old version uses Afatech AF9015 chips whilst new revision is ITE Technologies IT9135 and USB ID is same. Those are quite different chips and having different drivers. In such cases it could be quite challenging to get it working as both drivers are thinking it is for me according to USB ID.

regards
Antti

Signature · 1 line
http://palosaari.fi/
#9 lore raw
In reply to [email protected]
Quoted 6 lines · On Thu, Aug 2, 2012 at 3:41 PM, <[email protected]> wrote:
Quoted 3 lines

Heck, even for the 1250 there are eight or ten different versions, so most users wouldn't even know the right one to choose.

Do you mean boards that use different chips?
I hate it when manufacturers do that (ie. with routers).

In some cases it's different chips (changing the design to use a better/cheaper bridge, demodulator or tuner). In some cases it's because they have different inputs (there are several variants that have different configurations of composite, s-video, audio connector, IR support, etc).

As far as the manufacturer is concerned, if there is no end-user visible feature difference, it's reasonable to not change the model number and cause the confusion. That said though, it's a real PITA for Linux users who think they're something that the web says works but in fact they are getting something else.

Devin

Signature · 2 lines
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com
#10 lore raw
In reply to [email protected]
Quoted 8 lines · [email protected] wrote:
Quoted 3 lines

Heck, even for the 1250 there are eight or ten different versions, so most users wouldn't even know the right one to choose.

Do you mean boards that use different chips?
I hate it when manufacturers do that (ie. with routers).

Quoted 5 lines

--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

Yup. There are "HVR1250"s with different bridge chips: CX23885 vs CX23888. Normally board differences are with tuner, demod, fm radio, and IR chips.

Bridge drivers have the smarts to know what board they are dealing with much better than a human staring at vendor packaging. Bridge drivers look at:

PCI/USB id
Hard coded tables in the drivers
EEPROM information (vendor specific)
I2C bus probes at expected addresses
Goofy hueristics based on register reads (I.e. cx25840_probe ) User provided module options for card type (last resort)

The end user has no hope of compiling the exact linux drivers for a board without some simple experimentation with modprobe and lsmod with the hardware. The Kconfig system gets you the superset of everything the bridge driver might need for a card, given a particular bridge driver.

Regards,
Andy

#11 lore raw
In reply to [email protected]
Quoted 25 lines · [email protected] wrote:
Quoted 5 lines
Quoted 3 lines · Andy Walls

You can 'grep MODULE_ drivers/media/video/cx23885/* drivers/media/video/cx25840/* ' and other relevant directories under drivers/media/{dvb, common} to find all the parameter options for

all

Quoted 4 lines
Quoted 1 line

the drivers involved in making a HVR_1250 work.

Or just build with everything enabled until you know it is working, and then optimize the list of modules later.

It should have been easier, select the card and it builds all the drivers
it needs. :-)
Is there a script somewhere that lets me select a card and automatically
modifies the kernel config?

Quoted 3 lines

Also, the 1250 is broken for analog until very recently (patches went upstream for 3.5/3.6 a few days ago).

North American OTA is all digital so I have no way to test it.

Quoted 1 line
Quoted 11 lines
Quoted 7 lines

Devin

--
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com
--
To unsubscribe from this list: send the line "unsubscribe

linux-media" in

Quoted 3 lines

the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

There are too many different card models and variants supported by bridge drivers to list every one in the kconfig system.

There are several variants of the 1250 itself with different chips on board. You have no guarantee that two retail boxes labeled HVR-1250 both contain identical hardware.

IMO, trying to winnow down the supporting drivers you compile just sets yourself for more work in the future if you add a second card.

Regards,
Andy

#12 lore raw
In reply to Devin Heitmueller
Quoted 7 lines · Devin Heitmueller
Quoted 1 line · Andy Walls

You can 'grep MODULE_ drivers/media/video/cx23885/*

drivers/media/video/cx25840/* ' and other relevant directories under drivers/media/{dvb, common} to find all the parameter options for all the drivers involved in making a HVR_1250 work.

Quoted 11 lines

Or just build with everything enabled until you know it is working, and then optimize the list of modules later.

Also, the 1250 is broken for analog until very recently (patches went upstream for 3.5/3.6 a few days ago).

Devin

Signature · 2 lines
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com

Oh, James meant kernel *build* options, not kernel *commandline/module* options.

Then what I offered won't help at all.

-Andy