linux-kernel - Re: Lattice ECP3 load firmware

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <53B6687A.3070108@denx.de>
Date:	Fri, 04 Jul 2014 10:40:26 +0200
From:	Stefan Roese <sr@...x.de>
To:	Jean-Michel Hautbois <jhautbois@...il.com>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: Lattice ECP3 load firmware

Hi Jean-Michel,

On 04.07.2014 10:24, Jean-Michel Hautbois wrote:
> I noticed you (Stefan) are using request_firmware_nowait() call. This
> means user needs to explicitly call it using
>
> $ echo 1 > /sys/class/firmware/lattice-ecp3.0/loading
> $ cat lattice-ecp3.bit > /sys/class/firmware/lattice-ecp3.0/data
> $ echo 0 > /sys/class/firmware/lattice-ecp3.0/loading
>
> Or did I miss something ?

No, thats correct. This is how we use it on our platform.

> I would like to have it load the firmware bitstream when booting if
> there is a specific .bit file in /lib/firmware. Maybe don't you want
> to have this behaviour, though... ?

No. We don't want this. Please don't ask me about the details. Its quite 
a while ago that I worked on this platform. And I don't have access to 
this platform any more.

Thanks,
Stefan

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/