Re: [DISCUSSION] Hexagon code inside kernel

[cotulla@yandex.ua]

> šI think I've missed chunks of this conversation: what are you booting
> šit on?
>
> š(Wondering if I can get a test environment together. I haven't had one
> šsince I left qualcomm in 2010.)
>

Actually at the current time two persons are did some work in that project:
0)Cotulla (me) - HTC HD2 (HTC LEO) QSD8250B QDSP6v2
Image load done by custom MAGLDR bootloader.

1)jonpry - HP TouchPad (APQ8060) QDSP6v3
Image load done from kernel via PIL AFAIK.
He also tried it on APQ8064 with QDSP6v4 but no luck with loading unsigned LPASS images.


Current kernel code located here in GIT:
We took clear tree Linux 3.7.6 at the start and started to work with it.
https://github.com/detule/linux-hexagon


I am trying to bring up USB garget driver now.
Already found that arm/mach-msm is also nosense. In common it's bad, ugly code for something mythic. 
I was trying to use a built in chipidea driver, but it looks extremely overloaded and doesn't really fits for LEO hardware. 
I think I will try to port old msm7k_udc.c driver from 2.6.35. It's much more simple.


Also I found that adding "volatile" to variable declaration puts all accesses to it as not grouped into packets.
So it can be easy workaround for uncached memory access problem, instead of replacing everything to ioread32 and iowrite32.


-Cotulla