All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <deathsimple@vodafone.de>
To: "Lucas Stach" <dev@lynxeye.de>, "Michel Dänzer" <michel@daenzer.net>
Cc: 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: Wed, 12 Aug 2015 23:16:45 +0200	[thread overview]
Message-ID: <55CBB7BD.3090105@vodafone.de> (raw)
In-Reply-To: <1439447768.2230.13.camel@lynxeye.de>

On 13.08.2015 08:36, Lucas Stach wrote:
> 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.

Yeah, exactly. The timeout for loading the firmware is really long on 
both the standard Fedora as well as Ubuntu kernels. Not sure if that's 
the default or just their configuration.

While it doesn't have the highest priority for us I usually still do 
tests if working without firmware still works once or twice during the 
upstreaming process. So if you really find that the box doesn't work 
without the firmware leave me a note and I will fix it.

Best regards,
Christian.

>
> Regards,
> Lucas
>

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

WARNING: multiple messages have this Message-ID (diff)
From: "Christian König" <deathsimple@vodafone.de>
To: "Lucas Stach" <dev@lynxeye.de>, "Michel Dänzer" <michel@daenzer.net>
Cc: 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: Wed, 12 Aug 2015 23:16:45 +0200	[thread overview]
Message-ID: <55CBB7BD.3090105@vodafone.de> (raw)
In-Reply-To: <1439447768.2230.13.camel@lynxeye.de>

On 13.08.2015 08:36, Lucas Stach wrote:
> 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.

Yeah, exactly. The timeout for loading the firmware is really long on 
both the standard Fedora as well as Ubuntu kernels. Not sure if that's 
the default or just their configuration.

While it doesn't have the highest priority for us I usually still do 
tests if working without firmware still works once or twice during the 
upstreaming process. So if you really find that the box doesn't work 
without the firmware leave me a note and I will fix it.

Best regards,
Christian.

>
> Regards,
> Lucas
>


  reply	other threads:[~2015-08-13  9:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-11 20:01 [PATCH 1/9] drm/radeon: rework VCE FW size calculation Christian König
2015-05-11 20:01 ` [PATCH 2/9] drm/radeon: allow some more VCE firmware versions Christian König
2015-05-11 20:01 ` [PATCH 3/9] drm/radeon: implement si_set_vce_clocks v2 Christian König
2015-05-11 20:01 ` [PATCH 4/9] drm/radeon: implement tn_set_vce_clocks Christian König
2015-05-11 20:01 ` [PATCH 5/9] drm/radeon/dpm: add vce dpm support for TN Christian König
2015-05-11 20:01 ` [PATCH 6/9] drm/radeon/dpm: add vce support for SI Christian König
2015-05-11 20:01 ` [PATCH 7/9] drm/radeon: add VCE 1.0 support v4 Christian König
2015-08-13  6:03   ` [Regression v4.2] " Lucas Stach
2015-08-13  6:18     ` Michel Dänzer
2015-08-13  6:18       ` Michel Dänzer
2015-08-13  6:36       ` Lucas Stach
2015-08-13  6:36         ` Lucas Stach
2015-08-12 21:16         ` Christian König [this message]
2015-08-12 21:16           ` Christian König
2015-05-11 20:01 ` [PATCH 8/9] drm/radeon: add support for vce 1.0 clock gating Christian König
2015-05-11 20:01 ` [PATCH 9/9] drm/radeon/tn/si: enable/disable vce cg when encoding v2 Christian König
2015-05-12 15:53 ` [PATCH 1/9] drm/radeon: rework VCE FW size calculation Alex Deucher

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=55CBB7BD.3090105@vodafone.de \
    --to=deathsimple@vodafone.de \
    --cc=dev@lynxeye.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 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.