All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrei Gherzan <andrei@gherzan.ro>
To: Alex J Lennon <ajlennon@dynamicdevices.co.uk>
Cc: yocto@yoctoproject.org, Jonatan Magnusson <jonatan.magnusson@gmail.com>
Subject: Re: [meta-raspberrypi] how to customize kernel config?
Date: Thu, 14 Aug 2014 19:51:33 +0200	[thread overview]
Message-ID: <20140814175133.GJ18247@gmail.com> (raw)
In-Reply-To: <539A11D5.5030805@dynamicdevices.co.uk>

Hi Jonatan,

Did you managed to try Alex's patch? https://review.gherzan.ro:8443/#/c/106/
Your feedback would be helpful.

Thanks,

On Thu, Jun 12, 2014 at 09:47:17PM +0100, Alex J Lennon wrote:
>
> On 12/06/2014 07:48, Jonatan Magnusson wrote:
> > Hi
> >
> > I’m trying to use the meta-raspberrypi BSP with Yocto (1.6, Daisy).
> >
> > It works great, except I have no idea how to use a custom kernel config!
> >
> > I have a custom kernel recipe that bbappends to the meta-raspberrypi kernel recipe.
> >
> > I’ve tried using defconfig as well as configuration fragments, but neither work.
> >
> > I’ve also tried using the kernel_configure_variable function, and that almost works, except if I try to disable an option that is enabled earlier in the the config file, the option is still enabled since kernel_configure_variable only appends to the config file.
> >
> > Example:
> >
> > do_configure_append() {
> >   kernel_configure_variable SPI_SPIDEV n
> > }
> >
> > So I wonder: how is this supposed to work?
> >
> > In my case I need to enable CONFIG_IEEE802154_MRF24J40 and it’s dependencies and disable CONFIG_SPI_SPIDEV and a few more.
> >
> > I’ve found no help on IRC and all Google comes up with is this old discussion, which does not lead to a solution:
> >
> > https://lists.yoctoproject.org/pipermail/yocto/2013-November/017113.html
> >
> > I would be very happy to get any hints on how this is supposed to work!
>
> Jonatan,
>
> I have a patch set here which I believe will enable configuration
> fragment support (yocto-ization) for the RPi as detailed in the Yocto
> Kernel Development Manual.
>
> It needs more testing before I would be comfortable releasing it, and I
> am short of time right now. The kernel builds and my testing shows that
> the config and config. fragments seem to get picked up, but I haven't
> tested on a board yet as I have run into trouble moving up from Yocto
> daisy to master.
>
> I wonder if you would be interested in taking a look at it with me?
> If/when it worked/works you should be able to simply add a foo.cfg file
> with your CONFIG_foo to SRC_URI in a .bbappend and that should get
> pulled in as you need.
>
> Cheers,
>
> Alex
>
>
> Cheer
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

--
Andrei Gherzan


      reply	other threads:[~2014-08-14 17:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-12  6:48 [meta-raspberrypi] how to customize kernel config? Jonatan Magnusson
2014-06-12  6:55 ` Jens Lucius
2014-06-12  7:31 ` Alex J Lennon
2014-06-12 20:47 ` Alex J Lennon
2014-08-14 17:51   ` Andrei Gherzan [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=20140814175133.GJ18247@gmail.com \
    --to=andrei@gherzan.ro \
    --cc=ajlennon@dynamicdevices.co.uk \
    --cc=jonatan.magnusson@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.