All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Brown <davidb@codeaurora.org>
To: Denis 'GNUtoo' Carikli <GNUtoo@no-log.org>
Cc: linux-arm-msm@vger.kernel.org, carlv@codeaurora.org
Subject: Re: msmfb issues on trout(htc dream)
Date: Thu, 26 May 2011 09:50:06 -0700	[thread overview]
Message-ID: <8yak4dde79d.fsf@huya.qualcomm.com> (raw)
In-Reply-To: <1306359834.31879.11.camel@gnutoo-desktop> (Denis Carikli's message of "Wed, 25 May 2011 23:43:54 +0200")

On Wed, May 25 2011, Denis 'GNUtoo' Carikli wrote:

> hi, I've tried booting linux-next on the htc dream again, and I have
> some very quick dmesg messages and at the end I can see that:
>>mdp irq already on already on 4 4
>>mdp_dma_to_mddi: busy
>>r7:c6039ed0
>>[<c004b7b8>] (do_group_exit+0x0/0x378)
>>r4:0839998f
>>[<c0057064>] (get_signal_to_deliver+0x0/0x378) from [<c002f354>]
>>(do_signal+0x98/0x52c)
>>mdp irq already on already on 4 4
>>mdp_dma_to_mddi: busy
>>[<c002f2bc>] (do_signal+0x00/0x52c) from [<c002fcd0>] (work_pending
> +0x24/0x28)
>>mdp irq already on already on 4 4
>>mdp_dma_to_mddi: busy
>>r4:000ad0d8
>>msmfb_start_dma 92.050 ms after vsync request
> I've also MMC issues but without fixing theses error first since it will
> displays even more garbage(since the msmfb and the mmc error are both
> printed to the screen)

I guess the first question is which framebuffer driver are you using?
There's one in drivers/staging/msm and another one in
drivers/video/msm.  The staging one hasn't been updated in a while, but
at least used to work on the dream.  I'm not sure if the video/msm
driver has been tested on the dream (or even the MSM7201A).  I've CC'd
Carl to see if he has any knowledge about this.

It is possible to use a serial console on the Dream, but the cables are
hard to come buy, but
<http://www.instructables.com/id/Android-G1-Serial-Cable/> can be
useful.  I recommend initially just hooking up the serial transmit line,
since overdriving the receiver can damage it.

It's kind of unfortunate that most of the people working on the MSM
support code tend to just work on the newer targets and it seems the
older targets break easily.  Hopefully we can figure out what is
happening here.

David

-- 
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.

  reply	other threads:[~2011-05-26 16:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-25 21:43 msmfb issues on trout(htc dream) Denis 'GNUtoo' Carikli
2011-05-26 16:50 ` David Brown [this message]
2011-05-26 17:00   ` Denis 'GNUtoo' Carikli

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=8yak4dde79d.fsf@huya.qualcomm.com \
    --to=davidb@codeaurora.org \
    --cc=GNUtoo@no-log.org \
    --cc=carlv@codeaurora.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.