Problems with WinTV Hauppauge dualHD and LibreELEC 9 on Le Potato S905X box
lable for this card. [ 15.900463@2] em28xx: Registered (Em28xx Input Extension) extension For comparison, here's dmesg from the xbian/Raspberry: [ 14.844653] em28174 #0: EEPROM ID = 26 00 01 00, EEPROM hash = 0x16e6c5c8 [ 14.844668] em28174 #0: EEPROM info: [ 14.844679] em28174 #0: microcode start address = 0x0004, boot configuration = 0x01 [ 14.852600] em28174 #0: AC97 audio (5 sample rates) [ 14.852615] em28174 #0: 500mA max power [ 14.852632] em28174 #0: Table at offset 0x27, strings=0x0e6a, 0x1888, 0x087e [ 14.853068] em28174 #0: Identified as Hauppauge WinTV-dualHD DVB (card=99) [ 14.860852] tveeprom 4-0050: Hauppauge model 204109, rev B3I6, serial# 13886631 [ 14.860873] tveeprom 4-0050: tuner model is SiLabs Si2157 (idx 186, type 4) [ 14.860887] tveeprom 4-0050: TV standards PAL(B/G) NTSC(M) PAL(I) SECAM(L/L') PAL(D/D1/K) ATSC/DVB Digital (eeprom 0xfc) [ 14.860900] tveeprom 4-0050: audio processor is None (idx 0) [ 14.860912] tveeprom 4-0050: has no radio, has IR receiver, has no IR transmitter [ 14.860924] em28174 #0: dvb set to isoc mode. [ 14.861601] usbcore: registered new interface driver em28xx [ 14.862760] snd-rpi-cirrus soc:sound: ASoC: CODEC DAI wm5102-aif1 not registered - will retry [ 14.907896] em28174 #0: Binding DVB extension [ 15.002024] i2c i2c-4: Added multiplexed i2c bus 5 [ 15.002057] si2168 4-0064: Silicon Labs Si2168-B40 successfully identified [ 15.002076] si2168 4-0064: firmware version: B 4.0.2 [ 15.002639] snd-rpi-cirrus soc:sound: ASoC: CODEC DAI wm5102-aif1 not registered - will retry [ 15.043260] si2157 5-0060: Silicon Labs Si2147/2148/2157/2158 successfully attached [ 15.043363] DVB: registering new adapter (em28174 #0) [ 15.043404] usb 1-1.5: DVB: registering adapter 0 frontend 0 (Silicon Labs Si2168)... [ 15.044164] snd-rpi-cirrus soc:sound: ASoC: CODEC DAI wm5102-aif1 not registered - will retry [ 15.047208] em28174 #0: DVB extension successfully initialized [ 15.047229] em28xx: Registered (Em28xx dvb Extension) extension [ 15.095899] em28174 #0: Registering input extension [ 15.253160] Registered IR keymap rc-hauppauge [ 15.254164] input: em28xx IR (em28174 #0) as /devices/platform/soc/3f98.usb/usb1/1-1/1-1.5/rc/rc0/input0 [ 15.254765] rc rc0: em28xx IR (em28174 #0) as /devices/platform/soc/3f98.usb/usb1/1-1/1-1.5/rc/rc0 [ 15.262050] em28174 #0: Input extension successfully initalized [ 15.262071] em28xx: Registered (Em28xx Input Extension) extension [ 16.509324] si2168 4-0064: downloading firmware from file 'dvb-demod-si2168-b40-01.fw' [ 17.024833] si2168 4-0064: firmware version: B 4.0.11 [ 17.035803] si2157 5-0060: found a 'Silicon Labs Si2157-A30' [ 17.087464] si2157 5-0060: firmware version: 3.0.5 [ 17.087617] usb 1-1.5: DVB: adapter 0 frontend 0 frequency 0 out of range (4200..87000) Here's also lsmod from the Le Potato: Module Size Used by xt_nat 2015 1 xt_tcpudp 3293 3 veth 5005 0 ipt_MASQUERADE 2256 2 nf_conntrack_netlink 20028 0 nfnetlink 5227 2 nf_conntrack_netlink iptable_nat 3308 1 nf_conntrack_ipv4 9101 2 nf_defrag_ipv4 1457 1 nf_conntrack_ipv4 nf_nat_ipv4 3582 1 iptable_nat xt_addrtype 2899 2 iptable_filter 1478 1 ip_tables 17688 2 iptable_filter,iptable_nat xt_conntrack 3247 1 x_tables 18411 7 ip_tables,xt_tcpudp,ipt_MASQUERADE,xt_conntrack,xt_nat,iptable_filter,xt_addrtype nf_nat 13203 4 ipt_MASQUERADE,nf_nat_ipv4,xt_nat,iptable_nat nf_conntrack 60627 7 ipt_MASQUERADE,nf_nat,nf_nat_ipv4,xt_conntrack,nf_conntrack_netlink,iptable_nat,nf_conntrack_ipv4 bridge 96995 0 stp 1680 1 bridge llc 3773 2 stp,bridge rc_hauppauge 2193 0 em28xx_rc 8362 0 em28xx_dvb 22440 0 dvb_core 103890 1 em28xx_dvb 8021q 19007 0 ir_rc6_decoder 3557 0 mali 192729 5 em28xx 71682 2 em28xx_dvb,em28xx_rc tveeprom 13844 1 em28xx v4l2_common 4001 1 em28xx ir_nec_decoder 2429 0 ipheth 6743 0 wifi_dummy 806 0 ir_lirc_codec 4209 0 lirc_dev 7264 2 ir_lirc_codec meson_ir 3997 0 rc_core 23955 9 lirc_dev,meson_ir,ir_lirc_codec,rc_hauppauge,ir_nec_decoder,ir_rc6_decoder,em28xx_rc amlvideodri 12674 0 videobuf_res 5378 1 amlvideodri videobuf_core 16643 2 amlvideodri,videobuf_res videodev 150841 2 amlvideodri,v4l2_common media 25461 3 em28xx,videodev,dvb_core dwc_otg 233217 0 fbcon 38031 0 bitblit 4468 1 fbcon softcursor 1168 1 bitblit font 7327 1 fbcon Would be glad to get this up'n'running... Thanks for any help! If you need something, let me know! Hauke
[PATCH] [media] airspy: add missing include of linux/mm.h
airspy uses PAGE_ALIGN() which is defined in linux/mm.h, but this file is not directly included just indirectly thought some other include file. Signed-off-by: Hauke Mehrtens --- drivers/media/usb/airspy/airspy.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/media/usb/airspy/airspy.c b/drivers/media/usb/airspy/airspy.c index 4069234..d182dd2 100644 --- a/drivers/media/usb/airspy/airspy.c +++ b/drivers/media/usb/airspy/airspy.c @@ -15,6 +15,7 @@ */ #include +#include #include #include #include -- 2.1.4 -- 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
[PATCH] [media] hackrf: add missing include of linux/mm.h
hackrf uses PAGE_ALIGN() which is defined in linux/mm.h, but this file is not directly included just indirectly thought some other include file. Signed-off-by: Hauke Mehrtens --- drivers/media/usb/hackrf/hackrf.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/media/usb/hackrf/hackrf.c b/drivers/media/usb/hackrf/hackrf.c index fd1fa41..2eade31 100644 --- a/drivers/media/usb/hackrf/hackrf.c +++ b/drivers/media/usb/hackrf/hackrf.c @@ -15,6 +15,7 @@ */ #include +#include #include #include #include -- 2.1.4 -- 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: Removal of regulator framework
On 07/23/2014 08:23 PM, Luis R. Rodriguez wrote: > On Wed, Jul 23, 2014 at 10:57 AM, Mauro Carvalho Chehab > wrote: >> Em Wed, 23 Jul 2014 10:13:28 -0700 >> "Luis R. Rodriguez" escreveu: >> >>> On Sat, Jul 19, 2014 at 9:19 AM, Hauke Mehrtens wrote: >>>> Maintaining the regulator drivers in backports costs some time and I do >>>> not need them. Is anybody using the regulator drivers from backports? I >>>> would like to remove them. >>> >>> That came simply from collateral of backporting media drivers, >>> eventually I started running into device drivers that used the >>> regulator framework. Since we have tons of media drivers perhaps the >>> more sensible thing to do is to white list a set of media divers that >>> people actually care and then we just nuke both regulator and media >>> drivers that no one cares for. For that though I'd like to ask media >>> folks. >> >> Hi Luis, >> >> The drivers that currently use regulators are mostly the ones at >> drivers/media/platform, plus the corresponding I2C drivers for their >> webcam sensors, under drivers/media/i2c. >> >> I think that there's one exception though: em28xx. This driver can use >> some sensor drivers, as it supports a few webcams. This is one of >> the most used USB media driver, as there are lots of USB supported >> on it, supporting 4 types of devices on it: analog TV, capture card, >> digital TV and webcam. >> >> The webcam part of em28xx is not that relevant, as there are very few >> models using it. However, currently, it is not possible to just >> disable webcam support. It shouldn't be hard to make webcam support >> optional on it, as it has already sub-drivers for V4L2, DVB, ALSA and >> remote controller. One additional driver for webcam, that could be >> disabled at the backport tree shouldn't be hard to do. If you want it, >> patches are welcome. > > Thanks for the details Mauro, are you aware of current or future uses > of backports for media at this point? Adding media drivers was more of > an experiment to see how hard or easy it would be to add a new > unrelated subsystem, we carry it now and as collateral also carry some > regulator drivers but its not clear the value in terms of users, so > hence Hauke's question of removal of the regulator drivers. It'd be > good to limit the drivers we carry to what folks actually use and care > about. > > Luis > Hi, carrying some regularity drivers which are needed for some specific media driver does not look like a big problem. The current problem from my side is that we carry all regularity drivers by default and that causes some problems. Many of these driver are used only on one specific SoC product line and uses their often changing interface, so they break often. When all the regulator drivers are only needed for the media driver I would add just add the driver which are actually used by a shipped media driver and nothing more. Hauke -- 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
