From: Lucas Stach <dev@lynxeye.de>
To: "Michel Dänzer" <michel@daenzer.net>
Cc: "Christian König" <deathsimple@vodafone.de>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [Regression v4.2] Re: [PATCH 7/9] drm/radeon: add VCE 1.0 support v4
Date: Thu, 13 Aug 2015 08:36:08 +0200 [thread overview]
Message-ID: <1439447768.2230.13.camel@lynxeye.de> (raw)
In-Reply-To: <55CC36A4.7080106@daenzer.net>
Am Donnerstag, den 13.08.2015, 15:18 +0900 schrieb Michel Dänzer:
> On 13.08.2015 15:03, Lucas Stach wrote:
> > Hi Christian,
> >
> > this commit is causing a boot regression with v4.2-rcX on my Richland
> > APU (CHIP_ARUBA) based laptop. I didn't have time yet to track down
> > where exactly it is going wrong, but I bisected it down to this single
> > commit.
> >
> > I don't have the VCE firmware installed on this system, so from a quick
> > look at the code I would expect it to drop out pretty early and just
> > leave the VCE unconfigured, but otherwise keep things working as before.
> > This is unfortunately not the case.
>
> If the radeon driver is built into the kernel (or loaded from the
> initrd?), the attempt to load the firmware might take a long time to
> time out.
>
Gah. Thanks, I was too impatient to wait for the firmware loading to
time out. In fact this is a standard Fedora kernel config, so radeon is
a module, but it is built into the initrd.
So it's not really readeons fault, but one more iteration of the fact
that anything involving firmware loading is just horribly inconvenient.
Especially if it's firmware for an optional component.
Regards,
Lucas
next prev parent reply other threads:[~2015-08-13 6:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1431374515-2042-1-git-send-email-deathsimple@vodafone.de>
[not found] ` <1431374515-2042-7-git-send-email-deathsimple@vodafone.de>
2015-08-13 6:03 ` [Regression v4.2] Re: [PATCH 7/9] drm/radeon: add VCE 1.0 support v4 Lucas Stach
2015-08-13 6:18 ` Michel Dänzer
2015-08-13 6:36 ` Lucas Stach [this message]
2015-08-12 21:16 ` Christian König
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=1439447768.2230.13.camel@lynxeye.de \
--to=dev@lynxeye.de \
--cc=deathsimple@vodafone.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michel@daenzer.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