genfb(4) [netbsd man page]

GENFB(4)						   BSD Kernel Interfaces Manual 						  GENFB(4)

NAME

     genfb -- generic framebuffer console driver

SYNOPSIS

     genfb* at pci?
     genfb* at sbus?
     wsdisplay* at genfb?

DESCRIPTION

     The genfb driver provides support for generic framebuffers that have no native driver.  All it needs are some parameters to describe the
     framebuffer and an address.

   PCI
     When attaching to a pci(4) bus the driver is configured via device properties:

     width (uint32)
		   Width in pixels.

     height (uint32)
		   Height in pixels.

     stride (uint32)
		   Line size in bytes.

     depth (uint32)
		   Bits per pixel.

     is_console (bool)
		   If true, genfb will try to become the system console.

     address (uint32)
		   Bus address of the framebuffer.

   SBus
     When attaching to sbus(4) all those parameters are retrieved from the firmware.

SEE ALSO

     pci(4), sbus(4), wscons(4), wsdisplay(4)

BUGS

     There is no way to change the color map even when the firmware supports it.  The pci(4) bus frontend has only been tested on macppc, i386,
     and amd64 and requires machine dependent code to pass the properties mentioned above.  So far only macppc, i386, and amd64 provides them.

BSD
								  August 23, 2009							       BSD

IEEE1394IF(4)						   BSD Kernel Interfaces Manual 					     IEEE1394IF(4)

NAME

     ieee1394if -- IEEE1394 High-performance Serial Bus

SYNOPSIS

     ieee1394if* at fwohci?

DESCRIPTION

     NetBSD provides machine-independent bus support and raw drivers for IEEE1394 interfaces.

     The ieee1394if driver consists of two layers: the controller and the bus layer.  The controller attaches to a physical bus (like pci(4)).
     The ieee1394if bus attaches to the controller.  Additional drivers can be attached to the bus.

     Up to 63 devices, including the host itself, can be attached to a IEEE1394 bus.  The root node is dynamically assigned with a PHY device
     function.	Also, the other IEEE1394 bus specific parameters, e.g., node ID, cycle master, isochronous resource manager and bus manager, are
     dynamically assigned, after bus reset is initiated.  On the ieee1394if bus, every device is identified by an EUI 64 address.

FILES

     /dev/fw0.0
     /dev/fwmem0.0

SEE ALSO

     fwip(4), fwohci(4), pci(4), sbp(4), fwctl(8), sysctl(8)

HISTORY

     The ieee1394if driver first appeared in FreeBSD 5.0, as firewire.	It was added to NetBSD 4.0 under its present name.

AUTHORS

     The ieee1394if driver was written by Katsushi Kobayashi and Hidetoshi Shimokawa for the FreeBSD project.  It was added to NetBSD 4.0 by
     KIYOHARA Takashi.

BUGS

     See fwohci(4) for security notes.

BSD
								   June 18, 2005							       BSD