minix/drivers/fb
David van Moolenbroek 597151d963 libchardriver: full API rewrite
The new API now covers the entire character driver protocol, while
hiding all the message details. It should therefore be used by all
new character drivers. All existing drivers that already made use of
libchardriver have been changed to use the new API.

As one of the most important API changes, support for scatter and
gather transfers has been removed, as several key drivers already
did not support this, and it could be supported at the safecopy
level instead (for a future readv/writev).

Additional changes include:

- respond to block device open requests to avoid hanging VFS threads;
- add support for sef_cancel.

Change-Id: I1bab6c1cb66916c71b87aeb1db54a9bdf171fe6b
2014-03-01 09:04:50 +01: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 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

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.