linux-kernel - Re: Using firmware interface to write configuration blob to MMR space

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-next>] [day] [month] [year] [list]

Message-ID: <55DCCC35.9060305@ti.com>
Date:	Tue, 25 Aug 2015 16:12:37 -0400
From:	Murali Karicheri <m-karicheri2@...com>
To:	<linux-firmware@...nel.org>
CC:	"Kwok, WingMan" <w-kwok2@...com>, <linux-kernel@...r.kernel.org>
Subject: Re: Using firmware interface to write configuration blob to MMR space

On 08/25/2015 02:52 PM, Murali Karicheri wrote:
> All,
>
> One of our SoC integrates a hardware block from a hardware vendor. The
> vendor has provided a configuration blob that is used to customize the
> hardware block for a specific application. This configuration blob is to
> be written to the MMR space to customize the hardware. The vendor is not
> willing to provide details of the registers. So I am wondering if I
> could use the firmware API (request_firmware) to copy the blob to the
> kernel space so that driver could write these values to the MMR space.
> Is this an acceptable way of using the firmware interface? My research
> so far doesn't see the interface used this way and looking for your
> expert opinion.
>


-- 
Murali Karicheri
Linux Kernel, Keystone
--
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/