All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: Toby Gomersall <toby.gomersall@smartacoustics.co.uk>,
	yocto@yoctoproject.org
Subject: Re: yocto on zynq, How to configure kernel to include drivers
Date: Wed, 4 Nov 2015 08:55:58 -0500	[thread overview]
Message-ID: <563A0E6E.9010005@balister.org> (raw)
In-Reply-To: <563A09A3.4050706@smartacoustics.co.uk>

[-- Attachment #1: Type: text/plain, Size: 896 bytes --]

On 11/04/2015 08:35 AM, Toby Gomersall wrote:
> I'm quite new to yocto so still have a lot to learn. I'm trying to
> include the DMA drivers in my yocto build for a Zynq based on the
> meta-xilinx layer (http://git.yoctoproject.org/cgit/cgit.cgi/meta-xilinx/).

You should try emailing this list for meta-xilinx specific issues.

https://lists.yoctoproject.org/listinfo/meta-xilinx

Philip

> 
> I thought I'd be able to add them in the kernel configuration
> (menuconfig) by running (from within the build directory):
> 
> bitbake linux-xlnx -c kernel_configme -f
> bitbake linux-xlnx -c menuconfig
> 
> I can't see the DMA drivers in menuconfig. However if I run menuconfig
> within the linux-xlnx tree (which is referenced by the SRCURI) I can see
> the DMA drivers. Is there some reason they're hidden in the build
> menuconfig?
> 
> Thanks,
> Toby
> 
> 
> 
> 


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 484 bytes --]

      parent reply	other threads:[~2015-11-04 13:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-04 13:35 yocto on zynq, How to configure kernel to include drivers Toby Gomersall
2015-11-04 13:47 ` Hecht, Martin (Silica)
2015-11-04 14:20   ` Toby Gomersall
2015-11-04 15:08     ` Nathan Rossi
2015-11-05 11:16       ` Toby Gomersall
2015-11-04 13:55 ` Philip Balister [this message]

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=563A0E6E.9010005@balister.org \
    --to=philip@balister.org \
    --cc=toby.gomersall@smartacoustics.co.uk \
    --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.