public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@sigma-star.at>
To: Mathieu Poirier <mathieu.poirier@linaro.org>, Andrew Davis <afd@ti.com>
Cc: Richard Weinberger <richard@nod.at>,
	upstream@sigma-star.at, linux-remoteproc@vger.kernel.org,
	linux-kernel@vger.kernel.org, andersson@kernel.org,
	upstream+rproc@sigma-star.at, ohad@wizery.com, s-anna@ti.com,
	t-kristo@ti.com
Subject: Re: [PATCH] rpmsg_ns: Work around TI non-standard message
Date: Tue, 03 Dec 2024 17:40:04 +0100	[thread overview]
Message-ID: <8065064.qOBuL9xsDt@somecomputer> (raw)
In-Reply-To: <901d75f1-76ad-4c32-920b-1e9b10270236@ti.com>

Andrew,

Am Dienstag, 3. Dezember 2024, 16:19:31 CET schrieb Andrew Davis:
> On 10/15/24 1:00 PM, Richard Weinberger wrote:
> > 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.
> > 
> 
> RPMSG_NS_2_0 is a compile time option, you can turn that off and rebuild
> the firmware to go back to the standard message structure. Our new firmware
> doesn't use that anyway (and it was only introduced to support some OpenMA
> firmware that had multiple channels. It was left on by default in some old
> firmware SDKs which is why NS_2.0 is in more firmware than it really needed
> to have been). Is there some specific firmware you a working with that cannot
> be rebuilt?

Cool, that's valuable information!

In the meanwhile I got contact to the right people to be able to rebuild the
firmware. The overall software stack is complicated and I'm just the Linux guy...

So, with some luck, the DSP application can work on mainline with
almost no kernel patches. :-)

Thanks,
//richard

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



      reply	other threads:[~2024-12-03 16:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-11 12:39 [PATCH] rpmsg_ns: Work around TI non-standard message Richard Weinberger
2024-10-12 15:53 ` kernel test robot
2024-10-14  9:24   ` Richard Weinberger
2024-10-15 16:48 ` Mathieu Poirier
2024-10-15 16:58   ` Richard Weinberger
2024-10-15 17:56     ` Mathieu Poirier
2024-10-15 18:00       ` Richard Weinberger
2024-10-29 16:15         ` Romain Naour
2024-12-03 15:19         ` Andrew Davis
2024-12-03 16:40           ` Richard Weinberger [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8065064.qOBuL9xsDt@somecomputer \
    --to=richard@sigma-star.at \
    --cc=afd@ti.com \
    --cc=andersson@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=ohad@wizery.com \
    --cc=richard@nod.at \
    --cc=s-anna@ti.com \
    --cc=t-kristo@ti.com \
    --cc=upstream+rproc@sigma-star.at \
    --cc=upstream@sigma-star.at \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox