linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ico Doornekamp <fbdev@zevv.nl>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Xorg dies on my deferred I/O fb driver
Date: Wed, 17 Dec 2008 15:50:22 +0100	[thread overview]
Message-ID: <20081217145022.GM12994@pruts.nl> (raw)
In-Reply-To: <Pine.LNX.4.64.0812171515220.11971@anakin>



* On 2008-12-17 Geert Uytterhoeven <geert@linux-m68k.org> wrote  :

> On Wed, 17 Dec 2008, Ico Doornekamp wrote:
> > Today I wrote a simple framebuffer driver for a SPI driven LCD display
> > with internal memory, using the deferred I/O framework. The display is
> > capable of grayscale, 384x160 pixels.
> > 
> > My driver resembles the metronomefb driver, and seems to work using
> > write() and mmap() with my own test tools.
> > 
> > The next step would be to run Xorg/fbdev on top, but things don't seem
> > to simple work this way.
> > 
> > Xorg starts and detects te framebuffer driver, but dies with the message
> > 
> >   (EE) FBDEV(0): FBIOPUT_VSCREENINFO succeeded but modified mode
> >   (EE) FBDEV(0): mode initialization failed
> > 
> > I'm kind of stuck here. Any tips on how to solve or debug this one ?
> > 
> > On the bottom of this mail I pasted:
> > 
> > - fbinfo -i output
> > - Xorg log
> > - fb_fix_screeninfoa and fb_var_screeninfo from my driver
> > 
> > Running Xorg 1.4.2 on Linux 2.6.27.4
> 
> I guess your frame buffer device driver supports one single video mode only?

Indeed, good guess.

> There's a bug in Xorg that doesn't like drivers that support one
> single video mode only, and always return that single video mode in
> the FBIOPUT_VSCREENINFO ioctl (cfr. the "FBIOPUT_VSCREENINFO succeeded
> but modified mode" message).
> 
> One fix is to modify your frame buffer device driver to reject all
> modes that are not identical to the single supported mode.

Ok, that's the kind of hint I needed, I'll go steal some code from other
drivers right away.

Thanks,

Ico

-- 
:wq
^X^Cy^K^X^C^C^C^C

------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you.  Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/

  reply	other threads:[~2008-12-17 14:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-17 14:01 Xorg dies on my deferred I/O fb driver Ico Doornekamp
2008-12-17 14:18 ` Geert Uytterhoeven
2008-12-17 14:50   ` Ico Doornekamp [this message]
2008-12-17 16:35   ` Ico Doornekamp

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=20081217145022.GM12994@pruts.nl \
    --to=fbdev@zevv.nl \
    --cc=geert@linux-m68k.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).