From: Tomi Valkeinen <tomi.valkeinen@nokia.com>
To: ext Grazvydas Ignotas <notasas@gmail.com>,
"Maksim A. Boyko" <maksim.a.boyko@gmail.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: n810 video
Date: Tue, 02 Nov 2010 11:09:50 +0200 [thread overview]
Message-ID: <1288688990.5614.54.camel@tubuntu> (raw)
In-Reply-To: <AANLkTi=VcyzFBDGyko2RNpbdNhtv0pHKax8X6HnpVNuN@mail.gmail.com>
Hi,
On Mon, 2010-11-01 at 17:07 +0100, ext Grazvydas Ignotas wrote:
> hi,
>
> On Sat, Oct 30, 2010 at 11:40 AM, Maksim A. Boyko
> <maksim.a.boyko@gmail.com> wrote:
> > Hi,
> >
> > I try to switch on "OMAP2/3 Display Subsystem Support" and "Omap frame
> > buffer support" on n810 (commit 8b4b01).
> >
> > In OMAP2/3 Display Subsystem Support I used:
> > CONFIG_OMAP2_VRAM_SIZE=4
> > CONFIG_OMAP2_DSS_DEBUG_SUPPORT=y
> > CONFIG_OMAP2_DSS_DPI=y
> > CONFIG_OMAP2_DSS_VENC=y
> > CONFIG_PANEL_GENERIC=y
> >
> > In Omap frame buffer support I used:
> > CONFIG_FB=y
> > CONFIG_FB_OMAP_LCDC_EXTERNAL=y
> > CONFIG_FB_OMAP_LCDC_BLIZZARD=y
> > CONFIG_FB_OMAP_LCD_MIPID=y
> > CONFIG_FB_OMAP_BOOTLOADER_INIT=y
> > CONFIG_FB_OMAP=y
> > CONFIG_FB_OMAP_CONSISTENT_DMA_SIZE=2
> >
> > I create fb device:
> > #mknod /dev/fb0 c 29 0
> > #chgrp video /dev/fb0
> > #chmod 660 /dev/fb0
> >
> > But XServer 1.7.7-8 from debian squeeze armel don't work in both
> > cases. Tail of Xorg.0.log
> >
> > (II) LoadModule: "omapfb"
> > (II) Loading /usr/lib/xorg/modules/drivers/omapfb_drv.so
> > (II) Module omapfb: vendor="X.Org Foundation"
> > compiled for 1.7.4, module version = 0.1.1
> > ABI class: X.Org Video Driver, version 6.0
> > (II) omapfb: Driver for OMAP framebuffer (omapfb) and external LCD controllers:
> > omap1/2/3, S1D13745, HWA742
> > (WW) Falling back to old probe method for OMAPFB
> > (WW) Could not open '/dev/fb0': No such device or address(EE) No
> > devices detected
>
> The kernel driver probably failed to start, check your dmesg. I guess
> you'll need to update arch/arm/mach-omap2/board-n8x0.c and add dss2
> platform_data (see other board-* files for some examples).
Unfortunately there's no support in DSS2 for N800's Blizzard chip, so
you'll have to use the older omapfb driver. Or alternatively port the
Blizzard driver to DSS2, and probably make some fixes for DSS2's RFBI
support.
Tomi
next prev parent reply other threads:[~2010-11-02 9:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-30 8:40 n810 video Maksim A. Boyko
2010-11-01 16:07 ` Grazvydas Ignotas
2010-11-02 9:09 ` Tomi Valkeinen [this message]
2010-11-05 19:45 ` Maksim A. Boyko
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=1288688990.5614.54.camel@tubuntu \
--to=tomi.valkeinen@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=maksim.a.boyko@gmail.com \
--cc=notasas@gmail.com \
/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.