Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] RPi B+ update
Date: Wed, 17 May 2017 21:29:03 +0200	[thread overview]
Message-ID: <87fug35lkw.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <24ea86ee-9b48-816f-3e7a-6d5a985ea339@gmail.com> (Marco Trapanese's message of "Wed, 17 May 2017 17:28:26 +0200")

>>>>> "Marco" == Marco Trapanese <marcotrapanese@gmail.com> writes:

Hi,

 > Well, some good news. 
 > Using the latest versions of buildroot (2017.05-rc1-00062-g4b4fc27)
 > and kernel (4.9.21) I built an "empty" environment (without any
 > additional package but the rpi-firmware). Copying both zImage and the
 > fw files into the boot partition of the existing sd-card, leads to
 > boot-up again!

Great!

 > The problem now is related to the kernel drivers (wifi, rtc, cdc,
 > etc...) that I manually selected using make linux-menuconfig and that
 > were available (in the old rootfs) under /lib/modules/3.12.26. I'm
 > afraid the new kernel doesn't know where to find them - and perhaps it
 > cannot use them anyway because they are related to a different
 > version.

Yes, reusing the old kernel drivers with a new kernel is not going to
work.

 > It seems I need to update the whole system...

Unless the system boots with new fw and the old zImage. Did you try that
combination?


-- 
Bye, Peter Korsgaard

  parent reply	other threads:[~2017-05-17 19:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-16 19:32 [Buildroot] RPi B+ update Marco Trapanese
2017-05-16 21:23 ` Peter Seiderer
2017-05-17  6:05   ` Marco Trapanese
2017-05-17 15:28     ` Marco Trapanese
2017-05-17 17:36       ` Waldemar Brodkorb
2017-05-17 20:49         ` Marco Trapanese
2017-05-17 19:29       ` Peter Korsgaard [this message]
2017-05-16 21:46 ` Peter Korsgaard

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=87fug35lkw.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox