From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from omx.cbeyond.com (omx.cbeyond.com [50.20.30.10]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by yocto-www.yoctoproject.org (Postfix) with ESMTPS id 0905FE006AD for ; Tue, 12 Feb 2013 15:47:26 -0800 (PST) X-SBRS: 5.3 X-HAT: Sender Group CBEYOND_SYSTEMS, Policy $CBEYOND_RELAY applied. X-Hostname: omx08bay.sys.cbeyond.net X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AlwBACjUGlEyFB4LmWdsb2JhbABEgkkjvhcOAQEBAQEICwsHFCeCIQUtXgEqViYBBBuICgGeV5EVkAKRJGEDqX2CJw X-IronPort-AV: E=Sophos;i="4.84,652,1355115600"; d="scan'208,217";a="7952623" Received: from mts.cbeyond.com (HELO EXHUB101.mmeprod.cbeyond) ([50.20.30.11]) by omx.cbeyond.com with ESMTP; 12 Feb 2013 18:47:25 -0500 Received: from EXMBX202A.mmeprod.cbeyond ([fe80::b0ca:4d9b:ba7c:8227]) by EXHUB101.mmeprod.cbeyond ([::1]) with mapi id 14.02.0298.004; Tue, 12 Feb 2013 18:47:21 -0500 From: David Mulder To: "yocto@yoctoproject.org" Thread-Topic: Building uio-pci-generic into core-image-minimal Thread-Index: Ac4Je0VK0p5tUgoGRH+vZRb53O1pcA== Date: Tue, 12 Feb 2013 23:47:20 +0000 Message-ID: <19F0379280417C4A8FE3BD23AA7298E501346EB2@EXMBX202A.mmeprod.cbeyond> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [69.198.178.141] MIME-Version: 1.0 Subject: Building uio-pci-generic into core-image-minimal X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Feb 2013 23:47:27 -0000 Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_19F0379280417C4A8FE3BD23AA7298E501346EB2EXMBX202Ammepro_" --_000_19F0379280417C4A8FE3BD23AA7298E501346EB2EXMBX202Ammepro_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I need to use the uio-pci-generic kernel module, but I don't know how to ma= ke it available in my image. Yocto 1.3, core-image-minimal, did 'bitbake linux-yocto -c menuconfig' and = added "Generic driver for PCI 2.3". It took a while to bitbake core-image-m= inimal after that change, and I saw uio-pci-generic.o, so I assume it rebui= lt the kernel and built the module, but I don't see any traces of the modul= e in my image ('find / -name *uio*', /sys/class/uio or /sys/bus/pci/drivers= /uio-pci-generic). I added uio and uio-pci-generic to a recipe's RDEPENDS, but it can't find a= provider. I added them to IMAGE_FEATURES in local.conf, but that didn't se= em to do anything. I set 'module_autoload_uio =3D "uio"' in local.conf, whi= ch also seemed to do nothing. Same for setting it in linux-yocto_3.4.bbappe= nd (some patches indicate that it used to be set in that file). I don't kn= ow what else to try. What might I be missing? Where could I look to see if that module has been= built and copied to my image? Thanks! --_000_19F0379280417C4A8FE3BD23AA7298E501346EB2EXMBX202Ammepro_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I need to use the uio-pci-generic kernel module, but= I don’t know how to make it available in my image.

Yocto 1.3, core-image-minimal, did ‘bitbake li= nux-yocto –c menuconfig’ and added “Generic driver for PC= I 2.3”. It took a while to bitbake core-image-minimal after that chan= ge, and I saw uio-pci-generic.o, so I assume it rebuilt the kernel and built the module, but I don’t see any traces of the module in my= image (‘find / -name *uio*’, /sys/class/uio or /sys/bus/pci/dr= ivers/uio-pci-generic).

I added uio and uio-pci-generic to a recipe’s = RDEPENDS, but it can’t find a provider. I added them to IMAGE_FEATURE= S in local.conf, but that didn’t seem to do anything. I set ‘mo= dule_autoload_uio =3D “uio”’ in local.conf, which also se= emed to do nothing. Same for setting it in linux-yocto_3.4.bbappend (some patch= es indicate that it used to be set in that file). I don’t know = what else to try.

What might I be missing? Where could I look to= see if that module has been built and copied to my image?

Thanks!

--_000_19F0379280417C4A8FE3BD23AA7298E501346EB2EXMBX202Ammepro_-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail1.windriver.com (mail1.windriver.com [147.11.146.13]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by yocto-www.yoctoproject.org (Postfix) with ESMTPS id CE446E006C3 for ; Tue, 12 Feb 2013 17:43:46 -0800 (PST) Received: from ALA-HCA.corp.ad.wrs.com (ala-hca.corp.ad.wrs.com [147.11.189.40]) by mail1.windriver.com (8.14.5/8.14.3) with ESMTP id r1D1hhjE008726 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 12 Feb 2013 17:43:43 -0800 (PST) Received: from bruce-ashfields-macbook.local (128.224.21.22) by ALA-HCA.corp.ad.wrs.com (147.11.189.50) with Microsoft SMTP Server id 14.2.318.4; Tue, 12 Feb 2013 17:43:42 -0800 Message-ID: <511AEFCD.10600@windriver.com> Date: Tue, 12 Feb 2013 20:43:41 -0500 From: Bruce Ashfield User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 MIME-Version: 1.0 To: David Mulder References: <19F0379280417C4A8FE3BD23AA7298E501346EB2@EXMBX202A.mmeprod.cbeyond> In-Reply-To: <19F0379280417C4A8FE3BD23AA7298E501346EB2@EXMBX202A.mmeprod.cbeyond> Cc: "yocto@yoctoproject.org" Subject: Re: Building uio-pci-generic into core-image-minimal X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Feb 2013 01:43:46 -0000 Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 8bit On 13-02-12 6:47 PM, David Mulder wrote: > I need to use the uio-pci-generic kernel module, but I don’t know how to > make it available in my image. > > Yocto 1.3, core-image-minimal, did ‘bitbake linux-yocto –c menuconfig’ > and added “Generic driver for PCI 2.3”. It took a while to bitbake > core-image-minimal after that change, and I saw uio-pci-generic.o, so I > assume it rebuilt the kernel and built the module, but I don’t see any > traces of the module in my image (‘find / -name *uio*’, /sys/class/uio > or /sys/bus/pci/drivers/uio-pci-generic). > > I added uio and uio-pci-generic to a recipe’s RDEPENDS, but it can’t > find a provider. I added them to IMAGE_FEATURES in local.conf, but that You need to add the modules to IMAGE_INSTALL via their individual package name, or if you just want all modules, use the virtual package "kernel-modules" You can also get it in the image via MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS. Cheers, Bruce > didn’t seem to do anything. I set ‘module_autoload_uio = “uio”’ in > local.conf, which also seemed to do nothing. Same for setting it in > linux-yocto_3.4.bbappend (some patches indicate that it used to be set > in that file). I don’t know what else to try. > > What might I be missing? Where could I look to see if that module has > been built and copied to my image? > > Thanks! > > > > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from omx.cbeyond.com (omx.cbeyond.com [50.20.30.10]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 56FBEE006CB for ; Tue, 19 Mar 2013 16:36:14 -0700 (PDT) X-SBRS: 5.3 X-HAT: Sender Group CBEYOND_SYSTEMS, Policy $CBEYOND_RELAY applied. X-Hostname: omx03bay.sys.cbeyond.net X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AkQBADT2SFEyFB4LmWdsb2JhbABDhCODJr1GgVsOAQEBAQEICwsHFCiCJAEBAQMBOj8FDQEIFQEMFAk5FBIBBA4FCIgGBgGxf5AJjl0xgmZhA6prgig X-IronPort-AV: E=Sophos;i="4.84,874,1355115600"; d="scan'208";a="15085332" Received: from mts.cbeyond.com (HELO EXHUB101.mmeprod.cbeyond) ([50.20.30.11]) by omx.cbeyond.com with ESMTP; 19 Mar 2013 19:36:07 -0400 Received: from EXMBX202A.mmeprod.cbeyond ([fe80::b0ca:4d9b:ba7c:8227]) by EXHUB101.mmeprod.cbeyond ([::1]) with mapi id 14.02.0298.004; Tue, 19 Mar 2013 19:35:58 -0400 From: David Mulder To: Paul Eggleton Thread-Topic: [yocto] Building uio-pci-generic into core-image-minimal Thread-Index: Ac4k+n3uSd3FvjjwRnOqu+Ecg4mkfA== Date: Tue, 19 Mar 2013 23:35:57 +0000 Message-ID: <19F0379280417C4A8FE3BD23AA7298E5013484CF@EXMBX202A.mmeprod.cbeyond> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [69.198.178.141] MIME-Version: 1.0 Cc: "yocto@yoctoproject.org" Subject: Re: Building uio-pci-generic into core-image-minimal X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Mar 2013 23:36:14 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable > From: Paul Eggleton [mailto:paul.eggleton@linux.intel.com] > Sent: Thursday, February 21, 2013 11:53 AM > I've now simply cherry-picked the two patches that came before this plus = my > patch from master on top of the 1.3 release tag, and tested the result; > patches are attached. Hi, Paul. Just a note that this problem ('menuconfig', 'bitbake core-image-minimal' (= hddimg has correct kernel), 'bitbake core-image-minimal' (hddimage has olde= st-built kernel)) seems to be in 1.4 M4, which I just tried today, even tho= ugh you checked in patches to fix it a month ago. I don't need a fix for it, but I thought you might want to know (since I a= lways want to know when my stuff doesn't work :-) Thanks! Dave From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 4F0B1E014A5 for ; Thu, 21 Mar 2013 03:26:00 -0700 (PDT) Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga102.jf.intel.com with ESMTP; 21 Mar 2013 03:24:25 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.84,884,1355126400"; d="scan'208";a="282665332" Received: from unknown (HELO helios.localnet) ([10.255.13.149]) by orsmga001.jf.intel.com with ESMTP; 21 Mar 2013 03:25:59 -0700 From: Paul Eggleton To: David Mulder Date: Thu, 21 Mar 2013 10:25:56 +0000 Message-ID: <8690667.yHAQgTMMW4@helios> Organization: Intel Corporation User-Agent: KMail/4.10.1 (Linux/3.5.0-26-generic; KDE/4.10.1; i686; ; ) In-Reply-To: <19F0379280417C4A8FE3BD23AA7298E5013484CF@EXMBX202A.mmeprod.cbeyond> References: <19F0379280417C4A8FE3BD23AA7298E5013484CF@EXMBX202A.mmeprod.cbeyond> MIME-Version: 1.0 Cc: yocto@yoctoproject.org Subject: Re: Building uio-pci-generic into core-image-minimal X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Mar 2013 10:26:00 -0000 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" On Tuesday 19 March 2013 23:35:57 David Mulder wrote: > > From: Paul Eggleton [mailto:paul.eggleton@linux.intel.com] > > Sent: Thursday, February 21, 2013 11:53 AM > > I've now simply cherry-picked the two patches that came before this plus > > my > > patch from master on top of the 1.3 release tag, and tested the result; > > patches are attached. > > Hi, Paul. > > Just a note that this problem ('menuconfig', 'bitbake core-image-minimal' > (hddimg has correct kernel), 'bitbake core-image-minimal' (hddimage has > oldest-built kernel)) seems to be in 1.4 M4, which I just tried today, even > though you checked in patches to fix it a month ago. I was puzzling over this for a bit until I checked - FYI, my patch (poky revision 406cb9920fad57a23d2139f657c41598eb5087bf) did not make it into 1.4_M4. It is in master and will be in M5 and of course the final 1.4 release. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre