Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] rpi-userland: bump revision for musl compile fixes
Date: Sat, 18 Oct 2014 13:34:46 +0200	[thread overview]
Message-ID: <20141018113446.GA31723@free.fr> (raw)
In-Reply-To: <20141018110508.GC3858@free.fr>

Maarten, All,

On 2014-10-18 13:05 +0200, Yann E. MORIN spake thusly:
> On 2014-10-17 17:57 +0200, Maarten ter Huurne spake thusly:
> > Signed-off-by: Maarten ter Huurne <maarten@treewalker.org>
> > ---
> > The second version of this patch was missing the "v2" label; this is
> > the third version.
> > 
> > The changes from v2, plus an additional change I made later were merged
> > upstream. This patch bumps the git revision to the merge commit.
> > 
> > rpi-userland-002-remove-faulty-assert.patch had to be updated to match
> > other changes in the code that are pulled in by the version bump.
> > I checked that the updated patch compiles fine, but I have no idea
> > whether it is still needed to fix or work around a runtime problem.
> 
> So, I have tested this bump: weston on the rpi no longer works, with or
> without the asser patch.
> 
> So, I NAK this bump for now.
> 
> I'll see to bisect rpi-userland to see where it breaks.

The culprit is:
    66338d3 vc_dispmanx: Fix vsync service use counting

Unfortunately, weston has yet no fix for that, and I could not spot any
fix for rpi-userland either... :-/

So, still NAK for this bump. We can still bump it up to ba753c1 as this
still works, but is not enough to get the musl fixes.

Maybe we could just hide it for musl for now?

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2014-10-18 11:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-12  1:45 [Buildroot] [PATCH] rpi-userland: Add patches to fix compilation with musl libc Maarten ter Huurne
2014-09-12  7:32 ` Thomas Petazzoni
2014-09-12 14:56   ` Maarten ter Huurne
2014-09-12 15:11     ` Thomas Petazzoni
2014-09-12 17:01       ` Maarten ter Huurne
2014-10-17 15:57         ` [Buildroot] [PATCH v3] rpi-userland: bump revision for musl compile fixes Maarten ter Huurne
2014-10-17 20:31           ` Yann E. MORIN
2014-10-18 11:05           ` Yann E. MORIN
2014-10-18 11:34             ` Yann E. MORIN [this message]
2014-10-18 12:15               ` Maarten ter Huurne
2014-10-18 13:02                 ` Yann E. MORIN
2014-10-18 16:46                   ` Maarten ter Huurne
2014-10-18 17:16                     ` Yann E. MORIN
2014-10-18 17:22                       ` Maarten ter Huurne
2014-10-18 17:58                     ` [Buildroot] [PATCH v4] rpi-userland: bump revision and add patch to fix compile with musl Maarten ter Huurne
2014-10-19 10:32                       ` Yann E. MORIN
2014-10-19 14:37                       ` Thomas Petazzoni

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=20141018113446.GA31723@free.fr \
    --to=yann.morin.1998@free.fr \
    --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