linux-kernel - Re: RE: [PATCH v14 5/5] remoteproc: Add initial zynqmp R5 remoteproc driver

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

Message-ID: <20200918160721.GD15530@xaphan>
Date:   Fri, 18 Sep 2020 11:07:21 -0500
From:   Michael Auchter <michael.auchter@...com>
To:     Ben Levinsky <BLEVINSK@...inx.com>
Cc:     "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
        "linux-remoteproc@...r.kernel.org" <linux-remoteproc@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "linux-arm-kernel@...ts.infradead.org" 
        <linux-arm-kernel@...ts.infradead.org>
Subject: Re: RE: [PATCH v14 5/5] remoteproc: Add initial zynqmp R5 remoteproc driver

On Thu, Sep 17, 2020 at 10:50:42PM +0000, Ben Levinsky wrote:
> In addition to device tree, is there particular linker script you use
> for your R5 application? For example with OCM? As presently this
> driver only has DDR and TCM as supported regions to load into 

The firmware is being loaded to TCM.

I'm able to use this driver to load and run my firmware on both R5
cores, but only after I change the incorrect:

	rpu_mode = lockstep_mode

assignment to:

	rpu_mode = lockstep_mode ? PM_RPU_MODE_LOCKSTEP
				 : PM_RPU_MODE_SPLIT;