From: Dirk Behme <dirk.behme@googlemail.com>
To: "Sideleau, Scott R" <srs@WPI.EDU>
Cc: OMAP <Linux-omap-open-source@linux.omap.com>
Subject: Re: Bug? - OSK Frame Buffer Support in Kernel 2.6.18-omap1
Date: Fri, 06 Oct 2006 12:43:35 +0200 [thread overview]
Message-ID: <45263357.7090700@gmail.com> (raw)
In-Reply-To: <CC7B089C59ED6841BAE28F1EA69A854387372B@EXCHDB.admin.wpi.edu>
Sideleau, Scott R wrote:
> When trying to build the 2.6.18-omap1 kernel with the frame buffer support
> option for the OSK selected, the build fails while trying to compile
> ".../drivers/video/omap/omapfb_main.c" with numerous errors.
>
> I selected frame buffer support as shown at the "OSK for Dummies" web site
> (albeit without the "OMAP internal LCD controller support" option checked as
> it apparently no longer exists)...
>
> http://oskfordummies.hp.infoseek.co.jp/howto/lcd.html
>
> Has anyone successfully built the 2.6.18-omap1 kernel with frame buffer
> support?
With patch I sent some minutes ago most recent git works for
me on OSK with frame buffer and Mistral LCD.
Do you use recent git? What are your errors?
I use
CONFIG_OMAP_OSK_MISTRAL=y
CONFIG_VIDEO_V4L2=y
CONFIG_FB=y
CONFIG_FB_MODE_HELPERS=y
CONFIG_FB_OMAP=y
CONFIG_FB_OMAP_CONSISTENT_DMA_SIZE=2
CONFIG_FB_OMAP_DMA_TUNE=y
Cheers
Dirk
next prev parent reply other threads:[~2006-10-06 10:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-06 9:58 [PATCH] ARM: OMAP: Make OMAP1 work again Dirk Behme
2006-10-06 10:21 ` Bug? - OSK Frame Buffer Support in Kernel 2.6.18-omap1 Sideleau, Scott R
2006-10-06 10:43 ` Dirk Behme [this message]
2006-10-06 16:13 ` Sideleau, Scott R
2006-10-06 19:05 ` Can't Boot " Sideleau, Scott R
2006-10-06 19:30 ` Dirk Behme
2006-10-06 12:49 ` [PATCH] ARM: OMAP: Make OMAP1 work again Tony Lindgren
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=45263357.7090700@gmail.com \
--to=dirk.behme@googlemail.com \
--cc=Linux-omap-open-source@linux.omap.com \
--cc=srs@WPI.EDU \
/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.