All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: John Doe <xertz.yocto@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: Configuring linux-yocto-custom to build specific kernel modules
Date: Sun, 22 Sep 2013 22:38:01 -0400	[thread overview]
Message-ID: <523FA989.2010700@windriver.com> (raw)
In-Reply-To: <CAEo3mJVqezmQM5o8+=EozeHbU2O=WM91TGnZ=AJkGWRofbQ7yw@mail.gmail.com>

On 13-09-22 12:05 PM, John Doe wrote:
>> Is your kernel already building from linux-yocto-custom ? Or are you
>> using the default linux-yocto kernel and recipes already ?
>
> I have a project that is using linux-yocto-custom and another project
> which is using the default linux-yocto kernel.
>
>> If you are using one of the standard qemu machines, or a BSP that
>> is already working with linux-yocto*, you can simply enable the module
>> by creating a configuration fragment, and putting it on the SRC_URI.
>
> The problem is that I can not find the driver (rtl8187 under
> drivers/net/wireless/rtl818x) in the menuconfig. It seems all device
> drivers are missing despite them being in the repository or tarball.
>

If there's a missing dependency (say for example PCI), or a wrapping
Kconfig options that hides the menu, you won't see the drivers offered
in menuconfig.

Looking at the kernel source and the Kconfig is my next step, since it
lists all the dependencies that you need.

Bruce

> Cheers
> J
>



  reply	other threads:[~2013-09-23  2:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-20 19:53 Configuring linux-yocto-custom to build specific kernel modules John Doe
2013-09-20 19:56 ` Bruce Ashfield
2013-09-22 16:05   ` John Doe
2013-09-23  2:38     ` Bruce Ashfield [this message]
2013-10-11  9:27       ` John Doe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=523FA989.2010700@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=xertz.yocto@gmail.com \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.