Re: [yocto] FW: strange explanation of how to add a package to an existing recipe
On Thu, 21 Nov 2013, Nicolas Dechesne wrote: On Thu, Nov 21, 2013 at 7:35 PM, Rifenbark, Scott M scott.m.rifenb...@intel.com wrote: suggests that, to customize an image, you should copy the existing .bb file for that image to another name and add a line like: IMAGE_INSTALL += strace but rather than *copy* the entire image file, isn't it easier to use what's already being used; that is, just include or require the existing .bb file. example: core-image-minimal-mtdutils.bb contains: i would agree with the doc. while it is tempting to include/require a 'minimal' image, and it is simpler at first sight, eventually you will need to have full control of all your image. especially when your 'image' is your 'product' that gets deployed. In such circumstances I believe it is more appropriate to not rely on an external recipe. e.g. if the minimal image you include change, all your derived images change too... it's kind of a 'taste' choice, and you might want to choose to do differently, but still the best recommendation to me is to own your image recipes completely... your logic is sound; however, it's also reasonable to suspect that if someone is going to create a new, initial image over which they want full control, they may very well want to create some subtle variants of that image (as is done with all those core images). so perhaps both approaches should be documented with the appropriate caveats? rday -- Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] FW: strange explanation of how to add a package to an existing recipe
On Fri, 22 Nov 2013, Paul Eggleton wrote: Hi Robert, On Friday 22 November 2013 05:50:39 Robert P. J. Day wrote: On Thu, 21 Nov 2013, Nicolas Dechesne wrote: On Thu, Nov 21, 2013 at 7:35 PM, Rifenbark, Scott M scott.m.rifenb...@intel.com wrote: suggests that, to customize an image, you should copy the existing .bb file for that image to another name and add a line like: IMAGE_INSTALL += strace but rather than *copy* the entire image file, isn't it easier to use what's already being used; that is, just include or require the existing .bb file. example: core-image-minimal-mtdutils.bb contains: i would agree with the doc. while it is tempting to include/require a 'minimal' image, and it is simpler at first sight, eventually you will need to have full control of all your image. especially when your 'image' is your 'product' that gets deployed. In such circumstances I believe it is more appropriate to not rely on an external recipe. e.g. if the minimal image you include change, all your derived images change too... it's kind of a 'taste' choice, and you might want to choose to do differently, but still the best recommendation to me is to own your image recipes completely... your logic is sound; however, it's also reasonable to suspect that if someone is going to create a new, initial image over which they want full control, they may very well want to create some subtle variants of that image (as is done with all those core images). so perhaps both approaches should be documented with the appropriate caveats? Maybe, but this is really no different than any other type of recipe. I'd much rather us have some documentation on how to share commonality between recipes (where we discuss the usage and relative merits of include/require and bbclass files, for example) and just note in the image recipe section that image recipes are recipes and point to that generic documentation. I had a hand in writing this section so I'm completely biased, but I agree with Nicolas - including any of the core-image-* in your own recipe isn't giving you much of an advantage and may in fact cause unexpected changes when you come to upgrade. Image recipes tend to be fairly trivial, so it's simplest to just have your own discrete recipe (although if you want to have variants of that recipe that you also control, by all means use includes or classes to share the common parts.) ok, this makes sense. i'll shut up now. rday -- Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] FW: strange explanation of how to add a package to an existing recipe
Hi Robert, On Friday 22 November 2013 05:50:39 Robert P. J. Day wrote: On Thu, 21 Nov 2013, Nicolas Dechesne wrote: On Thu, Nov 21, 2013 at 7:35 PM, Rifenbark, Scott M scott.m.rifenb...@intel.com wrote: suggests that, to customize an image, you should copy the existing .bb file for that image to another name and add a line like: IMAGE_INSTALL += strace but rather than *copy* the entire image file, isn't it easier to use what's already being used; that is, just include or require the existing .bb file. example: core-image-minimal-mtdutils.bb contains: i would agree with the doc. while it is tempting to include/require a 'minimal' image, and it is simpler at first sight, eventually you will need to have full control of all your image. especially when your 'image' is your 'product' that gets deployed. In such circumstances I believe it is more appropriate to not rely on an external recipe. e.g. if the minimal image you include change, all your derived images change too... it's kind of a 'taste' choice, and you might want to choose to do differently, but still the best recommendation to me is to own your image recipes completely... your logic is sound; however, it's also reasonable to suspect that if someone is going to create a new, initial image over which they want full control, they may very well want to create some subtle variants of that image (as is done with all those core images). so perhaps both approaches should be documented with the appropriate caveats? Maybe, but this is really no different than any other type of recipe. I'd much rather us have some documentation on how to share commonality between recipes (where we discuss the usage and relative merits of include/require and bbclass files, for example) and just note in the image recipe section that image recipes are recipes and point to that generic documentation. I had a hand in writing this section so I'm completely biased, but I agree with Nicolas - including any of the core-image-* in your own recipe isn't giving you much of an advantage and may in fact cause unexpected changes when you come to upgrade. Image recipes tend to be fairly trivial, so it's simplest to just have your own discrete recipe (although if you want to have variants of that recipe that you also control, by all means use includes or classes to share the common parts.) Cheers, Paul Cheers, Paul - Intel Corporation (UK) Limited Registered No. 1134945 (England) Registered Office: Pipers Way, Swindon SN3 1RJ VAT No: 860 2173 47 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Yocto branches policy for concurrent SDK releases
Please ignore, sorry for the noise. Best Regards, Zhenhua -Original Message- From: Luo Zhenhua-B19537 Sent: Friday, November 22, 2013 6:44 PM To: Software Development Power Arch Multicore Cc: yocto@yoctoproject.org Subject: [mcswdev] Yocto branches policy for concurrent SDK releases Importance: High Hi all, Currently concurrent SDKs are on-going(e.g. SDK 1.5, T1040/T2080, LS1, etc), the same Yocto branch is used for multiple releases, there is conflict of Yocto recipes for different SDKs. To resolve above issue, following branch mechanism will be used: 1. For those layers without conflict(poky, meta-oe, meta-virtualization and layers reused from community), same branch will be used and no extra branches need to be created, change for those layer should be upstreamed synchronously. 2. For those layers with conflict, the branch specific to SDK are created, currently meta-fsl-ppc and meta-fsl-networking have conflict for different SDKs. Following branches will co-exist for such layers. a. Yocto release branch: dylan, dora. the common changes for all SDKs should be submitted against this branch and cherry-picked to SDK specific branches. The changes should be upstreamed synchronously. b. SDK specific branch: dylan-sdk1.5, dylan-t1_t2, etc. The SDK specific change should be submitted against SDK branch, when SDK is formally released, the changes will be upstreamed. Please let me know if any comment. Best Regards, Zhenhua ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Qt creator build error in the first demo try
Hi guys, I try to build my first embedded project in qt creator but failed. the target board is ATMEL SAMA5D34, and a qt-demo-image has been boot to the board and looks good, i build the yocto project by: bitbake mata-toolchain-qte command, after that i configured the qt creator by following the instruction from the link belows: https://community.freescale.com/thread/309578 but after i press the build i get the mass compiler output msg as showed below, the project is just a simple test with basic Gui, i cannot solve the problem, anyone can help me, thx in advance. ** 15:23:34: Running steps for project TestFun... 15:23:34: Starting: /opt/poky/1.4.1/sysroots/i686-pokysdk-linux/usr/bin/qmake2 /home/teng/Teng/TestFun/TestFun.pro -r -spec linux-gnueabi-oe-g++ CONFIG+=debug CONFIG+=declarative_debug 15:23:34: The process /opt/poky/1.4.1/sysroots/i686-pokysdk-linux/usr/bin/qmake2 exited normally. 15:23:34: Starting: /usr/bin/make /opt/poky/1.4.1/sysroots/i686-pokysdk-linux/usr/bin/uic4 ../TestFun/mainwindow.ui -o ui_mainwindow.h arm-poky-linux-gnueabi-g++ -march=armv7-a -marm -mthumb-interwork -mfloat-abi=hard -mtune=cortex-a9 --sysroot=/opt/poky/1.4.1/sysroots/cortexa9hf-vfp-poky-linux-gnueabi -c -pipe -pipe -pipe -O2 -pipe -g -feliminate-unused-debug-types -O2 -pipe -g -feliminate-unused-debug-types -fpermissive -g -g -g -Wall -W -Wall -W -Wall -W -D_REENTRANT -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/opt/poky/1.4.1/sysroots/cortexa9hf-vfp-poky-linux-gnueabi/usr/share/qtopia/mkspecs/linux-g++ -I../TestFun -I/opt/poky/1.4.1/sysroots/cortexa9hf-vfp-poky-linux-gnueabi//usr/include/qtopia/QtCore -I/opt/poky/1.4.1/sysroots/cortexa9hf-vfp-poky-linux-gnueabi//usr/include/qtopia/QtGui -I/opt/poky/1.4.1/sysroots/cortexa9hf-vfp-poky-linux-gnueabi//usr/include/qtopia -I. -I. -I../TestFun -I. -o main.o ../TestFun/main.cpp In file included from /opt/poky/1.4.1/sysroots/cortexa9hf-vfp-poky-linux-gnueabi//usr/include/qtopia/QtCore/qobject.h:48:0, from /opt/poky/1.4.1/sysroots/cortexa9hf-vfp-poky-linux-gnueabi//usr/include/qtopia/QtGui/qwidget.h:46, from /opt/poky/1.4.1/sysroots/cortexa9hf-vfp-poky-linux-gnueabi//usr/include/qtopia/QtGui/qmainwindow.h:45, from /opt/poky/1.4.1/sysroots/cortexa9hf-vfp-poky-linux-gnueabi//usr/include/qtopia/QtGui/QMainWindow:1, from ../TestFun/mainwindow.h:4, from ../TestFun/main.cpp:1: /opt/poky/1.4.1/sysroots/cortexa9hf-vfp-poky-linux-gnueabi//usr/include/qtopia/QtCore/qstring.h:174:17: note: the mangling of 'va_list' has changed in GCC 4.4 arm-poky-linux-gnueabi-g++ -march=armv7-a -marm -mthumb-interwork -mfloat-abi=hard -mtune=cortex-a9 --sysroot=/opt/poky/1.4.1/sysroots/cortexa9hf-vfp-poky-linux-gnueabi -c -pipe -pipe -pipe -O2 -pipe -g -feliminate-unused-debug-types -O2 -pipe -g -feliminate-unused-debug-types -fpermissive -g -g -g -Wall -W -Wall -W -Wall -W -D_REENTRANT -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/opt/poky/1.4.1/sysroots/cortexa9hf-vfp-poky-linux-gnueabi/usr/share/qtopia/mkspecs/linux-g++ -I../TestFun -I/opt/poky/1.4.1/sysroots/cortexa9hf-vfp-poky-linux-gnueabi//usr/include/qtopia/QtCore -I/opt/poky/1.4.1/sysroots/cortexa9hf-vfp-poky-linux-gnueabi//usr/include/qtopia/QtGui -I/opt/poky/1.4.1/sysroots/cortexa9hf-vfp-poky-linux-gnueabi//usr/include/qtopia -I. -I. -I../TestFun -I. -o mainwindow.o ../TestFun/mainwindow.cpp In file included from /opt/poky/1.4.1/sysroots/cortexa9hf-vfp-poky-linux-gnueabi//usr/include/qtopia/QtCore/qobject.h:48:0, from /opt/poky/1.4.1/sysroots/cortexa9hf-vfp-poky-linux-gnueabi//usr/include/qtopia/QtGui/qwidget.h:46, from /opt/poky/1.4.1/sysroots/cortexa9hf-vfp-poky-linux-gnueabi//usr/include/qtopia/QtGui/qmainwindow.h:45, from /opt/poky/1.4.1/sysroots/cortexa9hf-vfp-poky-linux-gnueabi//usr/include/qtopia/QtGui/QMainWindow:1, from ../TestFun/mainwindow.h:4, from ../TestFun/mainwindow.cpp:1: /opt/poky/1.4.1/sysroots/cortexa9hf-vfp-poky-linux-gnueabi//usr/include/qtopia/QtCore/qstring.h:174:17: note: the mangling of 'va_list' has changed in GCC 4.4 /opt/poky/1.4.1/sysroots/i686-pokysdk-linux/usr/bin/moc4 -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/opt/poky/1.4.1/sysroots/cortexa9hf-vfp-poky-linux-gnueabi/usr/share/qtopia/mkspecs/linux-g++ -I../TestFun -I/opt/poky/1.4.1/sysroots/cortexa9hf-vfp-poky-linux-gnueabi//usr/include/qtopia/QtCore -I/opt/poky/1.4.1/sysroots/cortexa9hf-vfp-poky-linux-gnueabi//usr/include/qtopia/QtGui -I/opt/poky/1.4.1/sysroots/cortexa9hf-vfp-poky-linux-gnueabi//usr/include/qtopia -I. -I. -I../TestFun -I. ../TestFun/mainwindow.h -o moc_mainwindow.cpp arm-poky-linux-gnueabi-g++ -march=armv7-a -marm -mthumb-interwork -mfloat-abi=hard -mtune=cortex-a9 --sysroot=/opt/poky/1.4.1/sysroots/cortexa9hf-vfp-poky-linux-gnueabi -c -pipe -pipe -pipe -O2 -pipe -g -feliminate-unused-debug-types -O2 -pipe -g -feliminate-unused-debug-types -fpermissive -g -g -g -Wall -W -Wall -W -Wall -W -D_REENTRANT
[yocto] any OE/yocto-interested folks in boston up for socializing sometime dec 2-6?
there's a fair-to-middling chance i'll be in boston for a good part of the week of dec 2-6 and mostly being a tourist, so i'll have plenty of free time -- anyone there interested in some kind of yocto-related socializing during that week, perhaps food or beer? i'd be staying in cambridge but i've heard the subway system works just fine so i can tool around on that if need be. i'd be particularly keen on getting together with other OE/yocto/embedded linux trainers/consultants and trading stories and ideas. and if there's any interest in a short seminar of some kind, i'm sure i can be talked into giving a 1-hour talk on yocto or something like that at a LUG or brown bag seminar or what have you. anyway, let me know if there's anything happening in boston that week i'd be interested in, or if anyone wants me to give a free talk on, say, introduction to yocto project somewhere. rday -- Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] chkconfig
Hello all, Is chkconfig part of any image? Also to force what is the best procedure? In my /etc/network/interfaces I have tried the following auto eth0 iface eth0 inet static address 192.168.0.29 hwaddress ether 00:0A:35:00:00:00 netmask 255.255.255.0 network 192.168.0.0 gateway 192.168.0.1 Since I have a router on my network I get an IP using dhcp, if I ifdown eth0 and ifup eth0 then the 192.168.0.29 get setup. Thanks ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[linux-yocto] [PATCH 08/16] media/pci-capture : A feature for PCI media capture devices
From: Nitin A Kamble nitin.a.kam...@intel.com This enables kernel configuration for bunch of PCI media capture devices. Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com --- .../kernel-cache/features/media/pci-capture.cfg| 80 ++ .../kernel-cache/features/media/pci-capture.scc| 8 +++ 2 files changed, 88 insertions(+) create mode 100644 meta/cfg/kernel-cache/features/media/pci-capture.cfg create mode 100644 meta/cfg/kernel-cache/features/media/pci-capture.scc diff --git a/meta/cfg/kernel-cache/features/media/pci-capture.cfg b/meta/cfg/kernel-cache/features/media/pci-capture.cfg new file mode 100644 index 000..232de32 --- /dev/null +++ b/meta/cfg/kernel-cache/features/media/pci-capture.cfg @@ -0,0 +1,80 @@ +# +# Media capture support for PCI devices +# +CONFIG_MEDIA_PCI_SUPPORT=y + +# +# Media capture/analog TV support +# +CONFIG_VIDEO_IVTV=m +CONFIG_VIDEO_IVTV_ALSA=m +CONFIG_VIDEO_FB_IVTV=m + +CONFIG_VIDEO_ZORAN=m +CONFIG_VIDEO_ZORAN_DC30=m +CONFIG_VIDEO_ZORAN_ZR36060=m +# CONFIG_VIDEO_ZORAN_BUZ is not set +CONFIG_VIDEO_ZORAN_DC10=m +CONFIG_VIDEO_ZORAN_LML33=m +CONFIG_VIDEO_ZORAN_LML33R10=m +CONFIG_VIDEO_ZORAN_AVS6EYES=m + +CONFIG_VIDEO_HEXIUM_GEMINI=m +CONFIG_VIDEO_HEXIUM_ORION=m +CONFIG_VIDEO_MXB=m + +# +# Media capture/analog/hybrid TV support +# +CONFIG_VIDEO_CX18=m +CONFIG_VIDEO_CX18_ALSA=m + +CONFIG_VIDEO_CX23885=m +CONFIG_MEDIA_ALTERA_CI=m + +CONFIG_VIDEO_CX25821=m +CONFIG_VIDEO_CX25821_ALSA=m + +CONFIG_VIDEO_CX88=m +CONFIG_VIDEO_CX88_ALSA=m +CONFIG_VIDEO_CX88_BLACKBIRD=m +CONFIG_VIDEO_CX88_DVB=m +CONFIG_VIDEO_CX88_VP3054=m +CONFIG_VIDEO_CX88_MPEG=m + +CONFIG_VIDEO_BT848=m +CONFIG_DVB_BT8XX=m + +CONFIG_VIDEO_SAA7134=m +CONFIG_VIDEO_SAA7134_ALSA=m +CONFIG_VIDEO_SAA7134_RC=y +CONFIG_VIDEO_SAA7134_DVB=m +CONFIG_VIDEO_SAA7164=m + +# +# Media digital TV PCI Adapters +# +CONFIG_DVB_AV7110=m +CONFIG_DVB_AV7110_OSD=y +CONFIG_DVB_BUDGET_CORE=m +CONFIG_DVB_BUDGET=m +CONFIG_DVB_BUDGET_CI=m +CONFIG_DVB_BUDGET_AV=m +CONFIG_DVB_BUDGET_PATCH=m + +CONFIG_DVB_B2C2_FLEXCOP_PCI=m +# CONFIG_DVB_B2C2_FLEXCOP_PCI_DEBUG is not set + +CONFIG_DVB_PLUTO2=m + +CONFIG_DVB_DM1105=m + +CONFIG_DVB_PT1=m + +CONFIG_MANTIS_CORE=m +CONFIG_DVB_MANTIS=m +CONFIG_DVB_HOPPER=m + +CONFIG_DVB_NGENE=m + +CONFIG_DVB_DDBRIDGE=m diff --git a/meta/cfg/kernel-cache/features/media/pci-capture.scc b/meta/cfg/kernel-cache/features/media/pci-capture.scc new file mode 100644 index 000..e24e6c8 --- /dev/null +++ b/meta/cfg/kernel-cache/features/media/pci-capture.scc @@ -0,0 +1,8 @@ +define KFEATURE_DESCRIPTION Enable Configuration For Media PCI Capture Devices +define KFEATURE_COMPATIBILITY all + +include media.scc +include ../pci/pci.scc +include common.scc + +kconf hardware pci-capture.cfg -- 1.8.1.4 ___ linux-yocto mailing list linux-yo...@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 14/16] media/dvb-frontends : A feature for Digital Video Broadcast Devices
From: Nitin A Kamble nitin.a.kam...@intel.com This enables configuration for bunch of Digital Video Broadcast devices. Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com --- .../kernel-cache/features/media/dvb_frontends.cfg | 116 + .../kernel-cache/features/media/dvb_frontends.scc | 6 ++ 2 files changed, 122 insertions(+) create mode 100644 meta/cfg/kernel-cache/features/media/dvb_frontends.cfg create mode 100644 meta/cfg/kernel-cache/features/media/dvb_frontends.scc diff --git a/meta/cfg/kernel-cache/features/media/dvb_frontends.cfg b/meta/cfg/kernel-cache/features/media/dvb_frontends.cfg new file mode 100644 index 000..08d94a1 --- /dev/null +++ b/meta/cfg/kernel-cache/features/media/dvb_frontends.cfg @@ -0,0 +1,116 @@ +# +# Multistandard (satellite) frontends +# +CONFIG_DVB_STB0899=m +CONFIG_DVB_STB6100=m +CONFIG_DVB_STV090x=m +CONFIG_DVB_STV6110x=m + +# +# Multistandard (cable + terrestrial) frontends +# +CONFIG_DVB_DRXK=m +CONFIG_DVB_TDA18271C2DD=m + +# +# DVB-S (satellite) frontends +# +CONFIG_DVB_CX24110=m +CONFIG_DVB_CX24123=m +CONFIG_DVB_MT312=m +CONFIG_DVB_ZL10036=m +CONFIG_DVB_ZL10039=m +CONFIG_DVB_S5H1420=m +CONFIG_DVB_STV0288=m +CONFIG_DVB_STB6000=m +CONFIG_DVB_STV0299=m +CONFIG_DVB_STV6110=m +CONFIG_DVB_STV0900=m +CONFIG_DVB_TDA8083=m +CONFIG_DVB_TDA10086=m +CONFIG_DVB_TDA8261=m +CONFIG_DVB_VES1X93=m +CONFIG_DVB_TUNER_ITD1000=m +CONFIG_DVB_TUNER_CX24113=m +CONFIG_DVB_TDA826X=m +CONFIG_DVB_TUA6100=m +CONFIG_DVB_CX24116=m +CONFIG_DVB_SI21XX=m +CONFIG_DVB_DS3000=m +CONFIG_DVB_MB86A16=m +CONFIG_DVB_TDA10071=m + +# +# DVB-T (terrestrial) frontends +# +CONFIG_DVB_SP8870=m +CONFIG_DVB_SP887X=m +CONFIG_DVB_CX22700=m +CONFIG_DVB_CX22702=m +CONFIG_DVB_DRXD=m +CONFIG_DVB_L64781=m +CONFIG_DVB_TDA1004X=m +CONFIG_DVB_NXT6000=m +CONFIG_DVB_MT352=m +CONFIG_DVB_ZL10353=m +CONFIG_DVB_DIB3000MB=m +CONFIG_DVB_DIB3000MC=m +CONFIG_DVB_DIB7000M=m +CONFIG_DVB_DIB7000P=m +CONFIG_DVB_TDA10048=m +CONFIG_DVB_AF9013=m +CONFIG_DVB_EC100=m +CONFIG_DVB_STV0367=m +CONFIG_DVB_CXD2820R=m +CONFIG_DVB_RTL2830=m +CONFIG_DVB_RTL2832=m + +# +# DVB-C (cable) frontends +# +CONFIG_DVB_VES1820=m +CONFIG_DVB_TDA10021=m +CONFIG_DVB_TDA10023=m +CONFIG_DVB_STV0297=m + +# +# ATSC (North American/Korean Terrestrial/Cable DTV) frontends +# +CONFIG_DVB_NXT200X=m +CONFIG_DVB_OR51211=m +CONFIG_DVB_OR51132=m +CONFIG_DVB_BCM3510=m +CONFIG_DVB_LGDT330X=m +CONFIG_DVB_LGDT3305=m +CONFIG_DVB_LG2160=m +CONFIG_DVB_S5H1409=m +CONFIG_DVB_AU8522=m +CONFIG_DVB_AU8522_DTV=m +CONFIG_DVB_AU8522_V4L=m +CONFIG_DVB_S5H1411=m + +# ISDB-T (terrestrial) frontends +# +CONFIG_DVB_S921=m +CONFIG_DVB_DIB8000=m +CONFIG_DVB_MB86A20S=m + +# +# Digital terrestrial only tuners/PLL +# +CONFIG_DVB_PLL=m +# SEC control devices for DVB-S +# +CONFIG_DVB_LNBP21=m +CONFIG_DVB_LNBP22=m +CONFIG_DVB_ISL6405=m +CONFIG_DVB_ISL6421=m +CONFIG_DVB_ISL6423=m +CONFIG_DVB_A8293=m +CONFIG_DVB_LGS8GXX=m +CONFIG_DVB_ATBM8830=m +CONFIG_DVB_TDA665x=m +CONFIG_DVB_IX2505V=m +CONFIG_DVB_IT913X_FE=m +CONFIG_DVB_M88RS2000=m +CONFIG_DVB_AF9033=m diff --git a/meta/cfg/kernel-cache/features/media/dvb_frontends.scc b/meta/cfg/kernel-cache/features/media/dvb_frontends.scc new file mode 100644 index 000..d3df591 --- /dev/null +++ b/meta/cfg/kernel-cache/features/media/dvb_frontends.scc @@ -0,0 +1,6 @@ +define KFEATURE_DESCRIPTION Enable Configuration For DVB (Digital Video Broadcast) Frontends +define KFEATURE_COMPATIBILITY all + +include media.scc + +kconf hardware dvb_frontends.cfg -- 1.8.1.4 ___ linux-yocto mailing list linux-yo...@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 03/16] remove old MEDIA config fragments
From: Nitin A Kamble nitin.a.kam...@intel.com These are getting replaced with newer extensive MEDIA config fragments. Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com --- .../kernel-cache/features/media/media-camera.cfg| 4 .../kernel-cache/features/media/media-camera.scc| 4 meta/cfg/kernel-cache/features/media/v4l2.cfg | 21 - meta/cfg/kernel-cache/features/media/v4l2.scc | 6 -- meta/cfg/kernel-cache/features/usb/usb-uvcvideo.cfg | 3 --- meta/cfg/kernel-cache/features/usb/usb-uvcvideo.scc | 7 --- 6 files changed, 45 deletions(-) delete mode 100644 meta/cfg/kernel-cache/features/media/media-camera.cfg delete mode 100644 meta/cfg/kernel-cache/features/media/media-camera.scc delete mode 100644 meta/cfg/kernel-cache/features/media/v4l2.cfg delete mode 100644 meta/cfg/kernel-cache/features/media/v4l2.scc delete mode 100644 meta/cfg/kernel-cache/features/usb/usb-uvcvideo.cfg delete mode 100644 meta/cfg/kernel-cache/features/usb/usb-uvcvideo.scc diff --git a/meta/cfg/kernel-cache/features/media/media-camera.cfg b/meta/cfg/kernel-cache/features/media/media-camera.cfg deleted file mode 100644 index 6e173a9..000 --- a/meta/cfg/kernel-cache/features/media/media-camera.cfg +++ /dev/null @@ -1,4 +0,0 @@ -# Enable Multimedia and Camera Device support -CONFIG_MEDIA_SUPPORT=m -CONFIG_MEDIA_CAMERA_SUPPORT=y -CONFIG_MEDIA_SUBDRV_AUTOSELECT=y diff --git a/meta/cfg/kernel-cache/features/media/media-camera.scc b/meta/cfg/kernel-cache/features/media/media-camera.scc deleted file mode 100644 index 15d04e4..000 --- a/meta/cfg/kernel-cache/features/media/media-camera.scc +++ /dev/null @@ -1,4 +0,0 @@ -define KFEATURE_DESCRIPTION Enable camera media device as a module -define KFEATURE_COMPATIBILITY all - -kconf non-hardware media-camera.cfg diff --git a/meta/cfg/kernel-cache/features/media/v4l2.cfg b/meta/cfg/kernel-cache/features/media/v4l2.cfg deleted file mode 100644 index 614886c..000 --- a/meta/cfg/kernel-cache/features/media/v4l2.cfg +++ /dev/null @@ -1,21 +0,0 @@ -# Enable the V4L2 core and API -CONFIG_VIDEO_DEV=m -CONFIG_VIDEO_V4L2=m -VIDEO_V4L2_SUBDEV_API=y - -# Used by drivers that need v4l2-mem2mem.ko -V4L2_MEM2MEM_DEV=m - -# Used by drivers that need Videobuf modules -VIDEOBUF_GEN=m -VIDEOBUF_DMA_SG=m -VIDEOBUF_VMALLOC=m -VIDEOBUF_DMA_CONTIG=m -VIDEOBUF_DVB=m - -# Used by drivers that need Videobuf2 modules -CONFIG_VIDEOBUF2_CORE=m -CONFIG_VIDEOBUF2_MEMOPS=m -CONFIG_VIDEOBUF2_VMALLOC=m -VIDEOBUF2_DMA_CONTIG=m -VIDEOBUF2_DMA_SG=m diff --git a/meta/cfg/kernel-cache/features/media/v4l2.scc b/meta/cfg/kernel-cache/features/media/v4l2.scc deleted file mode 100644 index 09ab7d6..000 --- a/meta/cfg/kernel-cache/features/media/v4l2.scc +++ /dev/null @@ -1,6 +0,0 @@ -define KFEATURE_DESCRIPTION Enable Video for Linux 2 as a module -define KFEATURE_COMPATIBILITY all - -include media-camera.scc - -kconf non-hardware v4l2.cfg diff --git a/meta/cfg/kernel-cache/features/usb/usb-uvcvideo.cfg b/meta/cfg/kernel-cache/features/usb/usb-uvcvideo.cfg deleted file mode 100644 index 366f08b..000 --- a/meta/cfg/kernel-cache/features/usb/usb-uvcvideo.cfg +++ /dev/null @@ -1,3 +0,0 @@ -# Enable USB Video Class camera support -CONFIG_MEDIA_USB_SUPPORT=y -CONFIG_USB_VIDEO_CLASS=m diff --git a/meta/cfg/kernel-cache/features/usb/usb-uvcvideo.scc b/meta/cfg/kernel-cache/features/usb/usb-uvcvideo.scc deleted file mode 100644 index a8cd0f1..000 --- a/meta/cfg/kernel-cache/features/usb/usb-uvcvideo.scc +++ /dev/null @@ -1,7 +0,0 @@ -define KFEATURE_DESCRIPTION Enable USB UVC Video Camera Module -define KFEATURE_COMPATIBILITY board - -include usb-base.scc -include features/media/media-camera.scc - -kconf hardware usb-uvcvideo.cfg -- 1.8.1.4 ___ linux-yocto mailing list linux-yo...@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 07/16] media/i2c: A feature for i2c media devices
From: Nitin A Kamble nitin.a.kam...@intel.com This enables kernel configuration for bunch of i2c media devices. Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com --- meta/cfg/kernel-cache/features/media/i2c.cfg | 74 meta/cfg/kernel-cache/features/media/i2c.scc | 7 +++ 2 files changed, 81 insertions(+) create mode 100644 meta/cfg/kernel-cache/features/media/i2c.cfg create mode 100644 meta/cfg/kernel-cache/features/media/i2c.scc diff --git a/meta/cfg/kernel-cache/features/media/i2c.cfg b/meta/cfg/kernel-cache/features/media/i2c.cfg new file mode 100644 index 000..a59631f --- /dev/null +++ b/meta/cfg/kernel-cache/features/media/i2c.cfg @@ -0,0 +1,74 @@ +# +# Media I2C Support +# + +# +# Encoders, Decoders, Sensors And Other Helper Chips +# +CONFIG_VIDEO_IR_I2C=y +CONFIG_VIDEO_TVAUDIO=m +CONFIG_VIDEO_TDA7432=m +CONFIG_VIDEO_TDA9840=m +CONFIG_VIDEO_TEA6415C=m +CONFIG_VIDEO_TEA6420=m +CONFIG_VIDEO_MSP3400=m +CONFIG_VIDEO_CS5345=m +CONFIG_VIDEO_CS53L32A=m +CONFIG_VIDEO_WM8775=m +CONFIG_VIDEO_WM8739=m +CONFIG_VIDEO_VP27SMPX=m + +# +# RDS decoders +# +CONFIG_VIDEO_SAA6588=m + +# +# Video decoders +# +CONFIG_VIDEO_BT819=m +CONFIG_VIDEO_BT856=m +CONFIG_VIDEO_BT866=m +CONFIG_VIDEO_KS0127=m +CONFIG_VIDEO_SAA7110=m +CONFIG_VIDEO_SAA711X=m +CONFIG_VIDEO_TVP5150=m +CONFIG_VIDEO_VPX3220=m + +# +# Video and audio decoders +# +CONFIG_VIDEO_SAA717X=m +CONFIG_VIDEO_CX25840=m + +# +# MPEG video encoders +# +CONFIG_VIDEO_CX2341X=m + +# +# Video encoders +# +CONFIG_VIDEO_SAA7127=m +CONFIG_VIDEO_ADV7170=m +CONFIG_VIDEO_ADV7175=m + +# +# Camera sensor devices +# +CONFIG_VIDEO_MT9V011=m + +# +# Flash devices +# + +# +# Video improvement chips +# +CONFIG_VIDEO_UPD64031A=m +CONFIG_VIDEO_UPD64083=m + +# +# Miscelaneous helper chips +# +CONFIG_VIDEO_M52790=m diff --git a/meta/cfg/kernel-cache/features/media/i2c.scc b/meta/cfg/kernel-cache/features/media/i2c.scc new file mode 100644 index 000..195266b --- /dev/null +++ b/meta/cfg/kernel-cache/features/media/i2c.scc @@ -0,0 +1,7 @@ +define KFEATURE_DESCRIPTION Enable Configuration For I2C Media devices +define KFEATURE_COMPATIBILITY all + +include media.scc +include ../i2c/i2c.scc + +kconf hardware i2c.cfg -- 1.8.1.4 ___ linux-yocto mailing list linux-yo...@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 05/16] media/common : A feature for common media support
From: Nitin A Kamble nitin.a.kam...@intel.com This enables the kernel configuration for media support common to some PCI and USB media devices. Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com --- meta/cfg/kernel-cache/features/media/common.cfg | 15 +++ meta/cfg/kernel-cache/features/media/common.scc | 6 ++ 2 files changed, 21 insertions(+) create mode 100644 meta/cfg/kernel-cache/features/media/common.cfg create mode 100644 meta/cfg/kernel-cache/features/media/common.scc diff --git a/meta/cfg/kernel-cache/features/media/common.cfg b/meta/cfg/kernel-cache/features/media/common.cfg new file mode 100644 index 000..bb5db0b --- /dev/null +++ b/meta/cfg/kernel-cache/features/media/common.cfg @@ -0,0 +1,15 @@ +# +# Media Common Options +# +CONFIG_MEDIA_COMMON_OPTIONS=y + +CONFIG_DVB_B2C2_FLEXCOP=m + +CONFIG_VIDEO_SAA7146=m +CONFIG_VIDEO_SAA7146_VV=m + +CONFIG_SMS_SIANO_MDTV=m +CONFIG_SMS_SIANO_RC=y + +CONFIG_VIDEO_BTCX=m +CONFIG_VIDEO_TVEEPROM=m diff --git a/meta/cfg/kernel-cache/features/media/common.scc b/meta/cfg/kernel-cache/features/media/common.scc new file mode 100644 index 000..e3df51d --- /dev/null +++ b/meta/cfg/kernel-cache/features/media/common.scc @@ -0,0 +1,6 @@ +define KFEATURE_DESCRIPTION Enable Common Media Options +define KFEATURE_COMPATIBILITY all + +include media.scc + +kconf hardware common.cfg -- 1.8.1.4 ___ linux-yocto mailing list linux-yo...@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 06/16] media/usb: A feature for USB media devices.
From: Nitin A Kamble nitin.a.kam...@intel.com This enables various USB media devices. Many of the USB webcams drivers are enabled here. Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com --- meta/cfg/kernel-cache/features/media/usb.cfg | 76 meta/cfg/kernel-cache/features/media/usb.scc | 7 +++ 2 files changed, 83 insertions(+) create mode 100644 meta/cfg/kernel-cache/features/media/usb.cfg create mode 100644 meta/cfg/kernel-cache/features/media/usb.scc diff --git a/meta/cfg/kernel-cache/features/media/usb.cfg b/meta/cfg/kernel-cache/features/media/usb.cfg new file mode 100644 index 000..12ac598 --- /dev/null +++ b/meta/cfg/kernel-cache/features/media/usb.cfg @@ -0,0 +1,76 @@ +# Support For USB Media Adapters/devices +CONFIG_MEDIA_USB_SUPPORT=y + +# USB Video Class Webcam Drivers +CONFIG_USB_VIDEO_CLASS=m +CONFIG_USB_VIDEO_CLASS_INPUT_EVDEV=y + +# USB GSPCA Webcam Drivers +CONFIG_USB_GSPCA=m +CONFIG_USB_M5602=m +CONFIG_USB_STV06XX=m +CONFIG_USB_GL860=m +CONFIG_USB_GSPCA_BENQ=m +CONFIG_USB_GSPCA_CONEX=m +CONFIG_USB_GSPCA_CPIA1=m +CONFIG_USB_GSPCA_ETOMS=m +CONFIG_USB_GSPCA_FINEPIX=m +CONFIG_USB_GSPCA_JEILINJ=m +CONFIG_USB_GSPCA_JL2005BCD=m +CONFIG_USB_GSPCA_KINECT=m +CONFIG_USB_GSPCA_KONICA=m +CONFIG_USB_GSPCA_MARS=m +CONFIG_USB_GSPCA_MR97310A=m +CONFIG_USB_GSPCA_NW80X=m +CONFIG_USB_GSPCA_OV519=m +CONFIG_USB_GSPCA_OV534=m +CONFIG_USB_GSPCA_OV534_9=m +CONFIG_USB_GSPCA_PAC207=m +CONFIG_USB_GSPCA_PAC7302=m +CONFIG_USB_GSPCA_PAC7311=m +CONFIG_USB_GSPCA_SE401=m +CONFIG_USB_GSPCA_SN9C2028=m +CONFIG_USB_GSPCA_SN9C20X=m +CONFIG_USB_GSPCA_SONIXB=m +CONFIG_USB_GSPCA_SONIXJ=m +CONFIG_USB_GSPCA_SPCA500=m +CONFIG_USB_GSPCA_SPCA501=m +CONFIG_USB_GSPCA_SPCA505=m +CONFIG_USB_GSPCA_SPCA506=m +CONFIG_USB_GSPCA_SPCA508=m +CONFIG_USB_GSPCA_SPCA561=m +CONFIG_USB_GSPCA_SPCA1528=m +CONFIG_USB_GSPCA_SQ905=m +CONFIG_USB_GSPCA_SQ905C=m +CONFIG_USB_GSPCA_SQ930X=m +CONFIG_USB_GSPCA_STK014=m +CONFIG_USB_GSPCA_STV0680=m +CONFIG_USB_GSPCA_SUNPLUS=m +CONFIG_USB_GSPCA_T613=m +CONFIG_USB_GSPCA_TOPRO=m +CONFIG_USB_GSPCA_TV8532=m +CONFIG_USB_GSPCA_VC032X=m +CONFIG_USB_GSPCA_VICAM=m +CONFIG_USB_GSPCA_XIRLINK_CIT=m +CONFIG_USB_GSPCA_ZC3XX=m + +# USB Philips Camera Drivers +CONFIG_USB_PWC=m +# CONFIG_USB_PWC_DEBUG is not set +CONFIG_USB_PWC_INPUT_EVDEV=y + +# Vision's CPiA2 (Colour Processor Interface ASIC) Camera Drivers +CONFIG_VIDEO_CPIA2=m + +# CONFIG_USB_ZR364XX is not set + +# USB Syntek DC1125 Camera Support +CONFIG_USB_STKWEBCAM=m + +# USB Sensoray 2255 video capture Device +CONFIG_USB_S2255=m + +# USB SN9C1xx PC Camera Controller Support +CONFIG_USB_SN9C102=m + +# CONFIG_USB_G_WEBCAM is not set diff --git a/meta/cfg/kernel-cache/features/media/usb.scc b/meta/cfg/kernel-cache/features/media/usb.scc new file mode 100644 index 000..5602311 --- /dev/null +++ b/meta/cfg/kernel-cache/features/media/usb.scc @@ -0,0 +1,7 @@ +define KFEATURE_DESCRIPTION Enable Configuration For USB Media Adapters +define KFEATURE_COMPATIBILITY all + +include media.scc +include ../usb/usb-base.cfg + +kconf hardware usb.cfg -- 1.8.1.4 ___ linux-yocto mailing list linux-yo...@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 01/16] minnow.cfg: Enable TEA575X sound driver
From: Nitin A Kamble nitin.a.kam...@intel.com The TEA575X sound driver configuration is relocated from the kernel recipe's media.cfg to here. Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com --- meta/cfg/kernel-cache/bsp/minnow/minnow.cfg | 1 + 1 file changed, 1 insertion(+) diff --git a/meta/cfg/kernel-cache/bsp/minnow/minnow.cfg b/meta/cfg/kernel-cache/bsp/minnow/minnow.cfg index 2be4ea4..b08f411 100644 --- a/meta/cfg/kernel-cache/bsp/minnow/minnow.cfg +++ b/meta/cfg/kernel-cache/bsp/minnow/minnow.cfg @@ -8,6 +8,7 @@ CONFIG_MTRR=y # Basic hardware support for the box - network, USB, PCI, sound CONFIG_PCI=y CONFIG_PCIEPORTBUS=y +CONFIG_SND_TEA575X=m # Ensure we can boot over MMC CONFIG_MMC=y -- 1.8.1.4 ___ linux-yocto mailing list linux-yo...@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 10/16] media/radio : A feature for AM/FM radio devices
From: Nitin A Kamble nitin.a.kam...@intel.com This enables kernel configuration for various AM/FM radio devices. Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com --- meta/cfg/kernel-cache/features/media/radio.cfg | 24 meta/cfg/kernel-cache/features/media/radio.scc | 6 ++ 2 files changed, 30 insertions(+) create mode 100644 meta/cfg/kernel-cache/features/media/radio.cfg create mode 100644 meta/cfg/kernel-cache/features/media/radio.scc diff --git a/meta/cfg/kernel-cache/features/media/radio.cfg b/meta/cfg/kernel-cache/features/media/radio.cfg new file mode 100644 index 000..2cbedf2 --- /dev/null +++ b/meta/cfg/kernel-cache/features/media/radio.cfg @@ -0,0 +1,24 @@ +# +# Media AM/FM Radio Adapters +# +CONFIG_RADIO_ADAPTERS=y +CONFIG_RADIO_SI470X=y +CONFIG_USB_SI470X=m +CONFIG_I2C_SI470X=m +CONFIG_USB_MR800=m +CONFIG_USB_DSBR=m +CONFIG_RADIO_MAXIRADIO=m +CONFIG_RADIO_SHARK=m +CONFIG_RADIO_SHARK2=m +CONFIG_I2C_SI4713=m +CONFIG_RADIO_SI4713=m +CONFIG_USB_KEENE=m +CONFIG_RADIO_TEA5764=m +CONFIG_RADIO_SAA7706H=m +CONFIG_RADIO_TEF6862=m +CONFIG_RADIO_WL1273=m + +# +# Multi Function Device Radio +# +CONFIG_MFD_WL1273_CORE=m diff --git a/meta/cfg/kernel-cache/features/media/radio.scc b/meta/cfg/kernel-cache/features/media/radio.scc new file mode 100644 index 000..4844a4c --- /dev/null +++ b/meta/cfg/kernel-cache/features/media/radio.scc @@ -0,0 +1,6 @@ +define KFEATURE_DESCRIPTION Enable Configuration for Radio Adapters +define KFEATURE_COMPATIBILITY all + +include media.scc + +kconf hardware radio.cfg -- 1.8.1.4 ___ linux-yocto mailing list linux-yo...@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 04/16] media.scc : A feature for Media infrastructure
From: Nitin A Kamble nitin.a.kam...@intel.com This replaces the previous limited media config fragments. Other hardware media features depends on this feature. Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com --- meta/cfg/kernel-cache/features/media/media.cfg | 54 ++ meta/cfg/kernel-cache/features/media/media.scc | 4 ++ 2 files changed, 58 insertions(+) create mode 100644 meta/cfg/kernel-cache/features/media/media.cfg create mode 100644 meta/cfg/kernel-cache/features/media/media.scc diff --git a/meta/cfg/kernel-cache/features/media/media.cfg b/meta/cfg/kernel-cache/features/media/media.cfg new file mode 100644 index 000..b7b5f5e --- /dev/null +++ b/meta/cfg/kernel-cache/features/media/media.cfg @@ -0,0 +1,54 @@ +# +# Enable support for multimedia devices such as webcams and Video grabber devices +# +CONFIG_MEDIA_SUPPORT=m +CONFIG_MEDIA_CAMERA_SUPPORT=y +CONFIG_MEDIA_ANALOG_TV_SUPPORT=y +CONFIG_MEDIA_DIGITAL_TV_SUPPORT=y +CONFIG_MEDIA_RADIO_SUPPORT=y +CONFIG_MEDIA_CONTROLLER=y + +# +# Enable the V4L2 core and API +# +CONFIG_VIDEO_DEV=m +CONFIG_VIDEO_V4L2=m +CONFIG_VIDEO_V4L2_SUBDEV_API=y + +# +# Used by drivers that need v4l2-mem2mem.ko +# +CONFIG_V4L2_MEM2MEM_DEV=m + +# +# Used by drivers that need Videobuf modules +# +CONFIG_VIDEOBUF_GEN=m +CONFIG_VIDEOBUF_DMA_SG=m +CONFIG_VIDEOBUF_DMA_CONTIG=m +CONFIG_VIDEOBUF_VMALLOC=m +CONFIG_VIDEOBUF_DVB=m + +# +# Used by drivers that need Videobuf2 modules +# +CONFIG_VIDEOBUF2_CORE=m +CONFIG_VIDEOBUF2_MEMOPS=m +CONFIG_VIDEOBUF2_DMA_SG=m +CONFIG_VIDEOBUF2_DMA_CONTIG=m +CONFIG_VIDEOBUF2_VMALLOC=m + +# +# Digital Video Broadcast support +# +CONFIG_DVB_CORE=y +CONFIG_DVB_NET=y +CONFIG_DVB_MAX_ADAPTERS=8 +CONFIG_DVB_DYNAMIC_MINORS=y + +# +# Autoselect ancillary drivers (tuners, sensors, i2c, frontends) +# +CONFIG_MEDIA_SUBDRV_AUTOSELECT=y + +CONFIG_MEDIA_ATTACH=y diff --git a/meta/cfg/kernel-cache/features/media/media.scc b/meta/cfg/kernel-cache/features/media/media.scc new file mode 100644 index 000..838782d --- /dev/null +++ b/meta/cfg/kernel-cache/features/media/media.scc @@ -0,0 +1,4 @@ +define KFEATURE_DESCRIPTION Enable support for multimedia devices such as webcams and Video grabber devices +define KFEATURE_COMPATIBILITY all + +kconf non-hardware media.cfg -- 1.8.1.4 ___ linux-yocto mailing list linux-yo...@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 11/16] media/rc : A feature for remote control media devices
From: Nitin A Kamble nitin.a.kam...@intel.com This enables kernel configuration for bunch of remote control media devices. Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com --- meta/cfg/kernel-cache/features/media/rc.cfg | 18 ++ meta/cfg/kernel-cache/features/media/rc.scc | 6 ++ 2 files changed, 24 insertions(+) create mode 100644 meta/cfg/kernel-cache/features/media/rc.cfg create mode 100644 meta/cfg/kernel-cache/features/media/rc.scc diff --git a/meta/cfg/kernel-cache/features/media/rc.cfg b/meta/cfg/kernel-cache/features/media/rc.cfg new file mode 100644 index 000..f8a345e --- /dev/null +++ b/meta/cfg/kernel-cache/features/media/rc.cfg @@ -0,0 +1,18 @@ +# support for remote control +CONFIG_MEDIA_RC_SUPPORT=y +CONFIG_RC_CORE=y +CONFIG_RC_MAP=y +CONFIG_RC_DECODERS=y + +# Support for Infra Red devices +CONFIG_LIRC=m +CONFIG_IR_LIRC_CODEC=m +CONFIG_IR_NEC_DECODER=y +CONFIG_IR_RC5_DECODER=y +CONFIG_IR_RC6_DECODER=y +CONFIG_IR_JVC_DECODER=y +CONFIG_IR_SONY_DECODER=y +CONFIG_IR_RC5_SZ_DECODER=y +CONFIG_IR_SANYO_DECODER=y +CONFIG_IR_MCE_KBD_DECODER=y + diff --git a/meta/cfg/kernel-cache/features/media/rc.scc b/meta/cfg/kernel-cache/features/media/rc.scc new file mode 100644 index 000..7ee158f --- /dev/null +++ b/meta/cfg/kernel-cache/features/media/rc.scc @@ -0,0 +1,6 @@ +define KFEATURE_DESCRIPTION Enable Configuration For Remote Control Media Devices +define KFEATURE_COMPATIBILITY all + +include media.scc + +kconf hardware rc.cfg -- 1.8.1.4 ___ linux-yocto mailing list linux-yo...@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 12/16] media/tuners: A feature for tuner media devices
From: Nitin A Kamble nitin.a.kam...@intel.com This enables kernel configuration for tuner media devices Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com --- meta/cfg/kernel-cache/features/media/tuners.cfg | 30 + meta/cfg/kernel-cache/features/media/tuners.scc | 7 ++ 2 files changed, 37 insertions(+) create mode 100644 meta/cfg/kernel-cache/features/media/tuners.cfg create mode 100644 meta/cfg/kernel-cache/features/media/tuners.scc diff --git a/meta/cfg/kernel-cache/features/media/tuners.cfg b/meta/cfg/kernel-cache/features/media/tuners.cfg new file mode 100644 index 000..90d8f47 --- /dev/null +++ b/meta/cfg/kernel-cache/features/media/tuners.cfg @@ -0,0 +1,30 @@ +CONFIG_VIDEO_TUNER=m +CONFIG_MEDIA_TUNER=y +CONFIG_MEDIA_TUNER_SIMPLE=y +CONFIG_MEDIA_TUNER_TDA8290=y +CONFIG_MEDIA_TUNER_TDA827X=y +CONFIG_MEDIA_TUNER_TDA18271=y +CONFIG_MEDIA_TUNER_TDA9887=y +CONFIG_MEDIA_TUNER_TEA5761=y +CONFIG_MEDIA_TUNER_TEA5767=y +CONFIG_MEDIA_TUNER_MT20XX=y +CONFIG_MEDIA_TUNER_MT2060=m +CONFIG_MEDIA_TUNER_MT2063=m +CONFIG_MEDIA_TUNER_MT2266=m +CONFIG_MEDIA_TUNER_MT2131=m +CONFIG_MEDIA_TUNER_QT1010=m +CONFIG_MEDIA_TUNER_XC2028=y +CONFIG_MEDIA_TUNER_XC5000=y +CONFIG_MEDIA_TUNER_XC4000=y +CONFIG_MEDIA_TUNER_MXL5005S=m +CONFIG_MEDIA_TUNER_MXL5007T=m +CONFIG_MEDIA_TUNER_MC44S803=y +CONFIG_MEDIA_TUNER_MAX2165=m +CONFIG_MEDIA_TUNER_TDA18218=m +CONFIG_MEDIA_TUNER_FC0011=m +CONFIG_MEDIA_TUNER_FC0012=m +CONFIG_MEDIA_TUNER_FC0013=m +CONFIG_MEDIA_TUNER_TDA18212=m +CONFIG_MEDIA_TUNER_E4000=m +CONFIG_MEDIA_TUNER_FC2580=m +CONFIG_MEDIA_TUNER_TUA9001=m diff --git a/meta/cfg/kernel-cache/features/media/tuners.scc b/meta/cfg/kernel-cache/features/media/tuners.scc new file mode 100644 index 000..d6965cb --- /dev/null +++ b/meta/cfg/kernel-cache/features/media/tuners.scc @@ -0,0 +1,7 @@ +define KFEATURE_DESCRIPTION Enable Configuration For Tuner Media Devices +define KFEATURE_COMPATIBILITY all + +include media.scc +include ../i2c/i2c.scc + +kconf hardware tuners.cfg -- 1.8.1.4 ___ linux-yocto mailing list linux-yo...@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 13/16] media/usb_tv: A feature for usb tv media adapters
From: Nitin A Kamble nitin.a.kam...@intel.com This enables kernel configuration fo bunch of USB TV adapters. Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com --- meta/cfg/kernel-cache/features/media/usb_tv.cfg | 82 + meta/cfg/kernel-cache/features/media/usb_tv.scc | 8 +++ 2 files changed, 90 insertions(+) create mode 100644 meta/cfg/kernel-cache/features/media/usb_tv.cfg create mode 100644 meta/cfg/kernel-cache/features/media/usb_tv.scc diff --git a/meta/cfg/kernel-cache/features/media/usb_tv.cfg b/meta/cfg/kernel-cache/features/media/usb_tv.cfg new file mode 100644 index 000..4641fa1 --- /dev/null +++ b/meta/cfg/kernel-cache/features/media/usb_tv.cfg @@ -0,0 +1,82 @@ +# +# Analog TV USB devices +# +CONFIG_VIDEO_AU0828=m +CONFIG_VIDEO_PVRUSB2=m +CONFIG_VIDEO_PVRUSB2_SYSFS=y +CONFIG_VIDEO_PVRUSB2_DVB=y +# CONFIG_VIDEO_PVRUSB2_DEBUGIFC is not set +CONFIG_VIDEO_HDPVR=m +CONFIG_VIDEO_TLG2300=m +CONFIG_VIDEO_USBVISION=m +CONFIG_VIDEO_STK1160=m +# CONFIG_VIDEO_STK1160_AC97 is not set + +# +# Analog/digital TV USB devices +# +CONFIG_VIDEO_CX231XX=m +CONFIG_VIDEO_CX231XX_RC=y +CONFIG_VIDEO_CX231XX_ALSA=m +CONFIG_VIDEO_CX231XX_DVB=m +CONFIG_VIDEO_TM6000=m +CONFIG_VIDEO_TM6000_ALSA=m +CONFIG_VIDEO_TM6000_DVB=m + +# +# Digital TV USB devices +# +CONFIG_DVB_USB=m +# CONFIG_DVB_USB_DEBUG is not set +CONFIG_DVB_USB_A800=m +CONFIG_DVB_USB_DIBUSB_MB=m +# CONFIG_DVB_USB_DIBUSB_MB_FAULTY is not set +CONFIG_DVB_USB_DIBUSB_MC=m +CONFIG_DVB_USB_DIB0700=m +CONFIG_DVB_USB_UMT_010=m +CONFIG_DVB_USB_CXUSB=m +CONFIG_DVB_USB_M920X=m +CONFIG_DVB_USB_DIGITV=m +CONFIG_DVB_USB_VP7045=m +CONFIG_DVB_USB_VP702X=m +CONFIG_DVB_USB_GP8PSK=m +CONFIG_DVB_USB_NOVA_T_USB2=m +CONFIG_DVB_USB_TTUSB2=m +CONFIG_DVB_USB_DTT200U=m +CONFIG_DVB_USB_OPERA1=m +CONFIG_DVB_USB_AF9005=m +CONFIG_DVB_USB_AF9005_REMOTE=m +CONFIG_DVB_USB_PCTV452E=m +CONFIG_DVB_USB_DW2102=m +CONFIG_DVB_USB_CINERGY_T2=m +CONFIG_DVB_USB_DTV5100=m +CONFIG_DVB_USB_FRIIO=m +CONFIG_DVB_USB_AZ6027=m +CONFIG_DVB_USB_TECHNISAT_USB2=m +CONFIG_DVB_USB_V2=m +CONFIG_DVB_USB_CYPRESS_FIRMWARE=m +CONFIG_DVB_USB_AF9015=m +CONFIG_DVB_USB_AF9035=m +CONFIG_DVB_USB_ANYSEE=m +CONFIG_DVB_USB_AU6610=m +CONFIG_DVB_USB_AZ6007=m +CONFIG_DVB_USB_CE6230=m +CONFIG_DVB_USB_EC168=m +CONFIG_DVB_USB_GL861=m +CONFIG_DVB_USB_IT913X=m +CONFIG_DVB_USB_LME2510=m +CONFIG_DVB_USB_MXL111SF=m +CONFIG_DVB_USB_RTL28XXU=m +CONFIG_DVB_TTUSB_BUDGET=m +CONFIG_DVB_TTUSB_DEC=m +CONFIG_SMS_USB_DRV=m +CONFIG_DVB_B2C2_FLEXCOP_USB=m +# CONFIG_DVB_B2C2_FLEXCOP_USB_DEBUG is not set + +# +# Webcam, TV (analog/digital) USB devices +# +CONFIG_VIDEO_EM28XX=m +CONFIG_VIDEO_EM28XX_ALSA=m +CONFIG_VIDEO_EM28XX_DVB=m +CONFIG_VIDEO_EM28XX_RC=m diff --git a/meta/cfg/kernel-cache/features/media/usb_tv.scc b/meta/cfg/kernel-cache/features/media/usb_tv.scc new file mode 100644 index 000..c7417ac --- /dev/null +++ b/meta/cfg/kernel-cache/features/media/usb_tv.scc @@ -0,0 +1,8 @@ +define KFEATURE_DESCRIPTION Enable Configuration For USB TV adapters +define KFEATURE_COMPATIBILITY all + +include usb.scc +include ../i2c/i2c.scc +include common.scc + +kconf hardware usb_tv.cfg -- 1.8.1.4 ___ linux-yocto mailing list linux-yo...@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 02/16] firmware.scc/cfg : Feature for firmware loading
From: Nitin A Kamble nitin.a.kam...@intel.com This enables the kernel configuration for firmware loading. Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com --- meta/cfg/kernel-cache/features/firmware/firmware.cfg | 8 meta/cfg/kernel-cache/features/firmware/firmware.scc | 4 2 files changed, 12 insertions(+) create mode 100644 meta/cfg/kernel-cache/features/firmware/firmware.cfg create mode 100644 meta/cfg/kernel-cache/features/firmware/firmware.scc diff --git a/meta/cfg/kernel-cache/features/firmware/firmware.cfg b/meta/cfg/kernel-cache/features/firmware/firmware.cfg new file mode 100644 index 000..7331ab3 --- /dev/null +++ b/meta/cfg/kernel-cache/features/firmware/firmware.cfg @@ -0,0 +1,8 @@ +CONFIG_FW_LOADER=m +CONFIG_FIRMWARE_IN_KERNEL=y +CONFIG_EXTRA_FIRMWARE= + +# +# Altera FPGA firmware download module +# +CONFIG_ALTERA_STAPL=m diff --git a/meta/cfg/kernel-cache/features/firmware/firmware.scc b/meta/cfg/kernel-cache/features/firmware/firmware.scc new file mode 100644 index 000..09432a8 --- /dev/null +++ b/meta/cfg/kernel-cache/features/firmware/firmware.scc @@ -0,0 +1,4 @@ +define KFEATURE_DESCRIPTION Firmware loading support +define KFEATURE_COMPATIBILITY all + +kconf non-hardware firmware.cfg -- 1.8.1.4 ___ linux-yocto mailing list linux-yo...@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 16/16] common-pc-64.scc: update as per changes in the media config fragments
From: Nitin A Kamble nitin.a.kam...@intel.com Some of the media config fragments are replaced by more extensive media fragments. Changes this BSP config accordingly. Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com --- meta/cfg/kernel-cache/bsp/common-pc-64/common-pc-64.scc | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/meta/cfg/kernel-cache/bsp/common-pc-64/common-pc-64.scc b/meta/cfg/kernel-cache/bsp/common-pc-64/common-pc-64.scc index 936df98..7d6eb2a 100644 --- a/meta/cfg/kernel-cache/bsp/common-pc-64/common-pc-64.scc +++ b/meta/cfg/kernel-cache/bsp/common-pc-64/common-pc-64.scc @@ -21,8 +21,7 @@ include features/power/intel.scc include cfg/8250.scc # webcam -include features/usb/usb-uvcvideo.scc -include features/media/v4l2.scc +include features/media/usb.scc # sugarbay graphics include features/i915/i915.scc -- 1.8.1.4 ___ linux-yocto mailing list linux-yo...@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 00/16] linux-yocto-3.10: config fragments for minnow BSP
From: Nitin A Kamble nitin.a.kam...@intel.com This patch series imports the 500 line media.cfg from the kernel recipe in to the linux-yocto-3.10 meta branch, by splitting it into many fragments. It replaces some of the existing webcam media fragments, and hence BSPs configs using the old media fragments is changed accordingly. This has been tested the following way. * It gives the same minnow kernel config as with the big media.cfg on SRC_URI * This changes the kernel config for sugarbay and genericx86-64 BSPs, and the sugarbay BSP is validated to work as expected with this change. Thanks, Nitin The following changes since commit 4a04774a6562ab37a769404920e070b70acf3c4c: minnow: Remove branch statements from minnow scc files (2013-11-14 22:56:03 -0500) are available in the git repository at: git://git.yoctoproject.org/linux-yocto-contrib nitin/meta http://git.yoctoproject.org/cgit.cgi/linux-yocto-contrib/log/?h=nitin/meta Nitin A Kamble (16): minnow.cfg: Enable TEA575X sound driver firmware.scc/cfg : Feature for firmware loading remove old MEDIA config fragments media.scc : A feature for Media infrastructure media/common : A feature for common media support media/usb: A feature for USB media devices. media/i2c: A feature for i2c media devices media/pci-capture : A feature for PCI media capture devices media/platform : A feature for platform media devices media/radio : A feature for AM/FM radio devices media/rc : A feature for remote control media devices media/tuners: A feature for tuner media devices media/usb_tv: A feature for usb tv media adapters media/dvb-frontends : A feature for Digital Video Broadcast Devices minnow.scc: enable media firmware features common-pc-64.scc: update as per changes in the media config fragments .../kernel-cache/bsp/common-pc-64/common-pc-64.scc | 3 +- meta/cfg/kernel-cache/bsp/minnow/minnow.cfg| 1 + meta/cfg/kernel-cache/bsp/minnow/minnow.scc| 9 ++ .../kernel-cache/features/firmware/firmware.cfg| 8 ++ .../kernel-cache/features/firmware/firmware.scc| 4 + meta/cfg/kernel-cache/features/media/common.cfg| 15 +++ meta/cfg/kernel-cache/features/media/common.scc| 6 ++ .../kernel-cache/features/media/dvb_frontends.cfg | 116 + .../kernel-cache/features/media/dvb_frontends.scc | 6 ++ meta/cfg/kernel-cache/features/media/i2c.cfg | 74 + meta/cfg/kernel-cache/features/media/i2c.scc | 7 ++ .../kernel-cache/features/media/media-camera.cfg | 4 - .../kernel-cache/features/media/media-camera.scc | 4 - meta/cfg/kernel-cache/features/media/media.cfg | 54 ++ meta/cfg/kernel-cache/features/media/media.scc | 4 + .../kernel-cache/features/media/pci-capture.cfg| 80 ++ .../kernel-cache/features/media/pci-capture.scc| 8 ++ meta/cfg/kernel-cache/features/media/platform.cfg | 15 +++ meta/cfg/kernel-cache/features/media/platform.scc | 6 ++ meta/cfg/kernel-cache/features/media/radio.cfg | 24 + meta/cfg/kernel-cache/features/media/radio.scc | 6 ++ meta/cfg/kernel-cache/features/media/rc.cfg| 18 meta/cfg/kernel-cache/features/media/rc.scc| 6 ++ meta/cfg/kernel-cache/features/media/tuners.cfg| 30 ++ meta/cfg/kernel-cache/features/media/tuners.scc| 7 ++ meta/cfg/kernel-cache/features/media/usb.cfg | 76 ++ meta/cfg/kernel-cache/features/media/usb.scc | 7 ++ meta/cfg/kernel-cache/features/media/usb_tv.cfg| 82 +++ meta/cfg/kernel-cache/features/media/usb_tv.scc| 8 ++ meta/cfg/kernel-cache/features/media/v4l2.cfg | 21 meta/cfg/kernel-cache/features/media/v4l2.scc | 6 -- .../cfg/kernel-cache/features/usb/usb-uvcvideo.cfg | 3 - .../cfg/kernel-cache/features/usb/usb-uvcvideo.scc | 7 -- 33 files changed, 678 insertions(+), 47 deletions(-) create mode 100644 meta/cfg/kernel-cache/features/firmware/firmware.cfg create mode 100644 meta/cfg/kernel-cache/features/firmware/firmware.scc create mode 100644 meta/cfg/kernel-cache/features/media/common.cfg create mode 100644 meta/cfg/kernel-cache/features/media/common.scc create mode 100644 meta/cfg/kernel-cache/features/media/dvb_frontends.cfg create mode 100644 meta/cfg/kernel-cache/features/media/dvb_frontends.scc create mode 100644 meta/cfg/kernel-cache/features/media/i2c.cfg create mode 100644 meta/cfg/kernel-cache/features/media/i2c.scc delete mode 100644 meta/cfg/kernel-cache/features/media/media-camera.cfg delete mode 100644 meta/cfg/kernel-cache/features/media/media-camera.scc create mode 100644 meta/cfg/kernel-cache/features/media/media.cfg create mode 100644 meta/cfg/kernel-cache/features/media/media.scc create mode 100644 meta/cfg/kernel-cache/features/media/pci-capture.cfg create mode 100644 meta/cfg/kernel-cache/features/media/pci-capture.scc create mode 100644
[linux-yocto] [PATCH] bridge: enable EBTABLES
From: Michel Thebeau michel.theb...@windriver.com All the BRIDGE_EBT configs depend on EBTABLES. Add the additional BRIDGE_EBT configs per request. Signed-off-by: Michel Thebeau michel.theb...@windriver.com --- Hi Bruce, Per our conversation, you wanted this on the linux-yocto list. This is needed for libvirtd to run /sbin/ebtables. M meta/cfg/kernel-cache/cfg/net/bridge.cfg | 4 1 file changed, 4 insertions(+) diff --git a/meta/cfg/kernel-cache/cfg/net/bridge.cfg b/meta/cfg/kernel-cache/cfg/net/bridge.cfg index 8b8016d..00d61c0 100644 --- a/meta/cfg/kernel-cache/cfg/net/bridge.cfg +++ b/meta/cfg/kernel-cache/cfg/net/bridge.cfg @@ -20,3 +20,7 @@ CONFIG_BRIDGE_EBT_MARK_T=m CONFIG_BRIDGE_EBT_REDIRECT=m CONFIG_BRIDGE_EBT_SNAT=m CONFIG_BRIDGE_EBT_LOG=m +CONFIG_BRIDGE_EBT_IP6=m +CONFIG_BRIDGE_EBT_NFLOG=m +CONFIG_BRIDGE_EBT_ULOG=m +CONFIG_BRIDGE_NF_EBTABLES=m -- 1.8.4.93.g57e4c17 ___ linux-yocto mailing list linux-yo...@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 00/16] linux-yocto-3.10: config fragments for minnow BSP
On Fri, 2013-11-22 at 11:36 -0800, nitin.a.kam...@intel.com wrote: From: Nitin A Kamble nitin.a.kam...@intel.com This patch series imports the 500 line media.cfg from the kernel recipe in to the linux-yocto-3.10 meta branch, by splitting it into many fragments. It replaces some of the existing webcam media fragments, and hence BSPs configs using the old media fragments is changed accordingly. This has been tested the following way. * It gives the same minnow kernel config as with the big media.cfg on SRC_URI * This changes the kernel config for sugarbay and genericx86-64 BSPs, and the sugarbay BSP is validated to work as expected with this change. Fantastic, thank you Nitin. Did you also verify that no new issues are reported by the config validation task and logged in the .meta/standard/$KMACHINE/* log files? missing, etc? -- Darren Thanks, Nitin The following changes since commit 4a04774a6562ab37a769404920e070b70acf3c4c: minnow: Remove branch statements from minnow scc files (2013-11-14 22:56:03 -0500) are available in the git repository at: git://git.yoctoproject.org/linux-yocto-contrib nitin/meta http://git.yoctoproject.org/cgit.cgi/linux-yocto-contrib/log/?h=nitin/meta Nitin A Kamble (16): minnow.cfg: Enable TEA575X sound driver firmware.scc/cfg : Feature for firmware loading remove old MEDIA config fragments media.scc : A feature for Media infrastructure media/common : A feature for common media support media/usb: A feature for USB media devices. media/i2c: A feature for i2c media devices media/pci-capture : A feature for PCI media capture devices media/platform : A feature for platform media devices media/radio : A feature for AM/FM radio devices media/rc : A feature for remote control media devices media/tuners: A feature for tuner media devices media/usb_tv: A feature for usb tv media adapters media/dvb-frontends : A feature for Digital Video Broadcast Devices minnow.scc: enable media firmware features common-pc-64.scc: update as per changes in the media config fragments .../kernel-cache/bsp/common-pc-64/common-pc-64.scc | 3 +- meta/cfg/kernel-cache/bsp/minnow/minnow.cfg| 1 + meta/cfg/kernel-cache/bsp/minnow/minnow.scc| 9 ++ .../kernel-cache/features/firmware/firmware.cfg| 8 ++ .../kernel-cache/features/firmware/firmware.scc| 4 + meta/cfg/kernel-cache/features/media/common.cfg| 15 +++ meta/cfg/kernel-cache/features/media/common.scc| 6 ++ .../kernel-cache/features/media/dvb_frontends.cfg | 116 + .../kernel-cache/features/media/dvb_frontends.scc | 6 ++ meta/cfg/kernel-cache/features/media/i2c.cfg | 74 + meta/cfg/kernel-cache/features/media/i2c.scc | 7 ++ .../kernel-cache/features/media/media-camera.cfg | 4 - .../kernel-cache/features/media/media-camera.scc | 4 - meta/cfg/kernel-cache/features/media/media.cfg | 54 ++ meta/cfg/kernel-cache/features/media/media.scc | 4 + .../kernel-cache/features/media/pci-capture.cfg| 80 ++ .../kernel-cache/features/media/pci-capture.scc| 8 ++ meta/cfg/kernel-cache/features/media/platform.cfg | 15 +++ meta/cfg/kernel-cache/features/media/platform.scc | 6 ++ meta/cfg/kernel-cache/features/media/radio.cfg | 24 + meta/cfg/kernel-cache/features/media/radio.scc | 6 ++ meta/cfg/kernel-cache/features/media/rc.cfg| 18 meta/cfg/kernel-cache/features/media/rc.scc| 6 ++ meta/cfg/kernel-cache/features/media/tuners.cfg| 30 ++ meta/cfg/kernel-cache/features/media/tuners.scc| 7 ++ meta/cfg/kernel-cache/features/media/usb.cfg | 76 ++ meta/cfg/kernel-cache/features/media/usb.scc | 7 ++ meta/cfg/kernel-cache/features/media/usb_tv.cfg| 82 +++ meta/cfg/kernel-cache/features/media/usb_tv.scc| 8 ++ meta/cfg/kernel-cache/features/media/v4l2.cfg | 21 meta/cfg/kernel-cache/features/media/v4l2.scc | 6 -- .../cfg/kernel-cache/features/usb/usb-uvcvideo.cfg | 3 - .../cfg/kernel-cache/features/usb/usb-uvcvideo.scc | 7 -- 33 files changed, 678 insertions(+), 47 deletions(-) create mode 100644 meta/cfg/kernel-cache/features/firmware/firmware.cfg create mode 100644 meta/cfg/kernel-cache/features/firmware/firmware.scc create mode 100644 meta/cfg/kernel-cache/features/media/common.cfg create mode 100644 meta/cfg/kernel-cache/features/media/common.scc create mode 100644 meta/cfg/kernel-cache/features/media/dvb_frontends.cfg create mode 100644 meta/cfg/kernel-cache/features/media/dvb_frontends.scc create mode 100644 meta/cfg/kernel-cache/features/media/i2c.cfg create mode 100644 meta/cfg/kernel-cache/features/media/i2c.scc delete mode 100644 meta/cfg/kernel-cache/features/media/media-camera.cfg delete mode 100644
Re: [linux-yocto] [PATCH 01/16] minnow.cfg: Enable TEA575X sound driver
On Fri, 2013-11-22 at 11:35 -0800, nitin.a.kam...@intel.com wrote: From: Nitin A Kamble nitin.a.kam...@intel.com The TEA575X sound driver configuration is relocated from the kernel recipe's media.cfg to here. This isn't required for the minnowboard, it uses an HDA. This should be part of a more generic sound fragment that can be included by BSPs like genericx86*. -- Darren Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com --- meta/cfg/kernel-cache/bsp/minnow/minnow.cfg | 1 + 1 file changed, 1 insertion(+) diff --git a/meta/cfg/kernel-cache/bsp/minnow/minnow.cfg b/meta/cfg/kernel-cache/bsp/minnow/minnow.cfg index 2be4ea4..b08f411 100644 --- a/meta/cfg/kernel-cache/bsp/minnow/minnow.cfg +++ b/meta/cfg/kernel-cache/bsp/minnow/minnow.cfg @@ -8,6 +8,7 @@ CONFIG_MTRR=y # Basic hardware support for the box - network, USB, PCI, sound CONFIG_PCI=y CONFIG_PCIEPORTBUS=y +CONFIG_SND_TEA575X=m # Ensure we can boot over MMC CONFIG_MMC=y -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel ___ linux-yocto mailing list linux-yo...@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 02/16] firmware.scc/cfg : Feature for firmware loading
On Fri, 2013-11-22 at 11:35 -0800, nitin.a.kam...@intel.com wrote: From: Nitin A Kamble nitin.a.kam...@intel.com This enables the kernel configuration for firmware loading. This is bare-minimum in size (3 CONFIGs) in my opinion to be considered for it's own fragment. I'm OK with it - but I wonder, Bruce, would this be better off just included in the base.cfg? It seems a reasonable thing to just include by default on all linux-yocto kernels. -- Darren Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com --- meta/cfg/kernel-cache/features/firmware/firmware.cfg | 8 meta/cfg/kernel-cache/features/firmware/firmware.scc | 4 2 files changed, 12 insertions(+) create mode 100644 meta/cfg/kernel-cache/features/firmware/firmware.cfg create mode 100644 meta/cfg/kernel-cache/features/firmware/firmware.scc diff --git a/meta/cfg/kernel-cache/features/firmware/firmware.cfg b/meta/cfg/kernel-cache/features/firmware/firmware.cfg new file mode 100644 index 000..7331ab3 --- /dev/null +++ b/meta/cfg/kernel-cache/features/firmware/firmware.cfg @@ -0,0 +1,8 @@ +CONFIG_FW_LOADER=m +CONFIG_FIRMWARE_IN_KERNEL=y +CONFIG_EXTRA_FIRMWARE= + +# +# Altera FPGA firmware download module +# +CONFIG_ALTERA_STAPL=m diff --git a/meta/cfg/kernel-cache/features/firmware/firmware.scc b/meta/cfg/kernel-cache/features/firmware/firmware.scc new file mode 100644 index 000..09432a8 --- /dev/null +++ b/meta/cfg/kernel-cache/features/firmware/firmware.scc @@ -0,0 +1,4 @@ +define KFEATURE_DESCRIPTION Firmware loading support +define KFEATURE_COMPATIBILITY all + +kconf non-hardware firmware.cfg -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel ___ linux-yocto mailing list linux-yo...@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 03/16] remove old MEDIA config fragments
On Fri, 2013-11-22 at 11:35 -0800, nitin.a.kam...@intel.com wrote: From: Nitin A Kamble nitin.a.kam...@intel.com These are getting replaced with newer extensive MEDIA config fragments. OK, but this should come last, after the others are in place and used by the BSPs. -- Darren Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com --- .../kernel-cache/features/media/media-camera.cfg| 4 .../kernel-cache/features/media/media-camera.scc| 4 meta/cfg/kernel-cache/features/media/v4l2.cfg | 21 - meta/cfg/kernel-cache/features/media/v4l2.scc | 6 -- meta/cfg/kernel-cache/features/usb/usb-uvcvideo.cfg | 3 --- meta/cfg/kernel-cache/features/usb/usb-uvcvideo.scc | 7 --- 6 files changed, 45 deletions(-) delete mode 100644 meta/cfg/kernel-cache/features/media/media-camera.cfg delete mode 100644 meta/cfg/kernel-cache/features/media/media-camera.scc delete mode 100644 meta/cfg/kernel-cache/features/media/v4l2.cfg delete mode 100644 meta/cfg/kernel-cache/features/media/v4l2.scc delete mode 100644 meta/cfg/kernel-cache/features/usb/usb-uvcvideo.cfg delete mode 100644 meta/cfg/kernel-cache/features/usb/usb-uvcvideo.scc diff --git a/meta/cfg/kernel-cache/features/media/media-camera.cfg b/meta/cfg/kernel-cache/features/media/media-camera.cfg deleted file mode 100644 index 6e173a9..000 --- a/meta/cfg/kernel-cache/features/media/media-camera.cfg +++ /dev/null @@ -1,4 +0,0 @@ -# Enable Multimedia and Camera Device support -CONFIG_MEDIA_SUPPORT=m -CONFIG_MEDIA_CAMERA_SUPPORT=y -CONFIG_MEDIA_SUBDRV_AUTOSELECT=y diff --git a/meta/cfg/kernel-cache/features/media/media-camera.scc b/meta/cfg/kernel-cache/features/media/media-camera.scc deleted file mode 100644 index 15d04e4..000 --- a/meta/cfg/kernel-cache/features/media/media-camera.scc +++ /dev/null @@ -1,4 +0,0 @@ -define KFEATURE_DESCRIPTION Enable camera media device as a module -define KFEATURE_COMPATIBILITY all - -kconf non-hardware media-camera.cfg diff --git a/meta/cfg/kernel-cache/features/media/v4l2.cfg b/meta/cfg/kernel-cache/features/media/v4l2.cfg deleted file mode 100644 index 614886c..000 --- a/meta/cfg/kernel-cache/features/media/v4l2.cfg +++ /dev/null @@ -1,21 +0,0 @@ -# Enable the V4L2 core and API -CONFIG_VIDEO_DEV=m -CONFIG_VIDEO_V4L2=m -VIDEO_V4L2_SUBDEV_API=y - -# Used by drivers that need v4l2-mem2mem.ko -V4L2_MEM2MEM_DEV=m - -# Used by drivers that need Videobuf modules -VIDEOBUF_GEN=m -VIDEOBUF_DMA_SG=m -VIDEOBUF_VMALLOC=m -VIDEOBUF_DMA_CONTIG=m -VIDEOBUF_DVB=m - -# Used by drivers that need Videobuf2 modules -CONFIG_VIDEOBUF2_CORE=m -CONFIG_VIDEOBUF2_MEMOPS=m -CONFIG_VIDEOBUF2_VMALLOC=m -VIDEOBUF2_DMA_CONTIG=m -VIDEOBUF2_DMA_SG=m diff --git a/meta/cfg/kernel-cache/features/media/v4l2.scc b/meta/cfg/kernel-cache/features/media/v4l2.scc deleted file mode 100644 index 09ab7d6..000 --- a/meta/cfg/kernel-cache/features/media/v4l2.scc +++ /dev/null @@ -1,6 +0,0 @@ -define KFEATURE_DESCRIPTION Enable Video for Linux 2 as a module -define KFEATURE_COMPATIBILITY all - -include media-camera.scc - -kconf non-hardware v4l2.cfg diff --git a/meta/cfg/kernel-cache/features/usb/usb-uvcvideo.cfg b/meta/cfg/kernel-cache/features/usb/usb-uvcvideo.cfg deleted file mode 100644 index 366f08b..000 --- a/meta/cfg/kernel-cache/features/usb/usb-uvcvideo.cfg +++ /dev/null @@ -1,3 +0,0 @@ -# Enable USB Video Class camera support -CONFIG_MEDIA_USB_SUPPORT=y -CONFIG_USB_VIDEO_CLASS=m diff --git a/meta/cfg/kernel-cache/features/usb/usb-uvcvideo.scc b/meta/cfg/kernel-cache/features/usb/usb-uvcvideo.scc deleted file mode 100644 index a8cd0f1..000 --- a/meta/cfg/kernel-cache/features/usb/usb-uvcvideo.scc +++ /dev/null @@ -1,7 +0,0 @@ -define KFEATURE_DESCRIPTION Enable USB UVC Video Camera Module -define KFEATURE_COMPATIBILITY board - -include usb-base.scc -include features/media/media-camera.scc - -kconf hardware usb-uvcvideo.cfg -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel ___ linux-yocto mailing list linux-yo...@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 04/16] media.scc : A feature for Media infrastructure
On Fri, 2013-11-22 at 11:35 -0800, nitin.a.kam...@intel.com wrote: From: Nitin A Kamble nitin.a.kam...@intel.com This replaces the previous limited media config fragments. Other hardware media features depends on this feature. Please include the intent of this particular feature here. This adds the infrastructure V4L2, tuner, camera, and radio, to be included by driver-specific features. But, yes, good abstraction. -- Darren Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com --- meta/cfg/kernel-cache/features/media/media.cfg | 54 ++ meta/cfg/kernel-cache/features/media/media.scc | 4 ++ 2 files changed, 58 insertions(+) create mode 100644 meta/cfg/kernel-cache/features/media/media.cfg create mode 100644 meta/cfg/kernel-cache/features/media/media.scc diff --git a/meta/cfg/kernel-cache/features/media/media.cfg b/meta/cfg/kernel-cache/features/media/media.cfg new file mode 100644 index 000..b7b5f5e --- /dev/null +++ b/meta/cfg/kernel-cache/features/media/media.cfg @@ -0,0 +1,54 @@ +# +# Enable support for multimedia devices such as webcams and Video grabber devices +# +CONFIG_MEDIA_SUPPORT=m +CONFIG_MEDIA_CAMERA_SUPPORT=y +CONFIG_MEDIA_ANALOG_TV_SUPPORT=y +CONFIG_MEDIA_DIGITAL_TV_SUPPORT=y +CONFIG_MEDIA_RADIO_SUPPORT=y +CONFIG_MEDIA_CONTROLLER=y + +# +# Enable the V4L2 core and API +# +CONFIG_VIDEO_DEV=m +CONFIG_VIDEO_V4L2=m +CONFIG_VIDEO_V4L2_SUBDEV_API=y + +# +# Used by drivers that need v4l2-mem2mem.ko +# +CONFIG_V4L2_MEM2MEM_DEV=m + +# +# Used by drivers that need Videobuf modules +# +CONFIG_VIDEOBUF_GEN=m +CONFIG_VIDEOBUF_DMA_SG=m +CONFIG_VIDEOBUF_DMA_CONTIG=m +CONFIG_VIDEOBUF_VMALLOC=m +CONFIG_VIDEOBUF_DVB=m + +# +# Used by drivers that need Videobuf2 modules +# +CONFIG_VIDEOBUF2_CORE=m +CONFIG_VIDEOBUF2_MEMOPS=m +CONFIG_VIDEOBUF2_DMA_SG=m +CONFIG_VIDEOBUF2_DMA_CONTIG=m +CONFIG_VIDEOBUF2_VMALLOC=m + +# +# Digital Video Broadcast support +# +CONFIG_DVB_CORE=y +CONFIG_DVB_NET=y +CONFIG_DVB_MAX_ADAPTERS=8 +CONFIG_DVB_DYNAMIC_MINORS=y + +# +# Autoselect ancillary drivers (tuners, sensors, i2c, frontends) +# +CONFIG_MEDIA_SUBDRV_AUTOSELECT=y + +CONFIG_MEDIA_ATTACH=y diff --git a/meta/cfg/kernel-cache/features/media/media.scc b/meta/cfg/kernel-cache/features/media/media.scc new file mode 100644 index 000..838782d --- /dev/null +++ b/meta/cfg/kernel-cache/features/media/media.scc @@ -0,0 +1,4 @@ +define KFEATURE_DESCRIPTION Enable support for multimedia devices such as webcams and Video grabber devices +define KFEATURE_COMPATIBILITY all + +kconf non-hardware media.cfg -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel ___ linux-yocto mailing list linux-yo...@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 02/16] firmware.scc/cfg : Feature for firmware loading
On 13-11-22 03:51 PM, Hart, Darren wrote: On Fri, 2013-11-22 at 11:35 -0800, nitin.a.kam...@intel.com wrote: From: Nitin A Kamble nitin.a.kam...@intel.com This enables the kernel configuration for firmware loading. This is bare-minimum in size (3 CONFIGs) in my opinion to be considered for it's own fragment. I'm OK with it - but I wonder, Bruce, would this be better off just included in the base.cfg? It seems a reasonable thing to just include by default on all linux-yocto kernels. It is fairly common, outside of the CONFIG_ALTERA_STAPL=m, which is hiding at the bottom. Rather than the base (which is harder to turn off), I'd say the standard.scc would be better, since tiny and preempt-rt can more easily not have the fragment enabled. Bruce -- Darren Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com --- meta/cfg/kernel-cache/features/firmware/firmware.cfg | 8 meta/cfg/kernel-cache/features/firmware/firmware.scc | 4 2 files changed, 12 insertions(+) create mode 100644 meta/cfg/kernel-cache/features/firmware/firmware.cfg create mode 100644 meta/cfg/kernel-cache/features/firmware/firmware.scc diff --git a/meta/cfg/kernel-cache/features/firmware/firmware.cfg b/meta/cfg/kernel-cache/features/firmware/firmware.cfg new file mode 100644 index 000..7331ab3 --- /dev/null +++ b/meta/cfg/kernel-cache/features/firmware/firmware.cfg @@ -0,0 +1,8 @@ +CONFIG_FW_LOADER=m +CONFIG_FIRMWARE_IN_KERNEL=y +CONFIG_EXTRA_FIRMWARE= + +# +# Altera FPGA firmware download module +# +CONFIG_ALTERA_STAPL=m diff --git a/meta/cfg/kernel-cache/features/firmware/firmware.scc b/meta/cfg/kernel-cache/features/firmware/firmware.scc new file mode 100644 index 000..09432a8 --- /dev/null +++ b/meta/cfg/kernel-cache/features/firmware/firmware.scc @@ -0,0 +1,4 @@ +define KFEATURE_DESCRIPTION Firmware loading support +define KFEATURE_COMPATIBILITY all + +kconf non-hardware firmware.cfg ___ linux-yocto mailing list linux-yo...@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 06/16] media/usb: A feature for USB media devices.
On Fri, 2013-11-22 at 11:35 -0800, nitin.a.kam...@intel.com wrote: From: Nitin A Kamble nitin.a.kam...@intel.com This enables various USB media devices. Many of the USB webcams drivers are enabled here. OK, you also have usb_tv, so probably want to be a bit more specific about the name here, what exactly does this fragment support? This makes it clear to people looking to use it, but also helps in the future when we add things to know where they should go. Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com --- meta/cfg/kernel-cache/features/media/usb.cfg | 76 meta/cfg/kernel-cache/features/media/usb.scc | 7 +++ 2 files changed, 83 insertions(+) create mode 100644 meta/cfg/kernel-cache/features/media/usb.cfg create mode 100644 meta/cfg/kernel-cache/features/media/usb.scc diff --git a/meta/cfg/kernel-cache/features/media/usb.cfg b/meta/cfg/kernel-cache/features/media/usb.cfg new file mode 100644 index 000..12ac598 --- /dev/null +++ b/meta/cfg/kernel-cache/features/media/usb.cfg @@ -0,0 +1,76 @@ +# Support For USB Media Adapters/devices +CONFIG_MEDIA_USB_SUPPORT=y + +# USB Video Class Webcam Drivers +CONFIG_USB_VIDEO_CLASS=m +CONFIG_USB_VIDEO_CLASS_INPUT_EVDEV=y + +# USB GSPCA Webcam Drivers +CONFIG_USB_GSPCA=m +CONFIG_USB_M5602=m +CONFIG_USB_STV06XX=m +CONFIG_USB_GL860=m +CONFIG_USB_GSPCA_BENQ=m +CONFIG_USB_GSPCA_CONEX=m +CONFIG_USB_GSPCA_CPIA1=m +CONFIG_USB_GSPCA_ETOMS=m +CONFIG_USB_GSPCA_FINEPIX=m +CONFIG_USB_GSPCA_JEILINJ=m +CONFIG_USB_GSPCA_JL2005BCD=m +CONFIG_USB_GSPCA_KINECT=m +CONFIG_USB_GSPCA_KONICA=m +CONFIG_USB_GSPCA_MARS=m +CONFIG_USB_GSPCA_MR97310A=m +CONFIG_USB_GSPCA_NW80X=m +CONFIG_USB_GSPCA_OV519=m +CONFIG_USB_GSPCA_OV534=m +CONFIG_USB_GSPCA_OV534_9=m +CONFIG_USB_GSPCA_PAC207=m +CONFIG_USB_GSPCA_PAC7302=m +CONFIG_USB_GSPCA_PAC7311=m +CONFIG_USB_GSPCA_SE401=m +CONFIG_USB_GSPCA_SN9C2028=m +CONFIG_USB_GSPCA_SN9C20X=m +CONFIG_USB_GSPCA_SONIXB=m +CONFIG_USB_GSPCA_SONIXJ=m +CONFIG_USB_GSPCA_SPCA500=m +CONFIG_USB_GSPCA_SPCA501=m +CONFIG_USB_GSPCA_SPCA505=m +CONFIG_USB_GSPCA_SPCA506=m +CONFIG_USB_GSPCA_SPCA508=m +CONFIG_USB_GSPCA_SPCA561=m +CONFIG_USB_GSPCA_SPCA1528=m +CONFIG_USB_GSPCA_SQ905=m +CONFIG_USB_GSPCA_SQ905C=m +CONFIG_USB_GSPCA_SQ930X=m +CONFIG_USB_GSPCA_STK014=m +CONFIG_USB_GSPCA_STV0680=m +CONFIG_USB_GSPCA_SUNPLUS=m +CONFIG_USB_GSPCA_T613=m +CONFIG_USB_GSPCA_TOPRO=m +CONFIG_USB_GSPCA_TV8532=m +CONFIG_USB_GSPCA_VC032X=m +CONFIG_USB_GSPCA_VICAM=m +CONFIG_USB_GSPCA_XIRLINK_CIT=m +CONFIG_USB_GSPCA_ZC3XX=m + +# USB Philips Camera Drivers +CONFIG_USB_PWC=m +# CONFIG_USB_PWC_DEBUG is not set Off by default, no need to disable explicitly. +CONFIG_USB_PWC_INPUT_EVDEV=y Defaults to yes, also not really needed - but I'm not terribly picky about this. It's selectable, so I could go either way. + +# Vision's CPiA2 (Colour Processor Interface ASIC) Camera Drivers +CONFIG_VIDEO_CPIA2=m + +# CONFIG_USB_ZR364XX is not set Why? + +# USB Syntek DC1125 Camera Support +CONFIG_USB_STKWEBCAM=m + +# USB Sensoray 2255 video capture Device +CONFIG_USB_S2255=m + +# USB SN9C1xx PC Camera Controller Support +CONFIG_USB_SN9C102=m + +# CONFIG_USB_G_WEBCAM is not set I can see not enabling this here, better off in a usb-gadgets fragment... but why disable it explicitly? diff --git a/meta/cfg/kernel-cache/features/media/usb.scc b/meta/cfg/kernel-cache/features/media/usb.scc new file mode 100644 index 000..5602311 --- /dev/null +++ b/meta/cfg/kernel-cache/features/media/usb.scc @@ -0,0 +1,7 @@ +define KFEATURE_DESCRIPTION Enable Configuration For USB Media Adapters +define KFEATURE_COMPATIBILITY all + +include media.scc Good, grabbed the dependencies from there. +include ../usb/usb-base.cfg I'd list this first though just to keep the dependency chain a bit more obvious. + +kconf hardware usb.cfg -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel ___ linux-yocto mailing list linux-yo...@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 00/16] linux-yocto-3.10: config fragments for minnow BSP
-Original Message- From: Hart, Darren Sent: Friday, November 22, 2013 12:48 PM To: Kamble, Nitin A Cc: linux-yo...@yoctoproject.org; bruce.ashfi...@windriver.com Subject: Re: [PATCH 00/16] linux-yocto-3.10: config fragments for minnow BSP On Fri, 2013-11-22 at 11:36 -0800, nitin.a.kam...@intel.com wrote: From: Nitin A Kamble nitin.a.kam...@intel.com This patch series imports the 500 line media.cfg from the kernel recipe in to the linux-yocto-3.10 meta branch, by splitting it into many fragments. It replaces some of the existing webcam media fragments, and hence BSPs configs using the old media fragments is changed accordingly. This has been tested the following way. * It gives the same minnow kernel config as with the big media.cfg on SRC_URI * This changes the kernel config for sugarbay and genericx86-64 BSPs, and the sugarbay BSP is validated to work as expected with this change. Fantastic, thank you Nitin. Did you also verify that no new issues are reported by the config validation task and logged in the .meta/standard/$KMACHINE/* log files? missing, etc? I did verify that there are no errors in those log file. Nitin -- Darren Thanks, Nitin The following changes since commit 4a04774a6562ab37a769404920e070b70acf3c4c: minnow: Remove branch statements from minnow scc files (2013-11-14 22:56:03 -0500) are available in the git repository at: git://git.yoctoproject.org/linux-yocto-contrib nitin/meta http://git.yoctoproject.org/cgit.cgi/linux-yocto-contrib/log/?h=nitin/ meta Nitin A Kamble (16): minnow.cfg: Enable TEA575X sound driver firmware.scc/cfg : Feature for firmware loading remove old MEDIA config fragments media.scc : A feature for Media infrastructure media/common : A feature for common media support media/usb: A feature for USB media devices. media/i2c: A feature for i2c media devices media/pci-capture : A feature for PCI media capture devices media/platform : A feature for platform media devices media/radio : A feature for AM/FM radio devices media/rc : A feature for remote control media devices media/tuners: A feature for tuner media devices media/usb_tv: A feature for usb tv media adapters media/dvb-frontends : A feature for Digital Video Broadcast Devices minnow.scc: enable media firmware features common-pc-64.scc: update as per changes in the media config fragments .../kernel-cache/bsp/common-pc-64/common-pc-64.scc | 3 +- meta/cfg/kernel-cache/bsp/minnow/minnow.cfg| 1 + meta/cfg/kernel-cache/bsp/minnow/minnow.scc| 9 ++ .../kernel-cache/features/firmware/firmware.cfg| 8 ++ .../kernel-cache/features/firmware/firmware.scc| 4 + meta/cfg/kernel-cache/features/media/common.cfg| 15 +++ meta/cfg/kernel-cache/features/media/common.scc| 6 ++ .../kernel-cache/features/media/dvb_frontends.cfg | 116 + .../kernel-cache/features/media/dvb_frontends.scc | 6 ++ meta/cfg/kernel-cache/features/media/i2c.cfg | 74 + meta/cfg/kernel-cache/features/media/i2c.scc | 7 ++ .../kernel-cache/features/media/media-camera.cfg | 4 - .../kernel-cache/features/media/media-camera.scc | 4 - meta/cfg/kernel-cache/features/media/media.cfg | 54 ++ meta/cfg/kernel-cache/features/media/media.scc | 4 + .../kernel-cache/features/media/pci-capture.cfg| 80 ++ .../kernel-cache/features/media/pci-capture.scc| 8 ++ meta/cfg/kernel-cache/features/media/platform.cfg | 15 +++ meta/cfg/kernel-cache/features/media/platform.scc | 6 ++ meta/cfg/kernel-cache/features/media/radio.cfg | 24 + meta/cfg/kernel-cache/features/media/radio.scc | 6 ++ meta/cfg/kernel-cache/features/media/rc.cfg| 18 meta/cfg/kernel-cache/features/media/rc.scc| 6 ++ meta/cfg/kernel-cache/features/media/tuners.cfg| 30 ++ meta/cfg/kernel-cache/features/media/tuners.scc| 7 ++ meta/cfg/kernel-cache/features/media/usb.cfg | 76 ++ meta/cfg/kernel-cache/features/media/usb.scc | 7 ++ meta/cfg/kernel-cache/features/media/usb_tv.cfg| 82 +++ meta/cfg/kernel-cache/features/media/usb_tv.scc| 8 ++ meta/cfg/kernel-cache/features/media/v4l2.cfg | 21 meta/cfg/kernel-cache/features/media/v4l2.scc | 6 -- .../cfg/kernel-cache/features/usb/usb-uvcvideo.cfg | 3 - .../cfg/kernel-cache/features/usb/usb-uvcvideo.scc | 7 -- 33 files changed, 678 insertions(+), 47 deletions(-) create mode 100644 meta/cfg/kernel-cache/features/firmware/firmware.cfg create mode 100644 meta/cfg/kernel-cache/features/firmware/firmware.scc create mode 100644 meta/cfg/kernel-cache/features/media/common.cfg create mode 100644
Re: [linux-yocto] [PATCH 01/16] minnow.cfg: Enable TEA575X sound driver
-Original Message- From: Darren Hart [mailto:dvh...@linux.intel.com] Sent: Friday, November 22, 2013 12:50 PM To: Kamble, Nitin A Cc: linux-yo...@yoctoproject.org; bruce.ashfi...@windriver.com Subject: Re: [PATCH 01/16] minnow.cfg: Enable TEA575X sound driver On Fri, 2013-11-22 at 11:35 -0800, nitin.a.kam...@intel.com wrote: From: Nitin A Kamble nitin.a.kam...@intel.com The TEA575X sound driver configuration is relocated from the kernel recipe's media.cfg to here. This isn't required for the minnowboard, it uses an HDA. This should be part of a more generic sound fragment that can be included by BSPs like genericx86*. The only reason for adding this was, because minnow board used it in it's media.cfg. If it is not needed for minnow, then why to keep it? Nitin -- Darren Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com --- meta/cfg/kernel-cache/bsp/minnow/minnow.cfg | 1 + 1 file changed, 1 insertion(+) diff --git a/meta/cfg/kernel-cache/bsp/minnow/minnow.cfg b/meta/cfg/kernel-cache/bsp/minnow/minnow.cfg index 2be4ea4..b08f411 100644 --- a/meta/cfg/kernel-cache/bsp/minnow/minnow.cfg +++ b/meta/cfg/kernel-cache/bsp/minnow/minnow.cfg @@ -8,6 +8,7 @@ CONFIG_MTRR=y # Basic hardware support for the box - network, USB, PCI, sound CONFIG_PCI=y CONFIG_PCIEPORTBUS=y +CONFIG_SND_TEA575X=m # Ensure we can boot over MMC CONFIG_MMC=y -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel ___ linux-yocto mailing list linux-yo...@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 07/16] media/i2c: A feature for i2c media devices
On Fri, 2013-11-22 at 11:35 -0800, nitin.a.kam...@intel.com wrote: From: Nitin A Kamble nitin.a.kam...@intel.com This enables kernel configuration for bunch of i2c media devices. Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com --- meta/cfg/kernel-cache/features/media/i2c.cfg | 74 meta/cfg/kernel-cache/features/media/i2c.scc | 7 +++ At the very least, lets use media-i2c, media-usb, etc. naming to avoid confusion. 2 files changed, 81 insertions(+) create mode 100644 meta/cfg/kernel-cache/features/media/i2c.cfg create mode 100644 meta/cfg/kernel-cache/features/media/i2c.scc diff --git a/meta/cfg/kernel-cache/features/media/i2c.cfg b/meta/cfg/kernel-cache/features/media/i2c.cfg new file mode 100644 index 000..a59631f --- /dev/null +++ b/meta/cfg/kernel-cache/features/media/i2c.cfg @@ -0,0 +1,74 @@ +# +# Media I2C Support +# + +# +# Encoders, Decoders, Sensors And Other Helper Chips +# +CONFIG_VIDEO_IR_I2C=y +CONFIG_VIDEO_TVAUDIO=m +CONFIG_VIDEO_TDA7432=m +CONFIG_VIDEO_TDA9840=m +CONFIG_VIDEO_TEA6415C=m +CONFIG_VIDEO_TEA6420=m +CONFIG_VIDEO_MSP3400=m +CONFIG_VIDEO_CS5345=m +CONFIG_VIDEO_CS53L32A=m +CONFIG_VIDEO_WM8775=m +CONFIG_VIDEO_WM8739=m +CONFIG_VIDEO_VP27SMPX=m + +# +# RDS decoders +# +CONFIG_VIDEO_SAA6588=m + +# +# Video decoders +# +CONFIG_VIDEO_BT819=m +CONFIG_VIDEO_BT856=m +CONFIG_VIDEO_BT866=m +CONFIG_VIDEO_KS0127=m +CONFIG_VIDEO_SAA7110=m +CONFIG_VIDEO_SAA711X=m +CONFIG_VIDEO_TVP5150=m +CONFIG_VIDEO_VPX3220=m + +# +# Video and audio decoders +# +CONFIG_VIDEO_SAA717X=m +CONFIG_VIDEO_CX25840=m + +# +# MPEG video encoders +# +CONFIG_VIDEO_CX2341X=m + +# +# Video encoders +# +CONFIG_VIDEO_SAA7127=m +CONFIG_VIDEO_ADV7170=m +CONFIG_VIDEO_ADV7175=m + +# +# Camera sensor devices +# +CONFIG_VIDEO_MT9V011=m + +# +# Flash devices +# Nothing here? Can drop the heading then. +# +# Video improvement chips +# +CONFIG_VIDEO_UPD64031A=m +CONFIG_VIDEO_UPD64083=m + +# +# Miscelaneous helper chips +# +CONFIG_VIDEO_M52790=m Looks good in general, I didn't check this one for options without prompts that are auto-selected, that audit should always be done when creating fragments. diff --git a/meta/cfg/kernel-cache/features/media/i2c.scc b/meta/cfg/kernel-cache/features/media/i2c.scc new file mode 100644 index 000..195266b --- /dev/null +++ b/meta/cfg/kernel-cache/features/media/i2c.scc @@ -0,0 +1,7 @@ +define KFEATURE_DESCRIPTION Enable Configuration For I2C Media devices +define KFEATURE_COMPATIBILITY all + +include media.scc +include ../i2c/i2c.scc + +kconf hardware i2c.cfg -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel ___ linux-yocto mailing list linux-yo...@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 08/16] media/pci-capture : A feature for PCI media capture devices
On Fri, 2013-11-22 at 11:35 -0800, nitin.a.kam...@intel.com wrote: From: Nitin A Kamble nitin.a.kam...@intel.com I've avoided too much feedback on the commit message, but these are nearly as important as the content itself. So I'll spend some time on just this one and leave it to you to extend to the others. This enables kernel configuration for bunch of PCI media capture ^ a :-) and elsewhere devices. Convention would be to speak in the imperative, so drop the This and replace enables with Enable. Enable kernel configuration for PCI media capture devices. Or perhaps more appropriately: Create a feature fragment for PCI media capture devices. If you made any non-obvious decisions in preparing this fragment, please note them here as well. Did you drop any specific options? Did you included something that appears out of place to avoid extra complexity elsewhere, etc. Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com --- .../kernel-cache/features/media/pci-capture.cfg| 80 ++ .../kernel-cache/features/media/pci-capture.scc| 8 +++ 2 files changed, 88 insertions(+) create mode 100644 meta/cfg/kernel-cache/features/media/pci-capture.cfg create mode 100644 meta/cfg/kernel-cache/features/media/pci-capture.scc diff --git a/meta/cfg/kernel-cache/features/media/pci-capture.cfg b/meta/cfg/kernel-cache/features/media/pci-capture.cfg new file mode 100644 index 000..232de32 --- /dev/null +++ b/meta/cfg/kernel-cache/features/media/pci-capture.cfg @@ -0,0 +1,80 @@ +# +# Media capture support for PCI devices +# +CONFIG_MEDIA_PCI_SUPPORT=y + +# +# Media capture/analog TV support +# +CONFIG_VIDEO_IVTV=m +CONFIG_VIDEO_IVTV_ALSA=m +CONFIG_VIDEO_FB_IVTV=m + +CONFIG_VIDEO_ZORAN=m +CONFIG_VIDEO_ZORAN_DC30=m +CONFIG_VIDEO_ZORAN_ZR36060=m +# CONFIG_VIDEO_ZORAN_BUZ is not set Why? +CONFIG_VIDEO_ZORAN_DC10=m +CONFIG_VIDEO_ZORAN_LML33=m +CONFIG_VIDEO_ZORAN_LML33R10=m +CONFIG_VIDEO_ZORAN_AVS6EYES=m + +CONFIG_VIDEO_HEXIUM_GEMINI=m +CONFIG_VIDEO_HEXIUM_ORION=m +CONFIG_VIDEO_MXB=m + +# +# Media capture/analog/hybrid TV support +# +CONFIG_VIDEO_CX18=m +CONFIG_VIDEO_CX18_ALSA=m + +CONFIG_VIDEO_CX23885=m +CONFIG_MEDIA_ALTERA_CI=m + +CONFIG_VIDEO_CX25821=m +CONFIG_VIDEO_CX25821_ALSA=m + +CONFIG_VIDEO_CX88=m +CONFIG_VIDEO_CX88_ALSA=m +CONFIG_VIDEO_CX88_BLACKBIRD=m +CONFIG_VIDEO_CX88_DVB=m +CONFIG_VIDEO_CX88_VP3054=m +CONFIG_VIDEO_CX88_MPEG=m + +CONFIG_VIDEO_BT848=m +CONFIG_DVB_BT8XX=m + +CONFIG_VIDEO_SAA7134=m +CONFIG_VIDEO_SAA7134_ALSA=m +CONFIG_VIDEO_SAA7134_RC=y +CONFIG_VIDEO_SAA7134_DVB=m +CONFIG_VIDEO_SAA7164=m + +# +# Media digital TV PCI Adapters +# +CONFIG_DVB_AV7110=m +CONFIG_DVB_AV7110_OSD=y +CONFIG_DVB_BUDGET_CORE=m +CONFIG_DVB_BUDGET=m +CONFIG_DVB_BUDGET_CI=m +CONFIG_DVB_BUDGET_AV=m +CONFIG_DVB_BUDGET_PATCH=m + +CONFIG_DVB_B2C2_FLEXCOP_PCI=m +# CONFIG_DVB_B2C2_FLEXCOP_PCI_DEBUG is not set Defaults to off I presume? + +CONFIG_DVB_PLUTO2=m + +CONFIG_DVB_DM1105=m + +CONFIG_DVB_PT1=m + +CONFIG_MANTIS_CORE=m +CONFIG_DVB_MANTIS=m +CONFIG_DVB_HOPPER=m + +CONFIG_DVB_NGENE=m + +CONFIG_DVB_DDBRIDGE=m diff --git a/meta/cfg/kernel-cache/features/media/pci-capture.scc b/meta/cfg/kernel-cache/features/media/pci-capture.scc new file mode 100644 index 000..e24e6c8 --- /dev/null +++ b/meta/cfg/kernel-cache/features/media/pci-capture.scc @@ -0,0 +1,8 @@ +define KFEATURE_DESCRIPTION Enable Configuration For Media PCI Capture Devices +define KFEATURE_COMPATIBILITY all + +include media.scc +include ../pci/pci.scc +include common.scc order again, pci first. + +kconf hardware pci-capture.cfg -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel ___ linux-yocto mailing list linux-yo...@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 03/16] remove old MEDIA config fragments
-Original Message- From: Darren Hart [mailto:dvh...@linux.intel.com] Sent: Friday, November 22, 2013 12:53 PM To: Kamble, Nitin A Cc: linux-yo...@yoctoproject.org; bruce.ashfi...@windriver.com Subject: Re: [PATCH 03/16] remove old MEDIA config fragments On Fri, 2013-11-22 at 11:35 -0800, nitin.a.kam...@intel.com wrote: From: Nitin A Kamble nitin.a.kam...@intel.com These are getting replaced with newer extensive MEDIA config fragments. OK, but this should come last, after the others are in place and used by the BSPs. The commit can be shifted easily. As you can guess, I was not concerned about for couple of reasons. The pull request bunches all the concerned commits together. And BSPs would not get affected unless one intends to break, by setting random commit IDs without testing. Anyway it is a quick fix so I won't argue. Nitin -- Darren Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com --- .../kernel-cache/features/media/media-camera.cfg| 4 .../kernel-cache/features/media/media-camera.scc| 4 meta/cfg/kernel-cache/features/media/v4l2.cfg | 21 - meta/cfg/kernel-cache/features/media/v4l2.scc | 6 -- meta/cfg/kernel-cache/features/usb/usb-uvcvideo.cfg | 3 --- meta/cfg/kernel-cache/features/usb/usb-uvcvideo.scc | 7 --- 6 files changed, 45 deletions(-) delete mode 100644 meta/cfg/kernel-cache/features/media/media-camera.cfg delete mode 100644 meta/cfg/kernel-cache/features/media/media-camera.scc delete mode 100644 meta/cfg/kernel-cache/features/media/v4l2.cfg delete mode 100644 meta/cfg/kernel-cache/features/media/v4l2.scc delete mode 100644 meta/cfg/kernel-cache/features/usb/usb-uvcvideo.cfg delete mode 100644 meta/cfg/kernel-cache/features/usb/usb-uvcvideo.scc diff --git a/meta/cfg/kernel-cache/features/media/media-camera.cfg b/meta/cfg/kernel-cache/features/media/media-camera.cfg deleted file mode 100644 index 6e173a9..000 --- a/meta/cfg/kernel-cache/features/media/media-camera.cfg +++ /dev/null @@ -1,4 +0,0 @@ -# Enable Multimedia and Camera Device support - CONFIG_MEDIA_SUPPORT=m -CONFIG_MEDIA_CAMERA_SUPPORT=y - CONFIG_MEDIA_SUBDRV_AUTOSELECT=y diff --git a/meta/cfg/kernel-cache/features/media/media-camera.scc b/meta/cfg/kernel-cache/features/media/media-camera.scc deleted file mode 100644 index 15d04e4..000 --- a/meta/cfg/kernel-cache/features/media/media-camera.scc +++ /dev/null @@ -1,4 +0,0 @@ -define KFEATURE_DESCRIPTION Enable camera media device as a module -define KFEATURE_COMPATIBILITY all - -kconf non-hardware media-camera.cfg diff --git a/meta/cfg/kernel-cache/features/media/v4l2.cfg b/meta/cfg/kernel-cache/features/media/v4l2.cfg deleted file mode 100644 index 614886c..000 --- a/meta/cfg/kernel-cache/features/media/v4l2.cfg +++ /dev/null @@ -1,21 +0,0 @@ -# Enable the V4L2 core and API -CONFIG_VIDEO_DEV=m -CONFIG_VIDEO_V4L2=m -VIDEO_V4L2_SUBDEV_API=y - -# Used by drivers that need v4l2-mem2mem.ko - V4L2_MEM2MEM_DEV=m - -# Used by drivers that need Videobuf modules -VIDEOBUF_GEN=m -VIDEOBUF_DMA_SG=m -VIDEOBUF_VMALLOC=m - VIDEOBUF_DMA_CONTIG=m -VIDEOBUF_DVB=m - -# Used by drivers that need Videobuf2 modules -CONFIG_VIDEOBUF2_CORE=m -CONFIG_VIDEOBUF2_MEMOPS=m -CONFIG_VIDEOBUF2_VMALLOC=m -VIDEOBUF2_DMA_CONTIG=m -VIDEOBUF2_DMA_SG=m diff --git a/meta/cfg/kernel-cache/features/media/v4l2.scc b/meta/cfg/kernel-cache/features/media/v4l2.scc deleted file mode 100644 index 09ab7d6..000 --- a/meta/cfg/kernel-cache/features/media/v4l2.scc +++ /dev/null @@ -1,6 +0,0 @@ -define KFEATURE_DESCRIPTION Enable Video for Linux 2 as a module -define KFEATURE_COMPATIBILITY all - -include media-camera.scc - -kconf non-hardware v4l2.cfg diff --git a/meta/cfg/kernel-cache/features/usb/usb-uvcvideo.cfg b/meta/cfg/kernel-cache/features/usb/usb-uvcvideo.cfg deleted file mode 100644 index 366f08b..000 --- a/meta/cfg/kernel-cache/features/usb/usb-uvcvideo.cfg +++ /dev/null @@ -1,3 +0,0 @@ -# Enable USB Video Class camera support - CONFIG_MEDIA_USB_SUPPORT=y -CONFIG_USB_VIDEO_CLASS=m diff --git a/meta/cfg/kernel-cache/features/usb/usb-uvcvideo.scc b/meta/cfg/kernel-cache/features/usb/usb-uvcvideo.scc deleted file mode 100644 index a8cd0f1..000 --- a/meta/cfg/kernel-cache/features/usb/usb-uvcvideo.scc +++ /dev/null @@ -1,7 +0,0 @@ -define KFEATURE_DESCRIPTION Enable USB UVC Video Camera Module -define KFEATURE_COMPATIBILITY board - -include usb-base.scc -include features/media/media-camera.scc - -kconf hardware usb-uvcvideo.cfg -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel ___ linux-yocto mailing list linux-yo...@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 09/16] media/platform : A feature for platform media devices
On Fri, 2013-11-22 at 11:35 -0800, nitin.a.kam...@intel.com wrote: From: Nitin A Kamble nitin.a.kam...@intel.com This enables kernel configuration for bunch of media devices which are generally part of some platforms. Many of these devices are webcam devices built into platforms. Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com --- meta/cfg/kernel-cache/features/media/platform.cfg | 15 +++ meta/cfg/kernel-cache/features/media/platform.scc | 6 ++ 2 files changed, 21 insertions(+) create mode 100644 meta/cfg/kernel-cache/features/media/platform.cfg create mode 100644 meta/cfg/kernel-cache/features/media/platform.scc diff --git a/meta/cfg/kernel-cache/features/media/platform.cfg b/meta/cfg/kernel-cache/features/media/platform.cfg new file mode 100644 index 000..b7484e7 --- /dev/null +++ b/meta/cfg/kernel-cache/features/media/platform.cfg @@ -0,0 +1,15 @@ +# +# Media Platform Configuration +# +# CONFIG_V4L_PLATFORM_DRIVERS is not set Hrm, really? + +CONFIG_V4L_MEM2MEM_DRIVERS=y +CONFIG_VIDEO_MEM2MEM_DEINTERLACE=m + +# CONFIG_V4L_TEST_DRIVERS is not set Can remove + + +# +# Media MMC Support +# +# CONFIG_SMS_SDIO_DRV is not set Again, really? Maybe this depends on some SDIO options? Typically we don't explicitly disable things without a very good reason, which should be noted in the fragment. diff --git a/meta/cfg/kernel-cache/features/media/platform.scc b/meta/cfg/kernel-cache/features/media/platform.scc new file mode 100644 index 000..b3a7e01 --- /dev/null +++ b/meta/cfg/kernel-cache/features/media/platform.scc @@ -0,0 +1,6 @@ +define KFEATURE_DESCRIPTION Enable Configuration For Platform Media Devices +define KFEATURE_COMPATIBILITY all + +include media.scc + +kconf hardware platform.cfg mem2mem and sdio dependency maybe? Just guessing. -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel ___ linux-yocto mailing list linux-yo...@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 04/16] media.scc : A feature for Media infrastructure
-Original Message- From: Hart, Darren Sent: Friday, November 22, 2013 12:56 PM To: Kamble, Nitin A Cc: linux-yo...@yoctoproject.org; bruce.ashfi...@windriver.com Subject: Re: [PATCH 04/16] media.scc : A feature for Media infrastructure On Fri, 2013-11-22 at 11:35 -0800, nitin.a.kam...@intel.com wrote: From: Nitin A Kamble nitin.a.kam...@intel.com This replaces the previous limited media config fragments. Other hardware media features depends on this feature. Please include the intent of this particular feature here. This adds the infrastructure V4L2, tuner, camera, and radio, to be included by driver- specific features. Ack. Makes sense. BTW, the real intent is to covert the minnow's media.cfg, ;) Nitin But, yes, good abstraction. -- Darren Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com --- meta/cfg/kernel-cache/features/media/media.cfg | 54 ++ meta/cfg/kernel-cache/features/media/media.scc | 4 ++ 2 files changed, 58 insertions(+) create mode 100644 meta/cfg/kernel-cache/features/media/media.cfg create mode 100644 meta/cfg/kernel-cache/features/media/media.scc diff --git a/meta/cfg/kernel-cache/features/media/media.cfg b/meta/cfg/kernel-cache/features/media/media.cfg new file mode 100644 index 000..b7b5f5e --- /dev/null +++ b/meta/cfg/kernel-cache/features/media/media.cfg @@ -0,0 +1,54 @@ +# +# Enable support for multimedia devices such as webcams and Video +grabber devices # CONFIG_MEDIA_SUPPORT=m +CONFIG_MEDIA_CAMERA_SUPPORT=y CONFIG_MEDIA_ANALOG_TV_SUPPORT=y +CONFIG_MEDIA_DIGITAL_TV_SUPPORT=y +CONFIG_MEDIA_RADIO_SUPPORT=y +CONFIG_MEDIA_CONTROLLER=y + +# +# Enable the V4L2 core and API +# +CONFIG_VIDEO_DEV=m +CONFIG_VIDEO_V4L2=m +CONFIG_VIDEO_V4L2_SUBDEV_API=y + +# +# Used by drivers that need v4l2-mem2mem.ko # +CONFIG_V4L2_MEM2MEM_DEV=m + +# +# Used by drivers that need Videobuf modules # CONFIG_VIDEOBUF_GEN=m +CONFIG_VIDEOBUF_DMA_SG=m CONFIG_VIDEOBUF_DMA_CONTIG=m +CONFIG_VIDEOBUF_VMALLOC=m CONFIG_VIDEOBUF_DVB=m + +# +# Used by drivers that need Videobuf2 modules # +CONFIG_VIDEOBUF2_CORE=m CONFIG_VIDEOBUF2_MEMOPS=m +CONFIG_VIDEOBUF2_DMA_SG=m CONFIG_VIDEOBUF2_DMA_CONTIG=m +CONFIG_VIDEOBUF2_VMALLOC=m + +# +# Digital Video Broadcast support +# +CONFIG_DVB_CORE=y +CONFIG_DVB_NET=y +CONFIG_DVB_MAX_ADAPTERS=8 +CONFIG_DVB_DYNAMIC_MINORS=y + +# +# Autoselect ancillary drivers (tuners, sensors, i2c, frontends) # +CONFIG_MEDIA_SUBDRV_AUTOSELECT=y + +CONFIG_MEDIA_ATTACH=y diff --git a/meta/cfg/kernel-cache/features/media/media.scc b/meta/cfg/kernel-cache/features/media/media.scc new file mode 100644 index 000..838782d --- /dev/null +++ b/meta/cfg/kernel-cache/features/media/media.scc @@ -0,0 +1,4 @@ +define KFEATURE_DESCRIPTION Enable support for multimedia devices such as webcams and Video grabber devices +define KFEATURE_COMPATIBILITY all + +kconf non-hardware media.cfg -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel ___ linux-yocto mailing list linux-yo...@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 11/16] media/rc : A feature for remote control media devices
On Fri, 2013-11-22 at 11:35 -0800, nitin.a.kam...@intel.com wrote: From: Nitin A Kamble nitin.a.kam...@intel.com This enables kernel configuration for bunch of remote control media devices. Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com Reviewed-by: Darren Hart dvh...@linux.intel.com --- meta/cfg/kernel-cache/features/media/rc.cfg | 18 ++ meta/cfg/kernel-cache/features/media/rc.scc | 6 ++ 2 files changed, 24 insertions(+) create mode 100644 meta/cfg/kernel-cache/features/media/rc.cfg create mode 100644 meta/cfg/kernel-cache/features/media/rc.scc diff --git a/meta/cfg/kernel-cache/features/media/rc.cfg b/meta/cfg/kernel-cache/features/media/rc.cfg new file mode 100644 index 000..f8a345e --- /dev/null +++ b/meta/cfg/kernel-cache/features/media/rc.cfg @@ -0,0 +1,18 @@ +# support for remote control +CONFIG_MEDIA_RC_SUPPORT=y +CONFIG_RC_CORE=y +CONFIG_RC_MAP=y +CONFIG_RC_DECODERS=y + +# Support for Infra Red devices +CONFIG_LIRC=m +CONFIG_IR_LIRC_CODEC=m +CONFIG_IR_NEC_DECODER=y +CONFIG_IR_RC5_DECODER=y +CONFIG_IR_RC6_DECODER=y +CONFIG_IR_JVC_DECODER=y +CONFIG_IR_SONY_DECODER=y +CONFIG_IR_RC5_SZ_DECODER=y +CONFIG_IR_SANYO_DECODER=y +CONFIG_IR_MCE_KBD_DECODER=y + diff --git a/meta/cfg/kernel-cache/features/media/rc.scc b/meta/cfg/kernel-cache/features/media/rc.scc new file mode 100644 index 000..7ee158f --- /dev/null +++ b/meta/cfg/kernel-cache/features/media/rc.scc @@ -0,0 +1,6 @@ +define KFEATURE_DESCRIPTION Enable Configuration For Remote Control Media Devices +define KFEATURE_COMPATIBILITY all + +include media.scc + +kconf hardware rc.cfg -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel ___ linux-yocto mailing list linux-yo...@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 12/16] media/tuners: A feature for tuner media devices
On Fri, 2013-11-22 at 11:35 -0800, nitin.a.kam...@intel.com wrote: From: Nitin A Kamble nitin.a.kam...@intel.com This enables kernel configuration for tuner media devices Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com --- meta/cfg/kernel-cache/features/media/tuners.cfg | 30 + meta/cfg/kernel-cache/features/media/tuners.scc | 7 ++ 2 files changed, 37 insertions(+) create mode 100644 meta/cfg/kernel-cache/features/media/tuners.cfg create mode 100644 meta/cfg/kernel-cache/features/media/tuners.scc diff --git a/meta/cfg/kernel-cache/features/media/tuners.cfg b/meta/cfg/kernel-cache/features/media/tuners.cfg new file mode 100644 index 000..90d8f47 --- /dev/null +++ b/meta/cfg/kernel-cache/features/media/tuners.cfg @@ -0,0 +1,30 @@ +CONFIG_VIDEO_TUNER=m +CONFIG_MEDIA_TUNER=y +CONFIG_MEDIA_TUNER_SIMPLE=y +CONFIG_MEDIA_TUNER_TDA8290=y +CONFIG_MEDIA_TUNER_TDA827X=y +CONFIG_MEDIA_TUNER_TDA18271=y +CONFIG_MEDIA_TUNER_TDA9887=y +CONFIG_MEDIA_TUNER_TEA5761=y +CONFIG_MEDIA_TUNER_TEA5767=y Any particular reason to make these all y? In fact, I suspect this triggers a config check warning and these are forced to m as their depencency on VIDEO_TUNER (set to m) won't allow y. Yes, No? Same for many below. +CONFIG_MEDIA_TUNER_MT20XX=y +CONFIG_MEDIA_TUNER_MT2060=m +CONFIG_MEDIA_TUNER_MT2063=m +CONFIG_MEDIA_TUNER_MT2266=m +CONFIG_MEDIA_TUNER_MT2131=m +CONFIG_MEDIA_TUNER_QT1010=m +CONFIG_MEDIA_TUNER_XC2028=y +CONFIG_MEDIA_TUNER_XC5000=y +CONFIG_MEDIA_TUNER_XC4000=y +CONFIG_MEDIA_TUNER_MXL5005S=m +CONFIG_MEDIA_TUNER_MXL5007T=m +CONFIG_MEDIA_TUNER_MC44S803=y +CONFIG_MEDIA_TUNER_MAX2165=m +CONFIG_MEDIA_TUNER_TDA18218=m +CONFIG_MEDIA_TUNER_FC0011=m +CONFIG_MEDIA_TUNER_FC0012=m +CONFIG_MEDIA_TUNER_FC0013=m +CONFIG_MEDIA_TUNER_TDA18212=m +CONFIG_MEDIA_TUNER_E4000=m +CONFIG_MEDIA_TUNER_FC2580=m +CONFIG_MEDIA_TUNER_TUA9001=m diff --git a/meta/cfg/kernel-cache/features/media/tuners.scc b/meta/cfg/kernel-cache/features/media/tuners.scc new file mode 100644 index 000..d6965cb --- /dev/null +++ b/meta/cfg/kernel-cache/features/media/tuners.scc @@ -0,0 +1,7 @@ +define KFEATURE_DESCRIPTION Enable Configuration For Tuner Media Devices +define KFEATURE_COMPATIBILITY all + +include media.scc +include ../i2c/i2c.scc + +kconf hardware tuners.cfg -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel ___ linux-yocto mailing list linux-yo...@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 13/16] media/usb_tv: A feature for usb tv media adapters
On Fri, 2013-11-22 at 11:36 -0800, nitin.a.kam...@intel.com wrote: From: Nitin A Kamble nitin.a.kam...@intel.com This enables kernel configuration fo bunch of USB TV adapters. Please always proofread the commit msg, these are on permanent display in the archives of the internet once committed to git :-) Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com --- meta/cfg/kernel-cache/features/media/usb_tv.cfg | 82 + meta/cfg/kernel-cache/features/media/usb_tv.scc | 8 +++ 2 files changed, 90 insertions(+) create mode 100644 meta/cfg/kernel-cache/features/media/usb_tv.cfg create mode 100644 meta/cfg/kernel-cache/features/media/usb_tv.scc diff --git a/meta/cfg/kernel-cache/features/media/usb_tv.cfg b/meta/cfg/kernel-cache/features/media/usb_tv.cfg new file mode 100644 index 000..4641fa1 --- /dev/null +++ b/meta/cfg/kernel-cache/features/media/usb_tv.cfg @@ -0,0 +1,82 @@ +# +# Analog TV USB devices +# +CONFIG_VIDEO_AU0828=m +CONFIG_VIDEO_PVRUSB2=m +CONFIG_VIDEO_PVRUSB2_SYSFS=y +CONFIG_VIDEO_PVRUSB2_DVB=y +# CONFIG_VIDEO_PVRUSB2_DEBUGIFC is not set Defaults to off I suspect +CONFIG_VIDEO_HDPVR=m +CONFIG_VIDEO_TLG2300=m +CONFIG_VIDEO_USBVISION=m +CONFIG_VIDEO_STK1160=m +# CONFIG_VIDEO_STK1160_AC97 is not set Why? + +# +# Analog/digital TV USB devices +# +CONFIG_VIDEO_CX231XX=m +CONFIG_VIDEO_CX231XX_RC=y +CONFIG_VIDEO_CX231XX_ALSA=m +CONFIG_VIDEO_CX231XX_DVB=m +CONFIG_VIDEO_TM6000=m +CONFIG_VIDEO_TM6000_ALSA=m +CONFIG_VIDEO_TM6000_DVB=m + +# +# Digital TV USB devices +# +CONFIG_DVB_USB=m +# CONFIG_DVB_USB_DEBUG is not set Necessary? +CONFIG_DVB_USB_A800=m +CONFIG_DVB_USB_DIBUSB_MB=m +# CONFIG_DVB_USB_DIBUSB_MB_FAULTY is not set Necessary? +CONFIG_DVB_USB_DIBUSB_MC=m +CONFIG_DVB_USB_DIB0700=m +CONFIG_DVB_USB_UMT_010=m +CONFIG_DVB_USB_CXUSB=m +CONFIG_DVB_USB_M920X=m +CONFIG_DVB_USB_DIGITV=m +CONFIG_DVB_USB_VP7045=m +CONFIG_DVB_USB_VP702X=m +CONFIG_DVB_USB_GP8PSK=m +CONFIG_DVB_USB_NOVA_T_USB2=m +CONFIG_DVB_USB_TTUSB2=m +CONFIG_DVB_USB_DTT200U=m +CONFIG_DVB_USB_OPERA1=m +CONFIG_DVB_USB_AF9005=m +CONFIG_DVB_USB_AF9005_REMOTE=m +CONFIG_DVB_USB_PCTV452E=m +CONFIG_DVB_USB_DW2102=m +CONFIG_DVB_USB_CINERGY_T2=m +CONFIG_DVB_USB_DTV5100=m +CONFIG_DVB_USB_FRIIO=m +CONFIG_DVB_USB_AZ6027=m +CONFIG_DVB_USB_TECHNISAT_USB2=m +CONFIG_DVB_USB_V2=m +CONFIG_DVB_USB_CYPRESS_FIRMWARE=m +CONFIG_DVB_USB_AF9015=m +CONFIG_DVB_USB_AF9035=m +CONFIG_DVB_USB_ANYSEE=m +CONFIG_DVB_USB_AU6610=m +CONFIG_DVB_USB_AZ6007=m +CONFIG_DVB_USB_CE6230=m +CONFIG_DVB_USB_EC168=m +CONFIG_DVB_USB_GL861=m +CONFIG_DVB_USB_IT913X=m +CONFIG_DVB_USB_LME2510=m +CONFIG_DVB_USB_MXL111SF=m +CONFIG_DVB_USB_RTL28XXU=m +CONFIG_DVB_TTUSB_BUDGET=m +CONFIG_DVB_TTUSB_DEC=m +CONFIG_SMS_USB_DRV=m +CONFIG_DVB_B2C2_FLEXCOP_USB=m +# CONFIG_DVB_B2C2_FLEXCOP_USB_DEBUG is not set ditto + +# +# Webcam, TV (analog/digital) USB devices +# +CONFIG_VIDEO_EM28XX=m +CONFIG_VIDEO_EM28XX_ALSA=m +CONFIG_VIDEO_EM28XX_DVB=m +CONFIG_VIDEO_EM28XX_RC=m diff --git a/meta/cfg/kernel-cache/features/media/usb_tv.scc b/meta/cfg/kernel-cache/features/media/usb_tv.scc new file mode 100644 index 000..c7417ac --- /dev/null +++ b/meta/cfg/kernel-cache/features/media/usb_tv.scc @@ -0,0 +1,8 @@ +define KFEATURE_DESCRIPTION Enable Configuration For USB TV adapters +define KFEATURE_COMPATIBILITY all + +include usb.scc +include ../i2c/i2c.scc +include common.scc As with others, we need a better name, media-common.scc ? + +kconf hardware usb_tv.cfg -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel ___ linux-yocto mailing list linux-yo...@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 01/16] minnow.cfg: Enable TEA575X sound driver
On Fri, 2013-11-22 at 21:26 +, Kamble, Nitin A wrote: -Original Message- From: Darren Hart [mailto:dvh...@linux.intel.com] Sent: Friday, November 22, 2013 12:50 PM To: Kamble, Nitin A Cc: linux-yo...@yoctoproject.org; bruce.ashfi...@windriver.com Subject: Re: [PATCH 01/16] minnow.cfg: Enable TEA575X sound driver On Fri, 2013-11-22 at 11:35 -0800, nitin.a.kam...@intel.com wrote: From: Nitin A Kamble nitin.a.kam...@intel.com The TEA575X sound driver configuration is relocated from the kernel recipe's media.cfg to here. This isn't required for the minnowboard, it uses an HDA. This should be part of a more generic sound fragment that can be included by BSPs like genericx86*. The only reason for adding this was, because minnow board used it in it's media.cfg. If it is not needed for minnow, then why to keep it? This fragment was used in Minnow to allow for general expansion. It should only be added explicitly to a BSP fragment if it is always part of that BSP. This device should be part of a general sound fragment that the BSP can choose to include, and other BSPs can make use of. -- Darren Nitin -- Darren Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com --- meta/cfg/kernel-cache/bsp/minnow/minnow.cfg | 1 + 1 file changed, 1 insertion(+) diff --git a/meta/cfg/kernel-cache/bsp/minnow/minnow.cfg b/meta/cfg/kernel-cache/bsp/minnow/minnow.cfg index 2be4ea4..b08f411 100644 --- a/meta/cfg/kernel-cache/bsp/minnow/minnow.cfg +++ b/meta/cfg/kernel-cache/bsp/minnow/minnow.cfg @@ -8,6 +8,7 @@ CONFIG_MTRR=y # Basic hardware support for the box - network, USB, PCI, sound CONFIG_PCI=y CONFIG_PCIEPORTBUS=y +CONFIG_SND_TEA575X=m # Ensure we can boot over MMC CONFIG_MMC=y -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel ___ linux-yocto mailing list linux-yo...@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 03/16] remove old MEDIA config fragments
On Fri, 2013-11-22 at 21:35 +, Kamble, Nitin A wrote: -Original Message- From: Darren Hart [mailto:dvh...@linux.intel.com] Sent: Friday, November 22, 2013 12:53 PM To: Kamble, Nitin A Cc: linux-yo...@yoctoproject.org; bruce.ashfi...@windriver.com Subject: Re: [PATCH 03/16] remove old MEDIA config fragments On Fri, 2013-11-22 at 11:35 -0800, nitin.a.kam...@intel.com wrote: From: Nitin A Kamble nitin.a.kam...@intel.com These are getting replaced with newer extensive MEDIA config fragments. OK, but this should come last, after the others are in place and used by the BSPs. The commit can be shifted easily. As you can guess, I was not concerned about for couple of reasons. The pull request bunches all the concerned commits together. And BSPs would not get affected unless one intends to break, by setting random commit IDs without testing. Anyway it is a quick fix so I won't argue. This is actually an important point. You cannot consider your pull request to be atomic. Patches must apply in order and build at each patch. Without this, we break the ability to bisect the tree to identify problems. Many developers will run their series through build scripts which ensure successful builds after each commit before proposing the series for inclusion. That's admittedly overkill here, but it illustrates the point. -- Darren Nitin -- Darren Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com --- .../kernel-cache/features/media/media-camera.cfg| 4 .../kernel-cache/features/media/media-camera.scc| 4 meta/cfg/kernel-cache/features/media/v4l2.cfg | 21 - meta/cfg/kernel-cache/features/media/v4l2.scc | 6 -- meta/cfg/kernel-cache/features/usb/usb-uvcvideo.cfg | 3 --- meta/cfg/kernel-cache/features/usb/usb-uvcvideo.scc | 7 --- 6 files changed, 45 deletions(-) delete mode 100644 meta/cfg/kernel-cache/features/media/media-camera.cfg delete mode 100644 meta/cfg/kernel-cache/features/media/media-camera.scc delete mode 100644 meta/cfg/kernel-cache/features/media/v4l2.cfg delete mode 100644 meta/cfg/kernel-cache/features/media/v4l2.scc delete mode 100644 meta/cfg/kernel-cache/features/usb/usb-uvcvideo.cfg delete mode 100644 meta/cfg/kernel-cache/features/usb/usb-uvcvideo.scc diff --git a/meta/cfg/kernel-cache/features/media/media-camera.cfg b/meta/cfg/kernel-cache/features/media/media-camera.cfg deleted file mode 100644 index 6e173a9..000 --- a/meta/cfg/kernel-cache/features/media/media-camera.cfg +++ /dev/null @@ -1,4 +0,0 @@ -# Enable Multimedia and Camera Device support - CONFIG_MEDIA_SUPPORT=m -CONFIG_MEDIA_CAMERA_SUPPORT=y - CONFIG_MEDIA_SUBDRV_AUTOSELECT=y diff --git a/meta/cfg/kernel-cache/features/media/media-camera.scc b/meta/cfg/kernel-cache/features/media/media-camera.scc deleted file mode 100644 index 15d04e4..000 --- a/meta/cfg/kernel-cache/features/media/media-camera.scc +++ /dev/null @@ -1,4 +0,0 @@ -define KFEATURE_DESCRIPTION Enable camera media device as a module -define KFEATURE_COMPATIBILITY all - -kconf non-hardware media-camera.cfg diff --git a/meta/cfg/kernel-cache/features/media/v4l2.cfg b/meta/cfg/kernel-cache/features/media/v4l2.cfg deleted file mode 100644 index 614886c..000 --- a/meta/cfg/kernel-cache/features/media/v4l2.cfg +++ /dev/null @@ -1,21 +0,0 @@ -# Enable the V4L2 core and API -CONFIG_VIDEO_DEV=m -CONFIG_VIDEO_V4L2=m -VIDEO_V4L2_SUBDEV_API=y - -# Used by drivers that need v4l2-mem2mem.ko - V4L2_MEM2MEM_DEV=m - -# Used by drivers that need Videobuf modules -VIDEOBUF_GEN=m -VIDEOBUF_DMA_SG=m -VIDEOBUF_VMALLOC=m - VIDEOBUF_DMA_CONTIG=m -VIDEOBUF_DVB=m - -# Used by drivers that need Videobuf2 modules -CONFIG_VIDEOBUF2_CORE=m -CONFIG_VIDEOBUF2_MEMOPS=m -CONFIG_VIDEOBUF2_VMALLOC=m -VIDEOBUF2_DMA_CONTIG=m -VIDEOBUF2_DMA_SG=m diff --git a/meta/cfg/kernel-cache/features/media/v4l2.scc b/meta/cfg/kernel-cache/features/media/v4l2.scc deleted file mode 100644 index 09ab7d6..000 --- a/meta/cfg/kernel-cache/features/media/v4l2.scc +++ /dev/null @@ -1,6 +0,0 @@ -define KFEATURE_DESCRIPTION Enable Video for Linux 2 as a module -define KFEATURE_COMPATIBILITY all - -include media-camera.scc - -kconf non-hardware v4l2.cfg diff --git a/meta/cfg/kernel-cache/features/usb/usb-uvcvideo.cfg b/meta/cfg/kernel-cache/features/usb/usb-uvcvideo.cfg deleted file mode 100644 index 366f08b..000 --- a/meta/cfg/kernel-cache/features/usb/usb-uvcvideo.cfg +++ /dev/null @@ -1,3 +0,0 @@ -# Enable USB Video Class camera support - CONFIG_MEDIA_USB_SUPPORT=y -CONFIG_USB_VIDEO_CLASS=m diff --git a/meta/cfg/kernel-cache/features/usb/usb-uvcvideo.scc
Re: [linux-yocto] [PATCH 14/16] media/dvb-frontends : A feature for Digital Video Broadcast Devices
On Fri, 2013-11-22 at 11:36 -0800, nitin.a.kam...@intel.com wrote: From: Nitin A Kamble nitin.a.kam...@intel.com This enables configuration for bunch of Digital Video Broadcast devices. Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com Reviewed-by: Darren Hart dvh...@linux.intel.com --- .../kernel-cache/features/media/dvb_frontends.cfg | 116 + .../kernel-cache/features/media/dvb_frontends.scc | 6 ++ 2 files changed, 122 insertions(+) create mode 100644 meta/cfg/kernel-cache/features/media/dvb_frontends.cfg create mode 100644 meta/cfg/kernel-cache/features/media/dvb_frontends.scc diff --git a/meta/cfg/kernel-cache/features/media/dvb_frontends.cfg b/meta/cfg/kernel-cache/features/media/dvb_frontends.cfg new file mode 100644 index 000..08d94a1 --- /dev/null +++ b/meta/cfg/kernel-cache/features/media/dvb_frontends.cfg @@ -0,0 +1,116 @@ +# +# Multistandard (satellite) frontends +# +CONFIG_DVB_STB0899=m +CONFIG_DVB_STB6100=m +CONFIG_DVB_STV090x=m +CONFIG_DVB_STV6110x=m + +# +# Multistandard (cable + terrestrial) frontends +# +CONFIG_DVB_DRXK=m +CONFIG_DVB_TDA18271C2DD=m + +# +# DVB-S (satellite) frontends +# +CONFIG_DVB_CX24110=m +CONFIG_DVB_CX24123=m +CONFIG_DVB_MT312=m +CONFIG_DVB_ZL10036=m +CONFIG_DVB_ZL10039=m +CONFIG_DVB_S5H1420=m +CONFIG_DVB_STV0288=m +CONFIG_DVB_STB6000=m +CONFIG_DVB_STV0299=m +CONFIG_DVB_STV6110=m +CONFIG_DVB_STV0900=m +CONFIG_DVB_TDA8083=m +CONFIG_DVB_TDA10086=m +CONFIG_DVB_TDA8261=m +CONFIG_DVB_VES1X93=m +CONFIG_DVB_TUNER_ITD1000=m +CONFIG_DVB_TUNER_CX24113=m +CONFIG_DVB_TDA826X=m +CONFIG_DVB_TUA6100=m +CONFIG_DVB_CX24116=m +CONFIG_DVB_SI21XX=m +CONFIG_DVB_DS3000=m +CONFIG_DVB_MB86A16=m +CONFIG_DVB_TDA10071=m + +# +# DVB-T (terrestrial) frontends +# +CONFIG_DVB_SP8870=m +CONFIG_DVB_SP887X=m +CONFIG_DVB_CX22700=m +CONFIG_DVB_CX22702=m +CONFIG_DVB_DRXD=m +CONFIG_DVB_L64781=m +CONFIG_DVB_TDA1004X=m +CONFIG_DVB_NXT6000=m +CONFIG_DVB_MT352=m +CONFIG_DVB_ZL10353=m +CONFIG_DVB_DIB3000MB=m +CONFIG_DVB_DIB3000MC=m +CONFIG_DVB_DIB7000M=m +CONFIG_DVB_DIB7000P=m +CONFIG_DVB_TDA10048=m +CONFIG_DVB_AF9013=m +CONFIG_DVB_EC100=m +CONFIG_DVB_STV0367=m +CONFIG_DVB_CXD2820R=m +CONFIG_DVB_RTL2830=m +CONFIG_DVB_RTL2832=m + +# +# DVB-C (cable) frontends +# +CONFIG_DVB_VES1820=m +CONFIG_DVB_TDA10021=m +CONFIG_DVB_TDA10023=m +CONFIG_DVB_STV0297=m + +# +# ATSC (North American/Korean Terrestrial/Cable DTV) frontends +# +CONFIG_DVB_NXT200X=m +CONFIG_DVB_OR51211=m +CONFIG_DVB_OR51132=m +CONFIG_DVB_BCM3510=m +CONFIG_DVB_LGDT330X=m +CONFIG_DVB_LGDT3305=m +CONFIG_DVB_LG2160=m +CONFIG_DVB_S5H1409=m +CONFIG_DVB_AU8522=m +CONFIG_DVB_AU8522_DTV=m +CONFIG_DVB_AU8522_V4L=m +CONFIG_DVB_S5H1411=m + +# ISDB-T (terrestrial) frontends +# +CONFIG_DVB_S921=m +CONFIG_DVB_DIB8000=m +CONFIG_DVB_MB86A20S=m + +# +# Digital terrestrial only tuners/PLL +# +CONFIG_DVB_PLL=m +# SEC control devices for DVB-S +# +CONFIG_DVB_LNBP21=m +CONFIG_DVB_LNBP22=m +CONFIG_DVB_ISL6405=m +CONFIG_DVB_ISL6421=m +CONFIG_DVB_ISL6423=m +CONFIG_DVB_A8293=m +CONFIG_DVB_LGS8GXX=m +CONFIG_DVB_ATBM8830=m +CONFIG_DVB_TDA665x=m +CONFIG_DVB_IX2505V=m +CONFIG_DVB_IT913X_FE=m +CONFIG_DVB_M88RS2000=m +CONFIG_DVB_AF9033=m diff --git a/meta/cfg/kernel-cache/features/media/dvb_frontends.scc b/meta/cfg/kernel-cache/features/media/dvb_frontends.scc new file mode 100644 index 000..d3df591 --- /dev/null +++ b/meta/cfg/kernel-cache/features/media/dvb_frontends.scc @@ -0,0 +1,6 @@ +define KFEATURE_DESCRIPTION Enable Configuration For DVB (Digital Video Broadcast) Frontends +define KFEATURE_COMPATIBILITY all + +include media.scc + +kconf hardware dvb_frontends.cfg -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel ___ linux-yocto mailing list linux-yo...@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 16/16] common-pc-64.scc: update as per changes in the media config fragments
On Fri, 2013-11-22 at 11:36 -0800, nitin.a.kam...@intel.com wrote: From: Nitin A Kamble nitin.a.kam...@intel.com Some of the media config fragments are replaced by more extensive media fragments. Changes this BSP config accordingly. Thanks for catching the broader impact. I presume this should impact common-pc.scc as well? In general they should be supporting the same peripheral devices. This will need an update after some renaming of the media sccs discussed above. Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com --- meta/cfg/kernel-cache/bsp/common-pc-64/common-pc-64.scc | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/meta/cfg/kernel-cache/bsp/common-pc-64/common-pc-64.scc b/meta/cfg/kernel-cache/bsp/common-pc-64/common-pc-64.scc index 936df98..7d6eb2a 100644 --- a/meta/cfg/kernel-cache/bsp/common-pc-64/common-pc-64.scc +++ b/meta/cfg/kernel-cache/bsp/common-pc-64/common-pc-64.scc @@ -21,8 +21,7 @@ include features/power/intel.scc include cfg/8250.scc # webcam -include features/usb/usb-uvcvideo.scc -include features/media/v4l2.scc +include features/media/usb.scc # sugarbay graphics include features/i915/i915.scc -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel ___ linux-yocto mailing list linux-yo...@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 48/94] drivers/net: Added debug code.
On Tue, 2013-11-19 at 13:57 -0500, Bruce Ashfield wrote: On 13-11-19 12:17 PM, Paul Butler wrote: On Sat, Nov 9, 2013 at 9:49 AM, Bruce Ashfield bruce.ashfi...@windriver.com mailto:bruce.ashfi...@windriver.com wrote: On 11/7/2013, 8:13 PM, Paul Butler wrote: From: John Jacques john.jacq...@lsi.com mailto:john.jacq...@lsi.com Signed-off-by: John Jacques john.jacq...@lsi.com mailto:john.jacq...@lsi.com --- drivers/net/ethernet/lsi/lsi___acp_mdio.c | 10 ++ 1 file changed, 10 insertions(+) diff --git a/drivers/net/ethernet/lsi/__lsi_acp_mdio.c b/drivers/net/ethernet/lsi/__lsi_acp_mdio.c index 04c224c..18aaba1 100644 --- a/drivers/net/ethernet/lsi/__lsi_acp_mdio.c +++ b/drivers/net/ethernet/lsi/__lsi_acp_mdio.c @@ -98,6 +98,11 @@ acp_mdio_read(unsigned long address, unsigned long offset, *value = (unsigned short)(command 0x); spin_unlock_irqrestore(mdio___lock, flags); +#if 0 + printk(%s - Read 0x%x from 0x%x register 0x%x\n, + __FUNCTION__, *value, address, offset); +#endif + return 0; } EXPORT_SYMBOL(acp_mdio_read); @@ -150,6 +155,11 @@ acp_mdio_write(unsigned long address, unsigned long offset, spin_unlock_irqrestore(mdio___lock, flags); +#if 0 These *really* need to be controlled by a define, or Kconfig that controls a #define. Leaving #if 0 code around the tree is bad form. The #if 0 code was removed in a later patch in this series. Actually, this file was touched again several times in this series. This is also true of other patches with dead code removal issues. In some cases I tried to squash the cleanup together with a change, but I see other comments discouraging that approach. I think we are pretty stable at the tip, but it's pretty ugly how we got there. What is preferred? Squash later cleanup into this patch? (And other similar issues.) We can live with either. It all depends on how much of the development history you want in the tree. Obviously once I've merged a patch series, we don't want to squash exiting commits, but when you are sending a new set of patches, the amount of squashing and history cleanup is in your hands. It's the time to make it as clean (or dirty) as you want :) As long as the series is sane, and reasonably bisectable, I won't quibble too much one way or the other. Erm... well... with the exception that this work should be going upstream FIRST and then backported here. If it wouldn't be acceptable upstream, it isn't here either. -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel ___ linux-yocto mailing list linux-yo...@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 02/16] firmware.scc/cfg : Feature for firmware loading
On Fri, 2013-11-22 at 16:12 -0500, Bruce Ashfield wrote: On 13-11-22 03:51 PM, Hart, Darren wrote: On Fri, 2013-11-22 at 11:35 -0800, nitin.a.kam...@intel.com wrote: From: Nitin A Kamble nitin.a.kam...@intel.com This enables the kernel configuration for firmware loading. This is bare-minimum in size (3 CONFIGs) in my opinion to be considered for it's own fragment. I'm OK with it - but I wonder, Bruce, would this be better off just included in the base.cfg? It seems a reasonable thing to just include by default on all linux-yocto kernels. It is fairly common, outside of the CONFIG_ALTERA_STAPL=m, which is hiding at the bottom. Rather than the base (which is harder to turn off), I'd say the standard.scc would be better, since tiny and preempt-rt can more easily not have the fragment enabled. In which case, we should keep the fragment, and just include it in standard. Otherwise there is no good way to include it from other ktypes directly. -- Darren Bruce -- Darren Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com --- meta/cfg/kernel-cache/features/firmware/firmware.cfg | 8 meta/cfg/kernel-cache/features/firmware/firmware.scc | 4 2 files changed, 12 insertions(+) create mode 100644 meta/cfg/kernel-cache/features/firmware/firmware.cfg create mode 100644 meta/cfg/kernel-cache/features/firmware/firmware.scc diff --git a/meta/cfg/kernel-cache/features/firmware/firmware.cfg b/meta/cfg/kernel-cache/features/firmware/firmware.cfg new file mode 100644 index 000..7331ab3 --- /dev/null +++ b/meta/cfg/kernel-cache/features/firmware/firmware.cfg @@ -0,0 +1,8 @@ +CONFIG_FW_LOADER=m +CONFIG_FIRMWARE_IN_KERNEL=y +CONFIG_EXTRA_FIRMWARE= + +# +# Altera FPGA firmware download module +# +CONFIG_ALTERA_STAPL=m diff --git a/meta/cfg/kernel-cache/features/firmware/firmware.scc b/meta/cfg/kernel-cache/features/firmware/firmware.scc new file mode 100644 index 000..09432a8 --- /dev/null +++ b/meta/cfg/kernel-cache/features/firmware/firmware.scc @@ -0,0 +1,4 @@ +define KFEATURE_DESCRIPTION Firmware loading support +define KFEATURE_COMPATIBILITY all + +kconf non-hardware firmware.cfg -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel ___ linux-yocto mailing list linux-yo...@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 00/16] linux-yocto-3.10: config fragments for minnow BSP
On Fri, 2013-11-22 at 21:23 +, Kamble, Nitin A wrote: -Original Message- From: Hart, Darren Sent: Friday, November 22, 2013 12:48 PM To: Kamble, Nitin A Cc: linux-yo...@yoctoproject.org; bruce.ashfi...@windriver.com Subject: Re: [PATCH 00/16] linux-yocto-3.10: config fragments for minnow BSP On Fri, 2013-11-22 at 11:36 -0800, nitin.a.kam...@intel.com wrote: From: Nitin A Kamble nitin.a.kam...@intel.com This patch series imports the 500 line media.cfg from the kernel recipe in to the linux-yocto-3.10 meta branch, by splitting it into many fragments. It replaces some of the existing webcam media fragments, and hence BSPs configs using the old media fragments is changed accordingly. This has been tested the following way. * It gives the same minnow kernel config as with the big media.cfg on SRC_URI * This changes the kernel config for sugarbay and genericx86-64 BSPs, and the sugarbay BSP is validated to work as expected with this change. Fantastic, thank you Nitin. Did you also verify that no new issues are reported by the config validation task and logged in the .meta/standard/$KMACHINE/* log files? missing, etc? I did verify that there are no errors in those log file. Hrm, I'm surprised, I would have expected many of those tuner y to have been changed to m which would show up in those logs. But, that's good. -- Darren Nitin -- Darren Thanks, Nitin The following changes since commit 4a04774a6562ab37a769404920e070b70acf3c4c: minnow: Remove branch statements from minnow scc files (2013-11-14 22:56:03 -0500) are available in the git repository at: git://git.yoctoproject.org/linux-yocto-contrib nitin/meta http://git.yoctoproject.org/cgit.cgi/linux-yocto-contrib/log/?h=nitin/ meta Nitin A Kamble (16): minnow.cfg: Enable TEA575X sound driver firmware.scc/cfg : Feature for firmware loading remove old MEDIA config fragments media.scc : A feature for Media infrastructure media/common : A feature for common media support media/usb: A feature for USB media devices. media/i2c: A feature for i2c media devices media/pci-capture : A feature for PCI media capture devices media/platform : A feature for platform media devices media/radio : A feature for AM/FM radio devices media/rc : A feature for remote control media devices media/tuners: A feature for tuner media devices media/usb_tv: A feature for usb tv media adapters media/dvb-frontends : A feature for Digital Video Broadcast Devices minnow.scc: enable media firmware features common-pc-64.scc: update as per changes in the media config fragments .../kernel-cache/bsp/common-pc-64/common-pc-64.scc | 3 +- meta/cfg/kernel-cache/bsp/minnow/minnow.cfg| 1 + meta/cfg/kernel-cache/bsp/minnow/minnow.scc| 9 ++ .../kernel-cache/features/firmware/firmware.cfg| 8 ++ .../kernel-cache/features/firmware/firmware.scc| 4 + meta/cfg/kernel-cache/features/media/common.cfg| 15 +++ meta/cfg/kernel-cache/features/media/common.scc| 6 ++ .../kernel-cache/features/media/dvb_frontends.cfg | 116 + .../kernel-cache/features/media/dvb_frontends.scc | 6 ++ meta/cfg/kernel-cache/features/media/i2c.cfg | 74 + meta/cfg/kernel-cache/features/media/i2c.scc | 7 ++ .../kernel-cache/features/media/media-camera.cfg | 4 - .../kernel-cache/features/media/media-camera.scc | 4 - meta/cfg/kernel-cache/features/media/media.cfg | 54 ++ meta/cfg/kernel-cache/features/media/media.scc | 4 + .../kernel-cache/features/media/pci-capture.cfg| 80 ++ .../kernel-cache/features/media/pci-capture.scc| 8 ++ meta/cfg/kernel-cache/features/media/platform.cfg | 15 +++ meta/cfg/kernel-cache/features/media/platform.scc | 6 ++ meta/cfg/kernel-cache/features/media/radio.cfg | 24 + meta/cfg/kernel-cache/features/media/radio.scc | 6 ++ meta/cfg/kernel-cache/features/media/rc.cfg| 18 meta/cfg/kernel-cache/features/media/rc.scc| 6 ++ meta/cfg/kernel-cache/features/media/tuners.cfg| 30 ++ meta/cfg/kernel-cache/features/media/tuners.scc| 7 ++ meta/cfg/kernel-cache/features/media/usb.cfg | 76 ++ meta/cfg/kernel-cache/features/media/usb.scc | 7 ++ meta/cfg/kernel-cache/features/media/usb_tv.cfg| 82 +++ meta/cfg/kernel-cache/features/media/usb_tv.scc| 8 ++ meta/cfg/kernel-cache/features/media/v4l2.cfg | 21 meta/cfg/kernel-cache/features/media/v4l2.scc | 6 -- .../cfg/kernel-cache/features/usb/usb-uvcvideo.cfg | 3 - .../cfg/kernel-cache/features/usb/usb-uvcvideo.scc | 7 -- 33 files
[yocto] RFC Autobuilder Naming
Currently all builders are simply named ab00-ab13 based on when we acquired them. The name doesn't change except for ab01 which has been reused on new hardware. As we increase the number of builders and make the build process more flexible this becomes inconvenient. I'd like to switch to embedding useful information in the name. Going forward as I refresh builders I'd like to name them with their distro and location. For example at OSL: fedora19.osl.yoctoproject.org fedora20.osl.yoctoproject.org opensuse131.osl.yoctoproject.org ubuntu1310.osl.yoctoproject.org etc. And if we added a build clusters in the EasyStreet datacenter in Portland: centos64.pdx.yoctoproject.org debian7.pdx.yoctoproject.org etc. This allows for additional build clusters to be added and makes the distro clear to anyone viewing the logs. The current available build slaves can be found on the relevant cluster's buildbot interface (http://autobuilder.yoctoproject.org/main/buildslaves) so as names change there is an easy place to look them up. Comments? -- Michael Halstead Yocto Project / System Administrator smime.p7s Description: S/MIME Cryptographic Signature ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [linux-yocto] [PATCH 48/94] drivers/net: Added debug code.
On 11/22/2013, 4:57 PM, Darren Hart wrote: On Tue, 2013-11-19 at 13:57 -0500, Bruce Ashfield wrote: On 13-11-19 12:17 PM, Paul Butler wrote: On Sat, Nov 9, 2013 at 9:49 AM, Bruce Ashfield bruce.ashfi...@windriver.com mailto:bruce.ashfi...@windriver.com wrote: On 11/7/2013, 8:13 PM, Paul Butler wrote: From: John Jacques john.jacq...@lsi.com mailto:john.jacq...@lsi.com Signed-off-by: John Jacques john.jacq...@lsi.com mailto:john.jacq...@lsi.com --- drivers/net/ethernet/lsi/lsi___acp_mdio.c | 10 ++ 1 file changed, 10 insertions(+) diff --git a/drivers/net/ethernet/lsi/__lsi_acp_mdio.c b/drivers/net/ethernet/lsi/__lsi_acp_mdio.c index 04c224c..18aaba1 100644 --- a/drivers/net/ethernet/lsi/__lsi_acp_mdio.c +++ b/drivers/net/ethernet/lsi/__lsi_acp_mdio.c @@ -98,6 +98,11 @@ acp_mdio_read(unsigned long address, unsigned long offset, *value = (unsigned short)(command 0x); spin_unlock_irqrestore(mdio___lock, flags); +#if 0 + printk(%s - Read 0x%x from 0x%x register 0x%x\n, + __FUNCTION__, *value, address, offset); +#endif + return 0; } EXPORT_SYMBOL(acp_mdio_read); @@ -150,6 +155,11 @@ acp_mdio_write(unsigned long address, unsigned long offset, spin_unlock_irqrestore(mdio___lock, flags); +#if 0 These *really* need to be controlled by a define, or Kconfig that controls a #define. Leaving #if 0 code around the tree is bad form. The #if 0 code was removed in a later patch in this series. Actually, this file was touched again several times in this series. This is also true of other patches with dead code removal issues. In some cases I tried to squash the cleanup together with a change, but I see other comments discouraging that approach. I think we are pretty stable at the tip, but it's pretty ugly how we got there. What is preferred? Squash later cleanup into this patch? (And other similar issues.) We can live with either. It all depends on how much of the development history you want in the tree. Obviously once I've merged a patch series, we don't want to squash exiting commits, but when you are sending a new set of patches, the amount of squashing and history cleanup is in your hands. It's the time to make it as clean (or dirty) as you want :) As long as the series is sane, and reasonably bisectable, I won't quibble too much one way or the other. Erm... well... with the exception that this work should be going upstream FIRST and then backported here. If it wouldn't be acceptable upstream, it isn't here either. Agreed. I shouldn't be so implicit at times :) Bruce ___ linux-yocto mailing list linux-yo...@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
