From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Brown Subject: Re: msmfb issues on trout(htc dream) Date: Thu, 26 May 2011 09:50:06 -0700 Message-ID: <8yak4dde79d.fsf@huya.qualcomm.com> References: <1306359834.31879.11.camel@gnutoo-desktop> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from wolverine01.qualcomm.com ([199.106.114.254]:58630 "EHLO wolverine01.qualcomm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932308Ab1EZQuJ (ORCPT ); Thu, 26 May 2011 12:50:09 -0400 In-Reply-To: <1306359834.31879.11.camel@gnutoo-desktop> (Denis Carikli's message of "Wed, 25 May 2011 23:43:54 +0200") Sender: linux-arm-msm-owner@vger.kernel.org List-Id: linux-arm-msm@vger.kernel.org To: Denis 'GNUtoo' Carikli Cc: linux-arm-msm@vger.kernel.org, carlv@codeaurora.org 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 >>[] (do_group_exit+0x0/0x378) >>r4:0839998f >>[] (get_signal_to_deliver+0x0/0x378) from [] >>(do_signal+0x98/0x52c) >>mdp irq already on already on 4 4 >>mdp_dma_to_mddi: busy >>[] (do_signal+0x00/0x52c) from [] (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 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.