linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Walker <dwalker@codeaurora.org>
To: Lukas-David Gorris <Lukas-David@htc-linux.org>
Cc: linux-arm-msm@vger.kernel.org, linux-arm@vger.kernel.org
Subject: RE: QSD8250 illegal instruction
Date: Thu, 10 Jun 2010 15:04:25 -0700	[thread overview]
Message-ID: <1276207465.25006.36.camel@c-dwalke-linux.qualcomm.com> (raw)
In-Reply-To: <20100610225232.0nrjbd5zhcg804sg@webmail.htc-linux.org>

On Thu, 2010-06-10 at 22:52 +0100, Lukas-David Gorris wrote:
> Quoting Daniel Walker <dwalker@codeaurora.org>:
> 
> > 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 ?

> > 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 ?

Daniel


  reply	other threads:[~2010-06-10 22:04 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-06  2:53 QSD8250 illegal instruction Lukas-David Gorris
2010-06-09 16:35 ` Daniel Walker
2010-06-09 20:18   ` Le Tama
2010-06-10 16:49     ` Daniel Walker
2010-06-10 17:37       ` Lukas-David Gorris
2010-06-10 17:51         ` Daniel Walker
2010-06-10 18:24         ` Le Tama
2010-06-10 18:41           ` Daniel Walker
2010-06-10 19:23             ` Le Tama
2010-06-10 19:33             ` Lukas-David Gorris
2010-06-10 20:51               ` Daniel Walker
2010-06-10 21:52                 ` Lukas-David Gorris
2010-06-10 22:04                   ` Daniel Walker [this message]
2010-06-10 22:37                     ` Lukas-David Gorris
2010-06-10 18:52           ` Daniel Walker
  -- strict thread matches above, loose matches on Subject: below --
2010-05-29 19:46 lukas
2010-05-29 19:20 lukas
2010-06-01 16:54 ` David Brown
2010-06-03  1:13   ` lukas
2010-06-06  2:23     ` Lukas-David Gorris

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=1276207465.25006.36.camel@c-dwalke-linux.qualcomm.com \
    --to=dwalker@codeaurora.org \
    --cc=Lukas-David@htc-linux.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-arm@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).