Re: [DISCUSSION] Hexagon code inside kernel

[cotulla@yandex.ua]

> šWhat would be some good models to try? (I dunno what has v3 or v4 in
> šit, not everything's got a qualcomm chipset...)
>

It's hard to advice. 
MSM8660/APQ8060 contains V3;
MSM8960/APQ8064 contains V4;
It also must be unlocked to run unsigned code. Most of modern phones are locked and it's rather hard to unlock that.
Note that some SoC contains QDSP5, not QDSP6.


> What I _do_ remember is that each instruction is 32 bits, and that one
> of those bits is the grouping bit which is either on or off (I forget
> which) to indicate the end of a packet.

Yea, same thing makes it hard to disassemble - it's hard to know where packet starts. And program flow is working only on packet edges.


>
> I really want qemu support for this. Sigh. Are there public assembly
> docs anywhere? (I had a giant printout brick circa 2010 but remember
> almost nothing from it and gave it back when I left...)

You can google for:
80-NB419-1_A_hexagon_v2_programmers_ref.pdf
80-NB419-2_A_hexagon_abi_spec.pdf


>
> If you poke Thomas Gleixner, he _might_ be able to help. (He did work
> under NDA, but some of the restrictions may have been relaxed when the
> code went upstream. If he can't help, he'll say so.)
>
> You won't get a lot of time out of him, but he may be able to answer
> questions about where code lives in various public trees...
>
I think it's just question of work ;)
It just need a some time to make it work.

Actually my device doesn't support USB OTG fully, ID pin is not used right as well no internal VBUS.
So I need change it to be able specify UDC or UHC mode manually by hands.


-Cotulla