Quoting Daniel Walker <dwalker@xxxxxxxxxxxxxx>:
On Thu, 2010-06-10 at 22:52 +0100, Lukas-David Gorris wrote:
Quoting Daniel Walker <dwalker@xxxxxxxxxxxxxx>:
> I don't know of a QSD8250B SoC .. If there is one, I have no idea what
> would be different.
Ok fine. So SoC revision seems like nothing to worry about.
Where are you getting the B distinction from ? something your getting
out of WinCE ?
Yes, in the WinCE hardware information program it says CPU:
QUALCOMM(R) QSD8250B .
> It might be that the baseband processor is running different code
> between the Nexus One and the Leo (i.e. different modem images), and
> that code is programming the SoC differently between the two.
Yes, we do have a different modem image. The Leo AMSS version is for
WinCE. The device comes with windows mobile 6.5 installed.
Can you think of anything specifically regarding different SoC
programming between different AMSS version? Some magic proc_comm to
send?
> Or it could be a bootloader thing, does the Leo have fastboot ?
We are using http://htc-linux.org/wiki/index.php?title=HaRET to boot
linux on Leo. So at boot time, all the hardware is initialized already
by WinCE.
Ok .. I suppose there could be something different between what WinCE
expects, and what Linux expect. Do you know if this method has been used
successfully on other HTC phones with Qualcomm SoC's ?
It has never been a problem to run linux using HaRET on msm7xxx
(non-A) and msm7xxxA based WinCE devices. I don't know of any haret
code for msm7* that handles low level initialization stuff other than
things about starting the kernel (which we obviously do successfully
on Leo). I will investigate this further.
But I can say I have never seen such a problem before. Once kernel on
msm7* is started, things just work. No strange low level problems as
seen on Leo I know of.
As for qsd8xxxx Leo is the first device we are booting linux on using haret.
Thanks
Lukas
--
To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
