minix

History

Lionel Sambuc 43d985050c Use one message type for all BDEV request. There are missing field assignements, and/or messsages being re-used without re-initializations, which allows for fields to be implicitly forwarded. This prevents me from creating per request message types, as I can't spend currently any more time debugging this issue.		2014-07-28 17:06:28 +02:00
..
arch/earm	libchardriver: full API rewrite	2014-03-01 09:04:50 +01:00
fb.c	libchardriver: full API rewrite	2014-03-01 09:04:50 +01:00
fb.h	libchardriver: full API rewrite	2014-03-01 09:04:50 +01:00
fb_edid.c	Use one message type for all BDEV request.	2014-07-28 17:06:28 +02:00
fb_edid.h	fb: auto-configure with EDID	2013-08-11 20:37:16 +02:00
logos.h	fb: introduce framebuffer support to Minix	2013-02-21 10:29:08 +00:00
Makefile	fb: auto-configure with EDID	2013-08-11 20:37:16 +02:00
README.txt	fb: auto-configure with EDID	2013-08-11 20:37:16 +02:00

README.txt

Frame Buffer Driver
===================

Overview
--------

This is the driver for the frame buffer. Currently it only supports the
DM37XX (BeagleBoard-xM).

Testing the Code
----------------

Starting up an instance:

service up /usr/sbin/fb -dev /dev/fb0 -args edid.0=cat24c256.3.50

The arguments take the following form:

	edid.X=L where X is the frame buffer device (usually 0) and L is
	the service label of the service to perform the EDID reading. In
	the example above, it's the EEPROM with slave address 0x50 on
	the 3rd I2C bus. If you want to use the defaults and skip EDID
	reading, you may omit the arguments.