minix

History

David van Moolenbroek 113635b019 Block protocol: use own [RW]_BIT definitions The original R_BIT and W_BIT definitions have nothing to do with the way these bits are used. Their distinct usage is more apparent when they have different names. Change-Id: Ia984457f900078b2e3502ceed565fead4e5bb965		2014-02-19 11:22:15 +01:00
..
arch/earm	fb: auto-configure with EDID	2013-08-11 20:37:16 +02:00
fb.c	Retire the synchronous character driver protocol	2014-02-18 11:25:02 +01:00
fb.h	fb: auto-configure with EDID	2013-08-11 20:37:16 +02:00
fb_edid.c	Block protocol: use own [RW]_BIT definitions	2014-02-19 11:22:15 +01: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.