Displaying 8 results from an estimated 8 matches for "gf100_gr_ctor_fw_legaci".
Did you mean:
gf100_gr_ctor_fw_legacy
2016 Nov 04
2
[PATCH v2] gr: fallback to legacy paths during firmware lookup
Look for firmware files using the legacy ("nouveau/nvxx_fucxxxx") path
if they cannot be found in the new, "official" path. User setups were
broken by the switch, which is bad.
There are only 4 firmware files we may want to look up that way, so
hardcode them into the lookup function. All new firmware files should
use the standard "nvidia/<chip>/gr/" path.
2016 Nov 02
3
[PATCH] gr: fallback to legacy paths during firmware lookup
Look for firmware files using the legacy ("nouveau/nvxx_fucxxxx") path
if they cannot be found in the new, "official" path. User setups were
broken by the switch, which is bad.
There are only 4 firmware files we may want to look up that way, so
hardcode them into the lookup function. All new firmware files should
use the standard "nvidia/<chip>/gr/" path.
2016 Nov 05
0
[PATCH v2] gr: fallback to legacy paths during firmware lookup
On Fri, Nov 04, 2016 at 06:36:17PM +0900, Alexandre Courbot wrote:
> Look for firmware files using the legacy ("nouveau/nvxx_fucxxxx") path
> if they cannot be found in the new, "official" path. User setups were
> broken by the switch, which is bad.
>
> There are only 4 firmware files we may want to look up that way, so
> hardcode them into the lookup
2016 Nov 02
0
[PATCH] gr: fallback to legacy paths during firmware lookup
On Wed, Nov 2, 2016 at 12:54 AM, Alexandre Courbot <acourbot at nvidia.com> wrote:
> Look for firmware files using the legacy ("nouveau/nvxx_fucxxxx") path
> if they cannot be found in the new, "official" path. User setups were
> broken by the switch, which is bad.
>
> There are only 4 firmware files we may want to look up that way, so
> hardcode them
2016 Nov 02
2
[PATCH] gr: fallback to legacy paths during firmware lookup
On 11/02/2016 02:07 PM, Ilia Mirkin wrote:
> On Wed, Nov 2, 2016 at 12:54 AM, Alexandre Courbot <acourbot at nvidia.com> wrote:
>> Look for firmware files using the legacy ("nouveau/nvxx_fucxxxx") path
>> if they cannot be found in the new, "official" path. User setups were
>> broken by the switch, which is bad.
>>
>> There are only 4
2019 Oct 08
4
[PATCH 1/5] drm/nouveau/gr/gf100-: make undeclared symbols static
The following functions are not declared outside of the
file they are in, so make them static to avoid these
warnings:
drivers/gpu/drm/nouveau/nvkm/engine/gr/gf100.c:745:1: warning: symbol 'gf100_gr_fecs_start_ctxsw' was not declared. Should it be static?
drivers/gpu/drm/nouveau/nvkm/engine/gr/gf100.c:760:1: warning: symbol 'gf100_gr_fecs_stop_ctxsw' was not declared. Should it be
2016 Nov 07
0
[PATCH] gr: fixup for legacy paths firmware lookup
The code would print a NULL string if no legacy firmware was found.
Signed-off-by: Alexandre Courbot <acourbot at nvidia.com>
Reported-by: Peter Wu <peter at lekensteyn.nl>
---
Hi Ben,
Sorry about the obvious mistake (and thanks Peter for reporting it!). You
may want to squash this one into the previous patch if there still is time.
drm/nouveau/nvkm/engine/gr/gf100.c | 7 ++-----
1
2016 Nov 03
0
[PATCH] gr: fallback to legacy paths during firmware lookup
On 11/02/2016 03:52 PM, Alexandre Courbot wrote:
> On 11/02/2016 02:07 PM, Ilia Mirkin wrote:
>> On Wed, Nov 2, 2016 at 12:54 AM, Alexandre Courbot <acourbot at nvidia.com> wrote:
>>> Look for firmware files using the legacy ("nouveau/nvxx_fucxxxx") path
>>> if they cannot be found in the new, "official" path. User setups were
>>>