All of lore.kernel.org
 help / color / mirror / Atom feed
From: rscr <rafacrespiramon@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Custom tarball and .config file
Date: Tue, 10 Dec 2019 07:58:53 -0600 (CST)	[thread overview]
Message-ID: <1575986333615-0.post@n4.nabble.com> (raw)
In-Reply-To: <20191210141145.5969eb63@windsurf>

Hi, 

I am new on Linux and buildroot, so it is possible I have misunderstood many
things. I will try to explain:

For testing purposes, I'm using a local linux source, downloaded from the
raspberry's github: linux-rpi-4.19.y

I have added to the linux source a kernel driver that I am testing ( If I
build the kernel out of buildroot it builds correct )

Now I want to use that linux kernel on Buildroot, so I tar the source, and I
set:

BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION="file://home/tec/rcr/tools/src/linux-rpi-4.19.y.tar.gz"


This is my buildroot's kernel configuration

BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_TARBALL=y
BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y
BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="/home/tec/rcr/projects/cp4/rscr_br2_extree/configs/ibLinux_defconfig"
BR2_LINUX_KERNEL_DTS_SUPPORT=y
BR2_LINUX_KERNEL_INTREE_DTS_NAME="bcm2708-rpi-zero-w"
BR2_LINUX_KERNEL_NEEDS_HOST_OPENSSL=y

Now my q?estion:

*How can I configure my custom kernel in buildroot, in order to select the
device drivers I have added? If I run linux-menuconfig does not appear the
driver on the Device Drivers menu. It seems it is pointing to another linux
source*

Kind Regards, 

Rafa







--
Sent from: http://buildroot-busybox.2317881.n4.nabble.com/

  reply	other threads:[~2019-12-10 13:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-10  7:54 [Buildroot] Custom tarball and .config file rscr
2019-12-10 13:11 ` Thomas Petazzoni
2019-12-10 13:58   ` rscr [this message]
2019-12-12  6:59     ` rscr
2019-12-13 12:27       ` rscr

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=1575986333615-0.post@n4.nabble.com \
    --to=rafacrespiramon@gmail.com \
    --cc=buildroot@busybox.net \
    /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.