From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from xkh0.infr.xiaoka.com ([85.11.67.240]:59097 "EHLO xkh0.infr.xiaoka.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753199Ab0JEVpg (ORCPT ); Tue, 5 Oct 2010 17:45:36 -0400 Received: from [84.79.160.54] (helo=[192.168.2.105]) by xkh0.infr.xiaoka.com with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from ) id 1P3FK9-0001Rz-Kb for linux-arm-msm@vger.kernel.org; Tue, 05 Oct 2010 23:45:35 +0200 Subject: X.Org fbdev driver and msm_fb From: Tomasz Sterna Content-Type: text/plain; charset="UTF-8" Date: Tue, 05 Oct 2010 23:45:23 +0200 Message-ID: <1286315123.1905.17.camel@wing> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-arm-msm-owner@vger.kernel.org List-ID: To: linux-arm-msm@vger.kernel.org Hi. I am using msm-2.6.35 branch from git://codeaurora.org/kernel/msm.git and I am puzzled with it's msm_fb If I try to put anything on screen, nothing happens. Even as simple test as below doesn't break my display, which displays textmode console just fine. [root@localhost ~]# cat /dev/urandom > /dev/fb0 cat: write error: No space left on device [root@localhost ~]# Nothing and I should have trash on screen. On the other hand if I do run X.Org fbdev X server, it does trash my screen and hangs the device then. Any ideas? In case of anyone is interested, here's a log from X start: http://pastebin.com/fR6FPXSt