RE: stv090x vs stv0900 support
Hi, Can someone help me, please? Regards, Kishore. -Original Message- From: Krishna Kishore Sent: Wednesday, August 28, 2013 6:05 PM To: Chris Lee; Mariusz Bialonczyk Cc: Linux Media Mailing List; linux-...@vger.kernel.org Subject: RE: stv090x vs stv0900 support Hi, When read_mac_address is called, khubd timed out error is seen. It looks like USB control msgs are not successfully being sent. Can someone please check attached logs and help me? Regards, Kishore. From: Krishna Kishore Sent: Tuesday, August 27, 2013 12:49 PM To: Chris Lee; Mariusz Bialonczyk Cc: Linux Media Mailing List Subject: RE: stv090x vs stv0900 support Hi Chris, Does it help me in getting through the problem I am facing? On Desktop (Ubuntu 12.04), 7500 does not work. But, on desktop Ubuntu 13.04 it works fine. Since it is working well with 13.04, I tried with 3.8.x kernel on my board. It does not work. So, I can see that kernel version does not matter. I assume you have 7500 DVB receiver. Can you please try this device with Ubuntu 12.04 and 13.04 and see the difference in the behavior? If it helps you, I can send you logs of 12.04 and 13.04. Thanks in advance. Regards, Kishore. -Original Message- From: linux-media-ow...@vger.kernel.org [mailto:linux-media-ow...@vger.kernel.org] On Behalf Of Chris Lee Sent: Friday, August 16, 2013 6:21 PM To: Mariusz Bialonczyk Cc: Linux Media Mailing List Subject: Re: stv090x vs stv0900 support Ive found a few bugs in stv090x that I want to get ironed out 100% before I submit the patch, dvb-s2 8psk fec2/3 for example has a slightly higher ber then stv0900, Got that fixed but Im still not happy with the patch, has a few other minor issues with low sr dvb-s qpsk sometimes not locking on the first attempt to tune. The Prof 7500 also seems to have an issue with stb6100 where get_frequency() wont return the correct frequency when other stb6100 devices I have do. Once I get those figured out to the point Im happy I'll submit it for everyones comments. Thanks for the link Mariusz, I'll check it out, maybe youve overcome some of the shortfalls Ive found Chris Lee On Fri, Aug 16, 2013 at 1:19 AM, Mariusz Bialonczyk ma...@skyboo.net wrote: On 07/24/2013 06:39 PM, Chris Lee wrote: Im looking for comments on these two modules, they overlap support for the same demods. stv0900 supporting stv0900 and stv090x supporting stv0900 and stv0903. Ive flipped a few cards from one to the other and they function fine. In some ways stv090x is better suited. Its a pain supporting two modules that are written differently but do the same thing, a fix in one almost always means it has to be implemented in the other as well. I totally agree with you. Im not necessarily suggesting dumping stv0900, but Id like to flip a few cards that I own over to stv090x just to standardize it. The Prof 7301 and Prof 7500. I did it already for 7301, see here: http://thread.gmane.org/gmane.linux.drivers.video-input-infrastructure /28082 but due to 'political' reasons it doesn't went upstream. For private use i am still using this patch on recent kernels, because it is working much more stable for my card comparing to stv0900. I think that moving prof 7500 should be relative easy, i even prepared a patch for this but I was not able to test it due to lack of hardware. Whats everyones thoughts on this? It will cut the number of patch''s in half when it comes to these demods. Ive got alot more coming lol :) Oh yes, you could also take into account another duplicate code: stb6100_cfg.h used for stv090x stb6100_proc.h used for stv0900 In my patch I've successfully switched to stb6100_cfg.h. Chris -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html regards, -- Mariusz Białończyk | xmpp/e-mail: ma...@skyboo.net http://manio.skyboo.net | https://github.com/manio -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html SASKEN BUSINESS DISCLAIMER: This message may contain confidential, proprietary or legally privileged information. In case you are not the original intended Recipient of the message, you must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message and you are requested to delete it and inform the sender. Any views expressed in this message are those of the individual sender unless otherwise stated. Nothing contained in this message shall be construed as an offer or acceptance of any offer by Sasken Communication Technologies Limited (Sasken) unless sent with that express intent and with due authority of Sasken. Sasken has
Re: stv090x vs stv0900 support
On Thu, Aug 29, 2013 at 03:20:32PM +, Krishna Kishore wrote: Hi, Can someone help me, please? Personally, I'm not allowed to do so because of: SASKEN BUSINESS DISCLAIMER: This message may contain confidential, proprietary or legally privileged information. In case you are not the original intended Recipient of the message, you must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message and you are requested to delete it and inform the sender. Any views expressed in this message are those of the individual sender unless otherwise stated. Nothing contained in this message shall be construed as an offer or acceptance of any offer by Sasken Communication Technologies Limited (Sasken) unless sent with that express intent and with due authority of Sasken. Sasken has taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus transmitted by this email. Read Disclaimer at http://www.sasken.com/extras/mail_disclaimer.html Which is really incompatible with open mailing list discussions... sorry, greg k-h -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: stv090x vs stv0900 support
Hi Chris, Does it help me in getting through the problem I am facing? On Desktop (Ubuntu 12.04), 7500 does not work. But, on desktop Ubuntu 13.04 it works fine. Since it is working well with 13.04, I tried with 3.8.x kernel on my board. It does not work. So, I can see that kernel version does not matter. I assume you have 7500 DVB receiver. Can you please try this device with Ubuntu 12.04 and 13.04 and see the difference in the behavior? If it helps you, I can send you logs of 12.04 and 13.04. Thanks in advance. Regards, Kishore. -Original Message- From: linux-media-ow...@vger.kernel.org [mailto:linux-media-ow...@vger.kernel.org] On Behalf Of Chris Lee Sent: Friday, August 16, 2013 6:21 PM To: Mariusz Bialonczyk Cc: Linux Media Mailing List Subject: Re: stv090x vs stv0900 support Ive found a few bugs in stv090x that I want to get ironed out 100% before I submit the patch, dvb-s2 8psk fec2/3 for example has a slightly higher ber then stv0900, Got that fixed but Im still not happy with the patch, has a few other minor issues with low sr dvb-s qpsk sometimes not locking on the first attempt to tune. The Prof 7500 also seems to have an issue with stb6100 where get_frequency() wont return the correct frequency when other stb6100 devices I have do. Once I get those figured out to the point Im happy I'll submit it for everyones comments. Thanks for the link Mariusz, I'll check it out, maybe youve overcome some of the shortfalls Ive found Chris Lee On Fri, Aug 16, 2013 at 1:19 AM, Mariusz Bialonczyk ma...@skyboo.net wrote: On 07/24/2013 06:39 PM, Chris Lee wrote: Im looking for comments on these two modules, they overlap support for the same demods. stv0900 supporting stv0900 and stv090x supporting stv0900 and stv0903. Ive flipped a few cards from one to the other and they function fine. In some ways stv090x is better suited. Its a pain supporting two modules that are written differently but do the same thing, a fix in one almost always means it has to be implemented in the other as well. I totally agree with you. Im not necessarily suggesting dumping stv0900, but Id like to flip a few cards that I own over to stv090x just to standardize it. The Prof 7301 and Prof 7500. I did it already for 7301, see here: http://thread.gmane.org/gmane.linux.drivers.video-input-infrastructure /28082 but due to 'political' reasons it doesn't went upstream. For private use i am still using this patch on recent kernels, because it is working much more stable for my card comparing to stv0900. I think that moving prof 7500 should be relative easy, i even prepared a patch for this but I was not able to test it due to lack of hardware. Whats everyones thoughts on this? It will cut the number of patch''s in half when it comes to these demods. Ive got alot more coming lol :) Oh yes, you could also take into account another duplicate code: stb6100_cfg.h used for stv090x stb6100_proc.h used for stv0900 In my patch I've successfully switched to stb6100_cfg.h. Chris -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html regards, -- Mariusz Białończyk | xmpp/e-mail: ma...@skyboo.net http://manio.skyboo.net | https://github.com/manio -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html SASKEN BUSINESS DISCLAIMER: This message may contain confidential, proprietary or legally privileged information. In case you are not the original intended Recipient of the message, you must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message and you are requested to delete it and inform the sender. Any views expressed in this message are those of the individual sender unless otherwise stated. Nothing contained in this message shall be construed as an offer or acceptance of any offer by Sasken Communication Technologies Limited (Sasken) unless sent with that express intent and with due authority of Sasken. Sasken has taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus transmitted by this email. Read Disclaimer at http://www.sasken.com/extras/mail_disclaimer.html -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: stv090x vs stv0900 support
On 07/24/2013 06:39 PM, Chris Lee wrote: Im looking for comments on these two modules, they overlap support for the same demods. stv0900 supporting stv0900 and stv090x supporting stv0900 and stv0903. Ive flipped a few cards from one to the other and they function fine. In some ways stv090x is better suited. Its a pain supporting two modules that are written differently but do the same thing, a fix in one almost always means it has to be implemented in the other as well. I totally agree with you. Im not necessarily suggesting dumping stv0900, but Id like to flip a few cards that I own over to stv090x just to standardize it. The Prof 7301 and Prof 7500. I did it already for 7301, see here: http://thread.gmane.org/gmane.linux.drivers.video-input-infrastructure/28082 but due to 'political' reasons it doesn't went upstream. For private use i am still using this patch on recent kernels, because it is working much more stable for my card comparing to stv0900. I think that moving prof 7500 should be relative easy, i even prepared a patch for this but I was not able to test it due to lack of hardware. Whats everyones thoughts on this? It will cut the number of patch''s in half when it comes to these demods. Ive got alot more coming lol :) Oh yes, you could also take into account another duplicate code: stb6100_cfg.h used for stv090x stb6100_proc.h used for stv0900 In my patch I've successfully switched to stb6100_cfg.h. Chris -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html regards, -- Mariusz Białończyk | xmpp/e-mail: ma...@skyboo.net http://manio.skyboo.net | https://github.com/manio -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: stv090x vs stv0900 support
Ive found a few bugs in stv090x that I want to get ironed out 100% before I submit the patch, dvb-s2 8psk fec2/3 for example has a slightly higher ber then stv0900, Got that fixed but Im still not happy with the patch, has a few other minor issues with low sr dvb-s qpsk sometimes not locking on the first attempt to tune. The Prof 7500 also seems to have an issue with stb6100 where get_frequency() wont return the correct frequency when other stb6100 devices I have do. Once I get those figured out to the point Im happy I'll submit it for everyones comments. Thanks for the link Mariusz, I'll check it out, maybe youve overcome some of the shortfalls Ive found Chris Lee On Fri, Aug 16, 2013 at 1:19 AM, Mariusz Bialonczyk ma...@skyboo.net wrote: On 07/24/2013 06:39 PM, Chris Lee wrote: Im looking for comments on these two modules, they overlap support for the same demods. stv0900 supporting stv0900 and stv090x supporting stv0900 and stv0903. Ive flipped a few cards from one to the other and they function fine. In some ways stv090x is better suited. Its a pain supporting two modules that are written differently but do the same thing, a fix in one almost always means it has to be implemented in the other as well. I totally agree with you. Im not necessarily suggesting dumping stv0900, but Id like to flip a few cards that I own over to stv090x just to standardize it. The Prof 7301 and Prof 7500. I did it already for 7301, see here: http://thread.gmane.org/gmane.linux.drivers.video-input-infrastructure/28082 but due to 'political' reasons it doesn't went upstream. For private use i am still using this patch on recent kernels, because it is working much more stable for my card comparing to stv0900. I think that moving prof 7500 should be relative easy, i even prepared a patch for this but I was not able to test it due to lack of hardware. Whats everyones thoughts on this? It will cut the number of patch''s in half when it comes to these demods. Ive got alot more coming lol :) Oh yes, you could also take into account another duplicate code: stb6100_cfg.h used for stv090x stb6100_proc.h used for stv0900 In my patch I've successfully switched to stb6100_cfg.h. Chris -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html regards, -- Mariusz Białończyk | xmpp/e-mail: ma...@skyboo.net http://manio.skyboo.net | https://github.com/manio -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
stv090x vs stv0900 support
Im looking for comments on these two modules, they overlap support for the same demods. stv0900 supporting stv0900 and stv090x supporting stv0900 and stv0903. Ive flipped a few cards from one to the other and they function fine. In some ways stv090x is better suited. Its a pain supporting two modules that are written differently but do the same thing, a fix in one almost always means it has to be implemented in the other as well. Im not necessarily suggesting dumping stv0900, but Id like to flip a few cards that I own over to stv090x just to standardize it. The Prof 7301 and Prof 7500. Whats everyones thoughts on this? It will cut the number of patch''s in half when it comes to these demods. Ive got alot more coming lol :) Chris -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: stv090x vs stv0900 support
My opinion is that, it is better to have only stv090x. Apart from minimizing the number of patches and ease of maintenance, it will avoid the confusion that I had When I started using prof 7500. I had to enable stv0900 and stb6100. I got confused on whether to enable stv0900 or to enable stv090x. -Original Message- From: linux-media-ow...@vger.kernel.org [mailto:linux-media-ow...@vger.kernel.org] On Behalf Of Chris Lee Sent: Wednesday, July 24, 2013 10:09 PM To: linux-media@vger.kernel.org Subject: stv090x vs stv0900 support Im looking for comments on these two modules, they overlap support for the same demods. stv0900 supporting stv0900 and stv090x supporting stv0900 and stv0903. Ive flipped a few cards from one to the other and they function fine. In some ways stv090x is better suited. Its a pain supporting two modules that are written differently but do the same thing, a fix in one almost always means it has to be implemented in the other as well. Im not necessarily suggesting dumping stv0900, but Id like to flip a few cards that I own over to stv090x just to standardize it. The Prof 7301 and Prof 7500. Whats everyones thoughts on this? It will cut the number of patch''s in half when it comes to these demods. Ive got alot more coming lol :) Chris -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html SASKEN BUSINESS DISCLAIMER: This message may contain confidential, proprietary or legally privileged information. In case you are not the original intended Recipient of the message, you must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message and you are requested to delete it and inform the sender. Any views expressed in this message are those of the individual sender unless otherwise stated. Nothing contained in this message shall be construed as an offer or acceptance of any offer by Sasken Communication Technologies Limited (Sasken) unless sent with that express intent and with due authority of Sasken. Sasken has taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus transmitted by this email. Read Disclaimer at http://www.sasken.com/extras/mail_disclaimer.html -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: stv090x vs stv0900 support
On 07/24/2013 08:21 PM, Krishna Kishore wrote: My opinion is that, it is better to have only stv090x. Apart from minimizing the number of patches and ease of maintenance, it will avoid the confusion that I had When I started using prof 7500. I had to enable stv0900 and stb6100. I got confused on whether to enable stv0900 or to enable stv090x. -Original Message- From: linux-media-ow...@vger.kernel.org [mailto:linux-media-ow...@vger.kernel.org] On Behalf Of Chris Lee Sent: Wednesday, July 24, 2013 10:09 PM To: linux-media@vger.kernel.org Subject: stv090x vs stv0900 support Im looking for comments on these two modules, they overlap support for the same demods. stv0900 supporting stv0900 and stv090x supporting stv0900 and stv0903. Ive flipped a few cards from one to the other and they function fine. In some ways stv090x is better suited. Its a pain supporting two modules that are written differently but do the same thing, a fix in one almost always means it has to be implemented in the other as well. Im not necessarily suggesting dumping stv0900, but Id like to flip a few cards that I own over to stv090x just to standardize it. The Prof 7301 and Prof 7500. Whats everyones thoughts on this? It will cut the number of patch''s in half when it comes to these demods. Ive got alot more coming lol :) Chris stv0900 is better separated from the tuner whilst stv090x has weird stv6110x_devctl structure. That's why I used stv0900 for anysee driver. I wonder is there something special supported by stv090x because normal tuner/demod callbacks are not enough. regards Antti -- http://palosaari.fi/ -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: stv090x vs stv0900 support
On 07/24/13 19:52, Antti Palosaari wrote: On 07/24/2013 08:21 PM, Krishna Kishore wrote: My opinion is that, it is better to have only stv090x. Apart from minimizing the number of patches and ease of maintenance, it will avoid the confusion that I had When I started using prof 7500. I had to enable stv0900 and stb6100. I got confused on whether to enable stv0900 or to enable stv090x. -Original Message- From: linux-media-ow...@vger.kernel.org [mailto:linux-media-ow...@vger.kernel.org] On Behalf Of Chris Lee Sent: Wednesday, July 24, 2013 10:09 PM To: linux-media@vger.kernel.org Subject: stv090x vs stv0900 support Im looking for comments on these two modules, they overlap support for the same demods. stv0900 supporting stv0900 and stv090x supporting stv0900 and stv0903. Ive flipped a few cards from one to the other and they function fine. In some ways stv090x is better suited. Its a pain supporting two modules that are written differently but do the same thing, a fix in one almost always means it has to be implemented in the other as well. Im not necessarily suggesting dumping stv0900, but Id like to flip a few cards that I own over to stv090x just to standardize it. The Prof 7301 and Prof 7500. Whats everyones thoughts on this? It will cut the number of patch''s in half when it comes to these demods. Ive got alot more coming lol :) Chris stv0900 is better separated from the tuner whilst stv090x has weird stv6110x_devctl structure. That's why I used stv0900 for anysee driver. I wonder is there something special supported by stv090x because normal tuner/demod callbacks are not enough. That's probably for the ddbridge driver, while ours is pretty old (0.5) Ralph/oliver is working on 0.9 atm. 0.8.6 still uses the same structure i think. regards Antti -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: stv090x vs stv0900
В сообщении от 10 мая 2010 14:44:08 автор Pascal Terjan написал: Le dimanche 09 mai 2010 à 21:34 +0300, Igor M. Liplianin a écrit : On 6 мая 2010 11:46:17 Pascal Terjan wrote: Hi, I was adding support for a non working version of DVBWorld HD 2104 It is listed on http://www.linuxtv.org/wiki/index.php/DVBWorld_HD_2104_FTA_USB_Box as : = for new solution : 2104B (Sharp0169 Tuner) * STV6110A tuner * ST0903 demod * Cyrix CY7C68013A USB controller = The 2104A is supposed to be working and also have ST0903 but uses stv0900, so I tried using it too but did not manage to get it working. But it working. I have the device and test it succesfully. OK, but the B does not here while it seems to work with stv090x All I get in log with femon is stv0900_read_status: 7DEMOD LOCK FAIL 6stv0900_get_rf_level 6stv0900_get_rf_level: RFLevel = -100 6stv0900_carr_get_quality And with scandvb : stv0900_read_status: 7DEMOD LOCK FAIL stv0900_read_status: 7DEMOD LOCK FAIL stv0900_read_status: 7DEMOD LOCK FAIL stv0900_read_status: 7DEMOD LOCK FAIL 6stv0900_search: 7stv0900_set_tuner: Frequency=1939000 stv0900_set_tuner: Bandwidth=7200 6stv0900_activate_s2_modcode 6Search Fail stv0900_read_status: 7DEMOD LOCK FAIL So modprobe dvb-usb-dw2102 demod=2 brings DVBWorld 2104A to you on golden plate. Yes but this one is 2104B OK, modprobe dvb-usb-dw2102 demod=2 brings DVBWorld 2104B to you on golden plate Look what I was tested already: 1. DVB-S2 USB 2104A (EARDA4B47, STB6100 + ST0903) 2. DVB-S2 USB 2104B (sharp0169, stv6110A + ST0903) 3. DVB-S2 USB 2104C (cx24116) 4. DVB-S2 USB 2104D (montage_ts2020 + ds3000) 5. DVB-S2 USB 2104E (SERIT2636, stv6110A + ST0903) If someone interested: md5sum dvb-usb-dw2104*.fw* 4cd4215e169c42f6d05cf23be2edd907 dvb-usb-dw2104.fw 4cd4215e169c42f6d05cf23be2edd907 dvb-usb-dw2104.fw.keep 9ccab99bdd4a0f252455d08dee189794 dvb-usb-dw2104d.fw 9ccab99bdd4a0f252455d08dee189794 dvb-usb-dw2104e.fw BR Igor -- Igor M. Liplianin Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: stv090x vs stv0900
Le dimanche 09 mai 2010 à 21:34 +0300, Igor M. Liplianin a écrit : On 6 мая 2010 11:46:17 Pascal Terjan wrote: Hi, I was adding support for a non working version of DVBWorld HD 2104 It is listed on http://www.linuxtv.org/wiki/index.php/DVBWorld_HD_2104_FTA_USB_Box as : = for new solution : 2104B (Sharp0169 Tuner) * STV6110A tuner * ST0903 demod * Cyrix CY7C68013A USB controller = The 2104A is supposed to be working and also have ST0903 but uses stv0900, so I tried using it too but did not manage to get it working. But it working. I have the device and test it succesfully. OK, but the B does not here while it seems to work with stv090x All I get in log with femon is stv0900_read_status: 7DEMOD LOCK FAIL 6stv0900_get_rf_level 6stv0900_get_rf_level: RFLevel = -100 6stv0900_carr_get_quality And with scandvb : stv0900_read_status: 7DEMOD LOCK FAIL stv0900_read_status: 7DEMOD LOCK FAIL stv0900_read_status: 7DEMOD LOCK FAIL stv0900_read_status: 7DEMOD LOCK FAIL 6stv0900_search: 7stv0900_set_tuner: Frequency=1939000 stv0900_set_tuner: Bandwidth=7200 6stv0900_activate_s2_modcode 6Search Fail stv0900_read_status: 7DEMOD LOCK FAIL So modprobe dvb-usb-dw2102 demod=2 brings DVBWorld 2104A to you on golden plate. Yes but this one is 2104B -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: stv090x vs stv0900
On 6 мая 2010 11:46:17 Pascal Terjan wrote: Hi, I was adding support for a non working version of DVBWorld HD 2104 It is listed on http://www.linuxtv.org/wiki/index.php/DVBWorld_HD_2104_FTA_USB_Box as : = for new solution : 2104B (Sharp0169 Tuner) * STV6110A tuner * ST0903 demod * Cyrix CY7C68013A USB controller = The 2104A is supposed to be working and also have ST0903 but uses stv0900, so I tried using it too but did not manage to get it working. But it working. I have the device and test it succesfully. I now have some working code by using stv090x + stv6110x (copied config from budget) but I am wondering why do we have 2 drivers for stv0900, and is stv0900 supposed to handle stv0903 devices or is either the code or the wki wrong about 2104A? Code for stv0900 supposed to handle stv0903 devices as well. And it handles. Feel free to add for stv0900. I don't impede. Also, are they both maintained ? I wrote a patch to add get_frontend to stv090x but stv0900 also does not have it and I don't know which one should get new code. And stv6110x seems to also handle stv6110 which also exists as a separate module... In time when I commit stv0900(stv6110 as well) there wasn't any driver for stv0900/stv0903. Now I'm wondering like you. Look here: r...@useri:/etc/default# modinfo dvb-usb-dw2102 filename: /lib/modules/2.6.34-rc6/kernel/drivers/media/dvb/dvb-usb/dvb-usb-dw2102.ko license:GPL version:0.1 description:Driver for DVBWorld DVB-S 2101, 2102, DVB-S2 2104, DVB-C 3101 USB2.0, TeVii S600, S630, S650, S660 USB2.0, Prof 1100, 7500 USB2.0 devices author: Igor M. Liplianin (c) liplia...@me.by srcversion: 496C3974FA3791E61D28672 alias: usb:v3034p7500d*dc*dsc*dp*ic*isc*ip* alias: usb:v9022pD660d*dc*dsc*dp*ic*isc*ip* alias: usb:v3011pB012d*dc*dsc*dp*ic*isc*ip* alias: usb:v9022pD630d*dc*dsc*dp*ic*isc*ip* alias: usb:v04B4p3101d*dc*dsc*dp*ic*isc*ip* alias: usb:v0CCDp0064d*dc*dsc*dp*ic*isc*ip* alias: usb:v9022pD650d*dc*dsc*dp*ic*isc*ip* alias: usb:v04B4p2104d*dc*dsc*dp*ic*isc*ip* alias: usb:v04B4p2101d*dc*dsc*dp*ic*isc*ip* alias: usb:v04B4p2102d*dc*dsc*dp*ic*isc*ip* depends:dvb-usb,i2c-core vermagic: 2.6.34-rc6 SMP mod_unload PENTIUM4 parm: debug:set debugging level (1=info 2=xfer 4=rc(or-able)). (int) parm: keymap:set keymap 0=default 1=dvbworld 2=tevii 3=tbs ... (int) parm: demod:demod to probe (1=cx24116 2=stv0903+stv6110 4=stv0903+stb6100(or-able)). (int) parm: adapter_nr:DVB adapter numbers (array of short) So modprobe dvb-usb-dw2102 demod=2 brings DVBWorld 2104A to you on golden plate. Best Regards -- Igor M. Liplianin Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: stv090x vs stv0900
2010/5/9 Igor M. Liplianin liplia...@me.by: Also, are they both maintained ? I wrote a patch to add get_frontend to stv090x but stv0900 also does not have it and I don't know which one should get new code. And stv6110x seems to also handle stv6110 which also exists as a separate module... In time when I commit stv0900(stv6110 as well) there wasn't any driver for stv0900/stv0903. Now I'm wondering like you. Quite strange indeed.. http://www.linuxtv.org/pipermail/linux-dvb/2008-November/030492.html http://www.mail-archive.com/linux-media@vger.kernel.org/msg13353.html -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: stv090x vs stv0900
Hello, On Thu, 2010-05-06 at 10:46 +0200, Pascal Terjan wrote: Also, are they both maintained ? I wrote a patch to add get_frontend to stv090x but stv0900 also does not have it and I don't know which one should get new code. I have added get_frontend to stv0900 two months ago - http://linuxtv.org/hg/v4l-dvb/rev/a3e28fbefdc3 I'm trying to describe my point of view about two drivers for stv6110 +stv0900. History: I have anounced our card on November 2008 - http://www.linuxtv.org/pipermail/linux-dvb/2008-November/030439.html As you can see I have mentioned that we developing code and will be publish it under GPL. All people in ML received this message. This should be prevent of duplicate work. Also we have obtained permission (signed letter) from STM to publish resulting code under GPL. We have send pull request at Feb 2009 - http://www.mail-archive.com/linux-media@vger.kernel.org/msg02180.html (stv090x commit requested later - in May 2009 - http://www.mail-archive.com/linux-media@vger.kernel.org/msg04978.html ). Solution: Ideally two drivers should be combined into one. stv0900 driver can be used as starting point. We (NetUP Inc.) can initiaite this job. But we need approval from Manu and all community who using stv090x. Manu what do you think about this ? This is not trivial because some features may be broken when combining this two code. -- Abylai Ospan aos...@netup.ru NetUP Inc. P.S. From our side we have strong experience in STV6110+STV0900 IC's. Our engeneers designed NetUP Dual DVB-S2 CI card from scratch. We know many nuances about this IC's. For example, we have tested 16APSK/32APSK - http://linuxtv.org/wiki/index.php/STMicroelectronics_STV0900A_16APSK_32APSK Also we developing new version of our NetUP Dual DVB-S2 CI based on FPGA (like our Dual DVB-T/C CI card - http://linuxtv.org/wiki/index.php/NetUP_Dual_DVB_T_C_CI_RF ). This new version of card can proceed high bitrates from STV0900 (120Mbps and higher ). Also this card can receive raw frames from STV0900 ( not only TS ) for extra functionality ( GSE ). -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: stv090x vs stv0900
On Sun, May 9, 2010 at 11:06 PM, Abylai Ospan aos...@netup.ru wrote: Hello, On Thu, 2010-05-06 at 10:46 +0200, Pascal Terjan wrote: Also, are they both maintained ? I wrote a patch to add get_frontend to stv090x but stv0900 also does not have it and I don't know which one should get new code. I have added get_frontend to stv0900 two months ago - http://linuxtv.org/hg/v4l-dvb/rev/a3e28fbefdc3 I'm trying to describe my point of view about two drivers for stv6110 +stv0900. History: I have anounced our card on November 2008 - http://www.linuxtv.org/pipermail/linux-dvb/2008-November/030439.html As you can see I have mentioned that we developing code and will be publish it under GPL. All people in ML received this message. This should be prevent of duplicate work. Also we have obtained permission (signed letter) from STM to publish resulting code under GPL. We have send pull request at Feb 2009 - http://www.mail-archive.com/linux-media@vger.kernel.org/msg02180.html (stv090x commit requested later - in May 2009 - http://www.mail-archive.com/linux-media@vger.kernel.org/msg04978.html ). Solution: Ideally two drivers should be combined into one. stv0900 driver can be used as starting point. We (NetUP Inc.) can initiaite this job. But we need approval from Manu and all community who using stv090x. Manu what do you think about this ? The STV090x driver supports both the STV0900 and STV0903 broadcast demodulators very well and in multiple configurations on couple of bridges (SAA7146, nGene, SAA7160, some USB bridges, some others also in the process) and is quite a generic one. Currently, the STV090x driver handles a lot of quirks which has been documented as well as undocumented by STM, basically being actively supported by STM themselves and by a few card vendors as well, other than for this community to a very great extend. Currently, since the driver has been fine tuned to this great extend and so many users of it, I have no plans of migrating to the STV0900 driver, which was developed later on and tested to a much lesser extend, by developers and vendors alike. So, I am much less inclined to go the STV0900 way. At the behest of STM themselves, I have withheld from adding support for the AAB/AAC chips initially, due to the basic reasons that these advanced features are not really well tested in the field, due to the lack of that many users and the highly unlikely chance that the advanced stuff (ACM/VCM) is yet to be deployed for a home user segment. In the chance that there are more likely users for the advanced stuff, these can be added quite easily to the STV090x/STV6110x driver. Also, interesting point to be noted is that there are no users for ACM/VCM in the Linux userspace for the driver to be supported for any broadcast purposes. The only case in where the Advanced chips are being sold (that too at a higher price) is where card manufacturers who cannot commit themselves to that volume, not that it adds any value to the general user as it is, at the this time. Simply adding in code and making it unmaintainable makes no sense to me at least. -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
stv090x vs stv0900
Hi, I was adding support for a non working version of DVBWorld HD 2104 It is listed on http://www.linuxtv.org/wiki/index.php/DVBWorld_HD_2104_FTA_USB_Box as : = for new solution : 2104B (Sharp0169 Tuner) * STV6110A tuner * ST0903 demod * Cyrix CY7C68013A USB controller = The 2104A is supposed to be working and also have ST0903 but uses stv0900, so I tried using it too but did not manage to get it working. I now have some working code by using stv090x + stv6110x (copied config from budget) but I am wondering why do we have 2 drivers for stv0900, and is stv0900 supposed to handle stv0903 devices or is either the code or the wki wrong about 2104A? Also, are they both maintained ? I wrote a patch to add get_frontend to stv090x but stv0900 also does not have it and I don't know which one should get new code. And stv6110x seems to also handle stv6110 which also exists as a separate module... -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: stv090x vs stv0900
Hi Pascal, I was adding support for a non working version of DVBWorld HD 2104 It is listed on http://www.linuxtv.org/wiki/index.php/DVBWorld_HD_2104_FTA_USB_Box as : = for new solution : 2104B (Sharp0169 Tuner) * STV6110A tuner * ST0903 demod * Cyrix CY7C68013A USB controller = The 2104A is supposed to be working and also have ST0903 but uses stv0900, so I tried using it too but did not manage to get it working. I now have some working code by using stv090x + stv6110x (copied config from budget) but I am wondering why do we have 2 drivers for stv0900, and is stv0900 supposed to handle stv0903 devices or is either the code or the wki wrong about 2104A? Also, are they both maintained ? I wrote a patch to add get_frontend to stv090x but stv0900 also does not have it and I don't know which one should get new code. And stv6110x seems to also handle stv6110 which also exists as a separate module... Hehe, you are not only one who is fooled by current situation regarding demods stv0900/stv0903 and plls stv6110. Current status-quo is not good. Same question is asked here again and again. Interesting that it is against usual rule having only one driver for every chip in kernel, but this time that rather strong rule was not applied. Dunno why. May be someone from knowings can answer that on wiki? /Honza PS: FYI I'm also using BOTH variants in 2 projects. For me both look very similar and work w/o probs. So I can't tell you which is better :) -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
