All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Bark <martin@barkynet.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/4] package/rpi-firmware: improve installation of dtb files
Date: Fri, 16 Mar 2018 10:52:54 +0000	[thread overview]
Message-ID: <CAFGQKxdXDVU_yWcrsiawYR2-=a7=FAp34=AOqB4EXXTCCyH7sg@mail.gmail.com> (raw)
In-Reply-To: <D04562A3-E6F9-44CB-862F-AD1B3D6D9941@jens-maus.de>

Jenus,

On 16 March 2018 at 09:32, Jens Maus <mail@jens-maus.de> wrote:
> BTW: As you seem to push updates regarding Pi3+ I have some more patches at hand for you :)
>
> https://github.com/jens-maus/RaspberryMatic/blob/master/buildroot-patches/0003-rpi-wifi-firmware.patch
> https://github.com/jens-maus/RaspberryMatic/blob/master/buildroot-patches/0004-wiringpi.patch
>
> The first is to actually get WiFi working again because the NVRAM settings file is different for the new WiFi chip of the Pi3+. The second updates the wiringpi package to the latest master version which fixes compatibility to the Pi3+.
>
> Sorry that I am not able to submit these patches myself via patchwork to buildroot, but my time is unfortunately limited these days. However, feel free to submit these patches yourself.

Yes I'm happy to submit a patch to update rpi-wifi-firmware.  I have a
rpi3b+ now so i can test this.  I don't use wiringpi so i think it
might be better if someone else more familiar with the package updates
it.

For some reason my v2 patch set disappeared into /dev/null in
patchwork.   I'll include the updates to rpi-wifi-firmware and submit
a v3 patchset.

Thanks

Martin

>
> Regards,
> Jens

[--SNIP--]

>
> --
> Jens Maus, Dresden/Germany
> http://jens-maus.de/
>
> *** Content is authentic only with digital signature  ***
>

  reply	other threads:[~2018-03-16 10:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-15 13:24 [Buildroot] [PATCH 1/4] package/rpi-firmware: bump version Martin Bark
2018-03-15 13:24 ` [Buildroot] [PATCH 2/4] configs/raspberrypi*: bump kernel version Martin Bark
2018-03-15 13:24 ` [Buildroot] [PATCH 3/4] board/raspberrypi: add support for rpi3 b+ Martin Bark
2018-03-15 13:33   ` Baruch Siach
2018-03-15 14:07     ` Martin Bark
2018-03-15 13:24 ` [Buildroot] [PATCH 4/4] package/rpi-firmware: improve installation of dtb files Martin Bark
2018-03-15 19:40   ` Peter Seiderer
2018-03-15 19:58     ` Martin Bark
2018-03-15 21:59       ` Yann E. MORIN
2018-03-15 22:40         ` Martin Bark
2018-03-16  9:32           ` Jens Maus
2018-03-16 10:52             ` Martin Bark [this message]
2018-03-16 13:07               ` Peter Korsgaard
2018-03-16 13:12               ` Jens Maus
2018-03-16 18:08                 ` Martin Bark
2018-03-15 19:28 ` [Buildroot] [PATCH 1/4] package/rpi-firmware: bump version Peter Seiderer
2018-03-15 20:23   ` Martin Bark

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='CAFGQKxdXDVU_yWcrsiawYR2-=a7=FAp34=AOqB4EXXTCCyH7sg@mail.gmail.com' \
    --to=martin@barkynet.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.