From: Woody Suwalski <terraluna977@gmail.com>
To: "Deucher, Alexander" <Alexander.Deucher@amd.com>,
LKML <linux-kernel@vger.kernel.org>
Cc: "Koenig, Christian" <Christian.Koenig@amd.com>
Subject: Re: [4.5-rc regression] drm radeon Tahiti_vce fails to load
Date: Thu, 18 Feb 2016 12:04:50 -0500 [thread overview]
Message-ID: <56C5F9B2.7060508@gmail.com> (raw)
In-Reply-To: <BLUPR12MB0691190B27AE8F728B43CF95F7AF0@BLUPR12MB0691.namprd12.prod.outlook.com>
Deucher, Alexander wrote:
>> -----Original Message-----
>> From: Woody Suwalski [mailto:terraluna977@gmail.com]
>> Sent: Thursday, February 18, 2016 7:53 AM
>> To: LKML
>> Cc: Deucher, Alexander; Koenig, Christian
>> Subject: [4.5-rc regression] drm radeon Tahiti_vce fails to load
>>
>> Alex, the 4.5-rc 32-bit kernels seem to have a problem initializing VCE.
>> The drm.debug boot option does not show more info as to what the problem
>> is.
>> On 4.4 (tested with 4.4.1 and 4.4.2) kernels it is loading OK.
>>
>> I have confirmed the regression on 4.5-rc2 and 4.5-rc4 kernels.
> [ 1.051686] radeon 0000:01:00.0: Requesting firmware: radeon/TAHITI_vce.bin
> [ 1.051856] radeon 0000:01:00.0: Direct firmware load for radeon/TAHITI_vce.bin failed with error -2
> [ 1.051858] radeon 0000:01:00.0: radeon_vce: Can't load firmware "radeon/TAHITI_vce.bin"
>
>
> You did not include the vce firmware image in your kernel image. Please make sure to include the firmware image in your kernel image if you are building it in or if you are using an initrd, please make sure the firmware image is in your initrd.
>
> Alex
>
You are right - somehow the TAHITI_vce.bin got omitted from the kernel's
.config.
The Radeon included firmware line is now close to 3400 long, and
growing... Will there be a better way to manage these firmware blobs (a
rhetorical question)...
Thanks, Woody
prev parent reply other threads:[~2016-02-18 17:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 12:53 [4.5-rc regression] drm radeon Tahiti_vce fails to load Woody Suwalski
2016-02-18 16:30 ` Deucher, Alexander
2016-02-18 17:04 ` Woody Suwalski [this message]
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=56C5F9B2.7060508@gmail.com \
--to=terraluna977@gmail.com \
--cc=Alexander.Deucher@amd.com \
--cc=Christian.Koenig@amd.com \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).