All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] pull request: raspberry pi updates
Date: Wed, 12 Jun 2019 15:56:27 -0400	[thread overview]
Message-ID: <20190612195627.GX7115@bill-the-cat> (raw)
In-Reply-To: <CALeDE9OLEf+GUdZzu6Aeqs56hNQLxrSQyQzjBUTSYm9Ov0fGPw@mail.gmail.com>

On Wed, Jun 12, 2019 at 03:48:06PM +0100, Peter Robinson wrote:
> Hi Matthias,
> 
> Have these been out on the list for general review? I don't remember
> seeing them.
> 
> On Wed, Jun 12, 2019 at 1:57 PM Matthias Brugger <mbrugger@suse.com> wrote:
> >
> > Hi Tom,
> >
> > Please have a look on the following patches.
> >
> > Regards,
> > Matthias
> >
> > ---
> > The following changes since commit fc6c0e29a28f6b71dfb728b7f78e9e770f2cd218:
> >
> >   Prepare v2019.07-rc4 (2019-06-10 21:27:46 -0400)
> >
> > are available in the Git repository at:
> >
> >   https://github.com/mbgg/u-boot.git tags/rpi-next-2019.07
> >
> > for you to fetch changes up to 38e58ff2b785b45e8c8ade8e23f916a1984016c6:
> >
> >   ARM: bcm283x: Fix definition of MBOX_TAG_TEST_PIXEL_ORDER (2019-06-12 12:23:46
> > +0200)
> >
> > ----------------------------------------------------------------
> > - fix complation error for CONFIG_USB
> > - update RPi3 DTBs to v5.1-rc6 state
> > - add defconfig for RPi3 B+
> 
> Why do we need a separate config when it's detected and works
> perfectly well with the standard rpi_3 and rpi_3_32b configs?

Good question.  It came from Heinrich, so Heinrich?

> 
> > - Fix BCM2835_MBOX_TAG_TEST_PIXEL_ORDER define
> >
> > ----------------------------------------------------------------
> > Berkus Decker (1):
> >       ARM: bcm283x: Fix definition of MBOX_TAG_TEST_PIXEL_ORDER

For the record:
https://patchwork.ozlabs.org/patch/1024140/

> >
> > Heinrich Schuchardt (2):
> >       fdt: update bcm283x device tree sources to Linux 5.1-rc6 state
> >       ARM: defconfig: add Raspberry Pi 3 Model B+

https://patchwork.ozlabs.org/patch/1092162/
https://patchwork.ozlabs.org/patch/1092161/

> >
> > akaher (1):
> >       Fix compilation error if CONFIG_USB is disabled

I don't see this one in patchwork for some reason but it started out at
https://lists.denx.de/pipermail/u-boot/2019-April/363693.html

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190612/34b7254f/attachment.sig>

  reply	other threads:[~2019-06-12 19:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-12 12:57 [U-Boot] pull request: raspberry pi updates Matthias Brugger
2019-06-12 14:48 ` Peter Robinson
2019-06-12 19:56   ` Tom Rini [this message]
2019-06-12 20:07     ` Heinrich Schuchardt
2019-06-12 20:08       ` Tom Rini
2019-06-12 20:21         ` Heinrich Schuchardt
2019-06-12 20:25           ` Tom Rini
2019-06-24 18:11             ` Tom Rini
2019-06-25  3:51               ` Jonathan Gray
2019-06-25  4:53                 ` Heinrich Schuchardt
2019-06-25  7:58               ` Matthias Brugger
2019-06-26 11:09                 ` Matthias Brugger
2019-07-05 11:27                   ` Matthias Brugger
2019-07-05 14:58                     ` Tom Rini

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=20190612195627.GX7115@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /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.