From: cotulla@yandex.ua
To: linux-hexagon@vger.kernel.org
Subject: Re: [DISCUSSION] Hexagon code inside kernel
Date: Sat, 16 Feb 2013 23:21:40 +0400 [thread overview]
Message-ID: <1568431361042500@web1g.yandex.ru> (raw)
In-Reply-To: <CAHrUA37eKrJXMQhgfNcZL5_Vdm0x=RGeH1q6ugWaJaCH7qZ-gg@mail.gmail.com>
> š! šI did not know that. šBTW, be aware that there are usually two
> šdifferent qdsp's on there. šThe smaller/older/slower one is running
> šthe radio signal processing code and it is very locked down, as that
> šcode is considered to be extremely valuable. š(Its also the one that
> šhas total control over all the master interrupt masks, which not even
> šthe ARM can over-ride). šI'm not sure, the radio processor might not
> ševen be a qdsp6, it might be a qdsp5 or qdsp4, I never paid attention
> što that. šBut the point is: šif it seems like its locked down, make
> šsure you've got the right one, that there isn't another one sitting
> šthere on the JTAG chain.
>
It depends from QCT chipset.
In old ones ARM + QDSP4 are used for modem operations.
And QDSP5 or QDSP6 for multimedia tasks.
New ones contains 2 x QDSP6 for modem usage and 1 x QDSP6 for audio.
So actually in some chipsets there are up to 3 QDSP6 instances nowdays.
But a problem that it's heavy locked nowdays. (signature checking, hardware key + hardware crypto engine)
So it's hard task to load own code to QDSP6 :-(
So you worked primary on userland QDSP6 support?
-Cotulla
next prev parent reply other threads:[~2013-02-16 19:21 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-15 14:28 [DISCUSSION] Hexagon code inside kernel cotulla
[not found] ` <CAHrUA364XES66kXhr0Gg1dh_MQBAS0+R8Q4x+EY3dgz6s=QRww@mail.gmail.com>
2013-02-15 22:33 ` Linas Vepstas
2013-02-16 1:35 ` cotulla
2013-02-16 2:34 ` Linas Vepstas
2013-02-16 12:39 ` cotulla
2013-02-16 17:33 ` Linas Vepstas
2013-02-16 19:21 ` cotulla [this message]
2013-02-19 4:36 ` rkuo
2013-02-19 14:29 ` Linas Vepstas
2013-02-20 1:07 ` cotulla
2013-02-20 1:17 ` cotulla
2013-02-23 4:24 ` Rob Landley
2013-02-24 12:00 ` cotulla
2013-02-24 16:32 ` Linas Vepstas
2013-02-24 17:29 ` cotulla
2013-02-24 21:03 ` Linas Vepstas
2013-02-25 17:26 ` Rob Landley
2013-02-26 18:54 ` cotulla
2013-02-27 0:58 ` Rob Landley
2013-02-27 12:39 ` cotulla
2013-02-24 12:23 ` cotulla
2013-02-26 6:55 ` Rob Landley
2013-02-26 19:30 ` cotulla
2013-02-26 19:32 ` cotulla
2013-02-26 19:59 ` Linas Vepstas
2013-02-26 20:25 ` cotulla
2013-02-26 20:57 ` Linas Vepstas
2013-02-27 1:06 ` Rob Landley
2013-02-27 1:30 ` Linas Vepstas
2013-02-27 3:03 ` Rob Landley
2013-02-27 12:35 ` cotulla
-- strict thread matches above, loose matches on Subject: below --
2013-02-24 0:24 Linas Vepstas
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=1568431361042500@web1g.yandex.ru \
--to=cotulla@yandex.ua \
--cc=linux-hexagon@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.