Hi Takashi,
I made a rework to load the firmware at a different time, when file
system is available.
I am now able to remove FW_LOADER_USER_HELPER_FALLBACK.
I will submit a new patch for this.
Vincent
On 10/29/2015 03:53 PM, Takashi Iwai wrote:
> On Thu, 29 Oct 2015 15:37:51 +0100,
> Emil Velik
On Thu, 29 Oct 2015 15:37:51 +0100,
Emil Velikov wrote:
>
> On 29 October 2015 at 14:21, Vincent ABRIOU wrote:
> > Hi Takashi,
> >
> > Removing FW_LOADER_USER_HELPER_FALLBACK leads to a failure in our HQVDP
> > firmware execution.
> > Indeed, our firmware is not built-in. It is a proprietary firm
On 29 October 2015 at 14:21, Vincent ABRIOU wrote:
> Hi Takashi,
>
> Removing FW_LOADER_USER_HELPER_FALLBACK leads to a failure in our HQVDP
> firmware execution.
> Indeed, our firmware is not built-in. It is a proprietary firmware
> uploaded into the file system that's why we need the
> USER_HELP
On Thu, 29 Oct 2015 15:21:35 +0100,
Vincent ABRIOU wrote:
>
> Hi Takashi,
>
> Removing FW_LOADER_USER_HELPER_FALLBACK leads to a failure in our HQVDP
> firmware execution.
> Indeed, our firmware is not built-in. It is a proprietary firmware
> uploaded into the file system that's why we need the
Hi Takashi,
Removing FW_LOADER_USER_HELPER_FALLBACK leads to a failure in our HQVDP
firmware execution.
Indeed, our firmware is not built-in. It is a proprietary firmware
uploaded into the file system that's why we need the
USER_HELPER_FALLBACK to be able to load it once file system is availabl
The commit [4fdbc678fe4d: drm: sti: add HQVDP plane] added the select
of CONFIG_FW_LOADER_USER_HELPER_FALLBACK by some unwritten reason.
But this config is known to be harmful, and is present only for
compatibility reason for an old exotic system that mandates udev
interaction which isn't supposed
6 matches
Mail list logo
