| 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
| ||
|
Message-ID: <CAK=WgbYLDTNjbq=Qn7wFqN44PTM7yqAVjDZycEq4Eri5C5unGg@mail.gmail.com> Date: Thu, 26 Nov 2015 11:05:13 +0200 From: Ohad Ben-Cohen <ohad@...ery.com> To: Stefan Agner <stefan@...er.ch> Cc: linux-arm <linux-arm-kernel@...ts.infradead.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: [PATCH] remoteproc: report error if resource table doesn't exist Hi Stefan, On Sat, Aug 29, 2015 at 4:08 AM, Stefan Agner <stefan@...er.ch> wrote: > Currently, if the resource table is completely missing in the > firmware, powering up the remoteproc fails silently. Add a message > indicating that the resource table is missing in the firmware. > > Signed-off-by: Stefan Agner <stefan@...er.ch> Applied to remoteproc-next, thanks. > This also opens up a more general question: Is it mandatory to have > a resource table in the firmware? The implementation we have today does require it, but that's just because this is what we had to support so far. > Theoretically a remoteproc could > also work completely independent, all what would be used from the > remoteproc framework is the loading and starting capabilities... Sure. Feel free to add support for your hardware as needed. Thanks, Ohad. -- 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/
Powered by blists - more mailing lists