linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Questions about fbdriver integration
Date: Sun, 25 Nov 2007 09:49:31 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.64.0711250947380.21779@anakin> (raw)
In-Reply-To: <20071124214325.GD3183@pruts.nl>

On Sat, 24 Nov 2007, Ico Doornekamp wrote:
> I have just finished writing a framebuffer driver for a LCD display
> connected to our embedded system (monochrome, 128x64, GPIO driven).
> It's very similar to the hecubafb driver, and uses deferred IO. I've
> included some of the drivers properties at the end of this mail.  Things
> works fine when displaying images by doing write()s to /dev/fb0, so this
> part seems to be ok.
> 
> I hope some of the regulars on this list can clear up some issues
> I've run into when using this driver:
> 
> - My next step as to redirect the linux console to this framebuffer
>   device. I've configured the kernel for framebuffer console, and when
>   loading the fbcon module, the message 
>     
>      Console: switching to mono frame buffer device 16x4" 
>      
>   appears, and
> 
>      cat /sys/class/vtconsole/vtcon1/name -> (M) frame buffer device
>      cat /sys/class/vtconsole/vtcon1/bind -> 1
>   
>   This seems just fine to me, but however, no output appears on the
>   display: just a blank screen. 
> 
>   It seems that the console is doing *something*, since my driver gets
>   triggered by the deferred IO every 200msec (blinking cursor?), problem
>   is that the data arriving in my driver is all zeroes!

Fbcon writes to the memory at fb_info.screen_base.

> - The other question is more a userspace issue: I was hoping to use the
>   xorg fbdev server on my dislay, but unfortunately this does not seem
>   to support 1 bit depth displays :
> 
>     (EE) FBDEV(0): unsupported number of bits per pixel: 1
> 
>   Is there a way to make X work on 1-bit fb devices, or am I out of luck
>   here ?

The old XF86_FBDev (from XFree86 3.x) definitely works with monochrome.
I expect (but never tried) KDrive also to support it.

It's a pity many frame buffer organizations were dropped in Xorg.

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

  parent reply	other threads:[~2007-11-25  8:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-24 21:43 Questions about fbdriver integration Ico Doornekamp
2007-11-24 22:09 ` Ico Doornekamp
2007-11-24 22:14 ` Ico Doornekamp
2007-11-24 22:49   ` Jaya Kumar
2007-11-25  9:05     ` Ico Doornekamp
2007-11-25 10:48       ` Jaya Kumar
2007-11-25 10:53         ` Ico Doornekamp
2007-11-25 11:12           ` Jaya Kumar
2007-11-25 11:21             ` Ico Doornekamp
2007-11-28 11:40         ` Ico Doornekamp
2007-11-28 13:00           ` Jaya Kumar
2007-11-28 13:11             ` Jaya Kumar
2007-11-28 13:21               ` Ico Doornekamp
2007-11-25  8:49 ` Geert Uytterhoeven [this message]
2007-11-25 10:51   ` Ico Doornekamp
2007-11-25 12:51     ` Ico Doornekamp
2007-11-25 13:32       ` Questions about fbdriver integration (solved) Ico Doornekamp
2007-11-25 22:17         ` Geert Uytterhoeven

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=Pine.LNX.4.64.0711250947380.21779@anakin \
    --to=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).