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
Subject: RE: QSD8250 illegal instruction
Date: Thu, 10 Jun 2010 13:51:40 -0700	[thread overview]
Message-ID: <1276203100.25006.22.camel@c-dwalke-linux.qualcomm.com> (raw)
In-Reply-To: <20100610203351.n7oa7jp9lcco0os4@webmail.htc-linux.org>

On Thu, 2010-06-10 at 20:33 +0100, Lukas-David Gorris wrote:
> Quoting Daniel Walker <dwalker@codeaurora.org>:
> 
> >
> > What kind of kernel did you use? You say you wanted to "avoid sdcard
> > driver interaction" , but was the sdcard actually compiled out?
> >
> > Daniel
> >
> 
> In reply to this and to your general proposition to narrow down the  
> problem I would like to mention that something like that was tried.  
> Markinus who wrote many of the patches in the mentioned htc-msm-2.6.32  
> branch made an approach to narrow down the problem by disabling  
> everything possible in the kernel configuration and manually removing  
> things from init, also SD. He still got the segfaults with a very very  
> basic kernel Image.

Ok .

> Did you see my mention of the DB vs BG timer config problem? As we  
> have to put a different config there than nexus, maybe there are some  
> minor differences in the SoC. Maybe that could be related to the  
> problem at hand.

I did see that.

> With regard to that we had some discussion on QSD8250 vs QSD8250B .  
> Maybe somebody can shed some light on this. Is there actually any  
> difference in B vs non-B ? Is there an A ? Or is this something like  
> MSM7200A vs msm7201A ?

I don't know of a QSD8250B SoC .. If there is one, I have no idea what
would be different.

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. Or it
could be a bootloader thing, does the Leo have fastboot ?

Daniel


  reply	other threads:[~2010-06-10 20:51 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 [this message]
2010-06-10 21:52                 ` Lukas-David Gorris
2010-06-10 22:04                   ` Daniel Walker
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=1276203100.25006.22.camel@c-dwalke-linux.qualcomm.com \
    --to=dwalker@codeaurora.org \
    --cc=Lukas-David@htc-linux.org \
    --cc=linux-arm-msm@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).