From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 76325E00809; Fri, 6 Feb 2015 01:58:45 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-1.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, FREEMAIL_REPLY, RCVD_IN_DNSWL_LOW autolearn=no version=3.3.1 X-Spam-HAM-Report: * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider * (picmaster[at]mail.bg) * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low * trust * [193.201.172.118 listed in list.dnswl.org] * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's * domain * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature * 1.0 FREEMAIL_REPLY From and body contain different freemails Received: from mx2.mail.bg (mx2.mail.bg [193.201.172.118]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id B883DE00757 for ; Fri, 6 Feb 2015 01:58:41 -0800 (PST) Received: from [192.168.0.123] (unknown [93.152.143.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mx2.mail.bg (Postfix) with ESMTPSA id A13856003F2E; Fri, 6 Feb 2015 11:58:40 +0200 (EET) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=mail.bg; s=default; t=1423216720; bh=vd73KyhN4WAxJWaxYJ9qciTvaR4GwyJvcFbL9IrxF1Q=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=SjVDsCSgl+0SlWXfWxhF1E9jOTr1IhIlYiVxjTOvCD3f4aTs98Q4WLRy0kMwdQXhI PmbMmzE/YiHLD+IGtGhrTle94yllhIN5vBYolqIe+mN+d2NQhEYm3GoALEfynEQEy8 Ws5W0k4fDNXZ4tFGfHZA/b9bpn57ZhDEDXhAafB0= Message-ID: <54D49050.4020200@mail.bg> Date: Fri, 06 Feb 2015 11:58:40 +0200 From: Nikolay Dimitrov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.4.0 MIME-Version: 1.0 To: "Alvin D.M. DIZON" References: <46557CEF4ABDB54B92C59390D2741FD1BD8C02@PCISGEX.pciltd.com.sg>, <46557CEF4ABDB54B92C59390D2741FD1BD8C82@PCISGEX.pciltd.com.sg> In-Reply-To: <46557CEF4ABDB54B92C59390D2741FD1BD8C82@PCISGEX.pciltd.com.sg> Cc: "meta-freescale@yoctoproject.org" , Otavio Salvador Subject: Re: Confused with adding drivers to kernel via bitbake -c menuconfig X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Feb 2015 09:58:45 -0000 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Hi Alvin, On 02/06/2015 04:59 AM, Alvin D.M. DIZON wrote: > Hello Otavio, > > If I set the drivers to be added as built-in, does that mean that the driver would be installed and loaded in the kernel? I ran "lsmod" and didn't see the bluetooth driver loaded. Am I missing something here? "lsmod" lists only loaded kernel modules (.ko files under /lib/modules/). If you enable a driver as built-in, it will be statically compiled in the kernel and won't show on "lsmod". Better way is to look in boot messages (dmesg) to see whether the drivers is initialized. > ________________________________________ > From: otavio.salvador@gmail.com [otavio.salvador@gmail.com] on behalf of Otavio Salvador [otavio@ossystems.com.br] > Sent: Thursday, February 05, 2015 7:23 PM > To: Alvin D.M. DIZON > Cc: meta-freescale@yoctoproject.org > Subject: Re: [meta-freescale] Confused with adding drivers to kernel via bitbake -c menuconfig > > On Thu, Feb 5, 2015 at 3:42 AM, Alvin D.M. DIZON > wrote: >> I would like to the generic USB bluetooth driver "btusb" to my i.MX6Q SABRE SD, so that my USB Bluetooth dongle(Cambridge Silicon Radio). Upon reading https://community.freescale.com/docs/DOC-100847 I enabled the Bluetooth subsystem support, RFCOMM, BNEP, and HIDP, as well as the HCI USB driver. I saved the .config file and copied it to the directory where my Linux recipe is (linux-imx_3.10.17.bb). I then renamed my .config file into defconfig, made a new folder called "files" and placed the defconfig in it. I also made a .bbappend file that contained >> >> FILESEXTRAPATHS_prepend := "${THISDIR}/files:" >> SRC_URI += "file://defconfig" >> >> I then ran "bitbake -c cleansstate linux-imx", after that I ran "bitbake fsl-image-x11". I flashed the resulting .sdcard file to an SD card, booted up my board, but found no trace of btusb. I tried doing "bitbake -f -c compile linux-imx" and then "bitbake -f -c deploy linux-imx", and copied the resulting uImage to my SD card's /media/Boot folder, but still no trace of btusb. I checked the tar archive for the kernel modules found in the /tmp/deploy/images/imx6qsabresd folder, and found two files called modules.order and modules.builtin, the btusb driver is listed in the modules.builtin file, but not mentioned in the modules.order file, I have also tried compiling the driver as module, and then ran the same commands as listed in the said link, but could not find the module. What am I doing wrong here? Any help will be will be appreciated, since I am new to Linux and the Yocto Project. > > You might have made it built-in, no? in this case no module will be > generated but it will be included in the kernel. > > -- > Otavio Salvador O.S. Systems > http://www.ossystems.com.br http://code.ossystems.com.br > Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750 > [PCI] > > Innovative Manufacturing Solutions. Professionally Delivered! > > The information contained in this email is confidential and is intended for addressee(s) only. If you have received this email in error, please notify the originator immediately. Nothing in this email shall constitute an offer or acceptance leading to a legally binding contract which shall only arise from a formal written agreement between yourselves and ourselves in the form of a Purchase Order issued by us and accepted by you in writing. For the avoidance of doubt, this email shall not be construed in any way as a formal written agreement. We accept no liability for any damage arising from alteration of the contents of this message by a third party or as a result of any virus being passed on. Please consider your environmental responsibility before printing this e-mail. > Regards, Nikolay