linux-kernel - Re: [PATCH] rpmsg_ns: Work around TI non-standard message

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: <3518312.cLl3JjQhRp@somecomputer>
Date: Tue, 15 Oct 2024 20:00:47 +0200
From: Richard Weinberger <richard@...ma-star.at>
To: Mathieu Poirier <mathieu.poirier@...aro.org>
Cc: Richard Weinberger <richard@....at>, upstream@...ma-star.at, linux-remoteproc@...r.kernel.org, linux-kernel@...r.kernel.org, andersson@...nel.org, upstream+rproc@...ma-star.at, ohad@...ery.com, s-anna@...com, t-kristo@...com
Subject: Re: [PATCH] rpmsg_ns: Work around TI non-standard message

Am Dienstag, 15. Oktober 2024, 19:56:08 CEST schrieb Mathieu Poirier:
> > > In my opinion the real fix here is to get TI to use the standard message
> > > announcement structure.  The ->desc field doesn't seem to be that useful since
> > > it gets discarted.
> > 
> > This is for the future, the goal of my patch is helping people to
> > get existing DSP programs work with mainline.
> > Not everyone can or want to rebuild theirs DSP programs when moving to a mainline
> > kernel.
> 
> That's an even better argument to adopt the standard structure as soon as
> possible.  Modifying the mainline kernel to adapt to vendors' quirks doesn't
> scale.  

Well, I can't speak for TI.
But I have little hope.

Thanks,
//richard

-- 
sigma star gmbh | Eduard-Bodem-Gasse 6, 6020 Innsbruck, AUT
UID/VAT Nr: ATU 66964118 | FN: 374287y