.\" This manpage has been automatically generated by docbook2man 
.\" from a DocBook document.  This tool can be found at:
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/> 
.\" Please send any bug reports, improvements, comments, patches, 
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "S1D13XXXFB_FETCH_HW_STATE" "9" "09 October 2005" "" ""

.SH NAME
s1d13xxxfb_fetch_hw_state \- Configure the framebuffer according to
.SH SYNOPSIS
"SYNOPSIS"
.sp
\fB
.sp
void __devinit s1d13xxxfb_fetch_hw_state  (struct fb_info * \fIinfo\fB);
\fR
.SH "ARGUMENTS"
.TP
\fB\fIinfo\fB\fR
frame buffer structure
.SH "DESCRIPTION"
.PP
We setup the framebuffer structures according to the current
hardware setup. On some machines, the BIOS will have filled
the chip registers with such info, on others, these values will
have been written in some init procedure. In any case, the
software values needs to match the hardware ones. This is what
this function ensures.
.SH "DESCRIPTION"
.PP
We setup the framebuffer structures according to the current
hardware setup. On some machines, the BIOS will have filled
the chip registers with such info, on others, these values will
have been written in some init procedure. In any case, the
software values needs to match the hardware ones. This is what
this function ensures.
.SH "NOTE"
.PP
some of the hardcoded values here might need some love to
work on various chips, and might need to no longer be hardcoded.