From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.windriver.com (mail.windriver.com [147.11.1.11]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by yocto-www.yoctoproject.org (Postfix) with ESMTPS id 4491CE00496 for ; Fri, 8 Mar 2013 09:13:13 -0800 (PST) Received: from ALA-HCA.corp.ad.wrs.com (ala-hca.corp.ad.wrs.com [147.11.189.40]) by mail.windriver.com (8.14.5/8.14.3) with ESMTP id r28HDAwl023384 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 8 Mar 2013 09:13:10 -0800 (PST) Received: from [128.224.146.67] (128.224.146.67) by ALA-HCA.corp.ad.wrs.com (147.11.189.50) with Microsoft SMTP Server id 14.2.342.3; Fri, 8 Mar 2013 09:13:10 -0800 Message-ID: <513A1C1A.4030506@windriver.com> Date: Fri, 8 Mar 2013 12:12:58 -0500 From: Bruce Ashfield User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: =?ISO-8859-1?Q?Hans_Beck=E9rus?= References: In-Reply-To: Cc: yocto@yoctoproject.org Subject: Re: How do I control what kernel modules are being loaded? 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: Fri, 08 Mar 2013 17:13:13 -0000 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 8bit On 13-03-08 07:08 AM, Hans Beckérus wrote: > Hi. I have built some custom kernel modules (.ko) using a .bb that > inherits from the module.bbclass. There is one main kernel module and > the rest are dependent on the first. Building and installing the > modules to the rootfs works fine. Next question is how do I control > what actual modules are loaded at boot, or actually how do I control > this through Yocto? To my surprise one of the kernel module loaded > automatically!? How could this happen? I did not have an entry for it > in /etc/modules. And what do I need to do to actually add entries to > /etc/modules? Or is there some other mechanism that I should use. I > tried going through the module.bbclass but must admit I lost it > somewhere in the middle ;) Any guidance would be appreciated. module_autoload_, in your module recipe, will trigger the load on boot. Cheers, Bruce > > Hans > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto >