> So I doubt they're loaded by the firmware loader (they are random data files,
> a
> compression test corpus) but maybe they are being used in a test inside the
> kernel and
> the firmware directory is hack to find them?
>
> I'm CCing some people who have touched the qat16 recipe lately (as it
On 23 May 2016 at 14:48, Burton, Ross wrote:
>
> On 23 May 2016 at 12:41, Jussi Kukkonen wrote:
>>
>> -FILES_${PN} = "/lib/firmware/*"
>> +FILES_${PN} = "${base_libdir}/firmware/*"
>
> If these files are being loaded by the kernel firmware loader
On 23 May 2016 at 14:48, Burton, Ross wrote:
>
> On 23 May 2016 at 12:41, Jussi Kukkonen wrote:
>>
>> -FILES_${PN} = "/lib/firmware/*"
>> +FILES_${PN} = "${base_libdir}/firmware/*"
>
>
> If these files are being loaded by the kernel firmware
On 23 May 2016 at 12:41, Jussi Kukkonen wrote:
> -FILES_${PN} = "/lib/firmware/*"
> +FILES_${PN} = "${base_libdir}/firmware/*"
>
If these files are being loaded by the kernel firmware loader then /lib is
right and the rest of the recipe is wrong.
Ross
--
Signed-off-by: Jussi Kukkonen
---
common/recipes-corpus/canterbury-corpus/canterbury-corpus.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/common/recipes-corpus/canterbury-corpus/canterbury-corpus.bb