Ronald G Minnich wrote:
> cirrusfb is fixed as of 2.4 release.
>
> This stuff is going to get fixed over time.
>
> I think I know how to think about this. Linux knows how to turn chipsets
> on. linux doesn't know mainboard details. So, linuxbios needs to fix
> things that are mainboard-specific, and linux does the rest.
>
> example: motherboard with both via vt82c686a south and a superio.
> Linuxbios has to know which pieces of which part to turn on, since the 686
> has some superio functions.
>
> example: motherboard with two superios. Linuxbios will probably have to
> know which pieces of which superios to turn on, since linux will not.
>
> So, I'm going to try to figure out an API for BOTH config tool AND C.
>
> Configtool might be something like
>
> superio ITD/it1235 serial, mouse
> superio via/vt82c686a flash, ide
>
> so I extend superio syntax to say what bits of the superio matter. Then I
> can generate code to call the right pieces.
>
> comments?
>
> ron
I'm sorry if this is already what's being done, i suppose I should
read more code before commenting, but I think this includes some
new material.
I've been thinking about a more fine grained config, and "macros"
that contain settings for common configs;
The reason being that this could account for "glue logic" changes
between different motherboards, and allow embedded people
who have specific knowledge (ie schematics) to accommodate
their nonstandard hardware very easily.
For instance, the PIIX4 has a number of pins which have different
functions GPIO vs X that depend on where it's wired to.
SO the PIIX4 code should be generic, and include a config .h
At the same time another chip, say keyboard controller,
is written the same way, and includes config.
Then, the above syntax (doesn't fit my example so just pretend)
superio ITD/it1235 serial, mouse
superio via/vt82c686a flash, ide
would tie the two together by pointing the rom chip select output
of the via at the flash, the console serial code at the it1235, etc.
it would require a lot of redundant config options (since they
many are ALWAYS used a certain way) for pc motherboards,
but would be extremely powerful for embedded and mods to
pc mb's (i remember a post where someone was selecting
rom images with toggle switch) or how about a kit to
implement /dev/initctl on unused flopy port?
you would just mindlessly code each chip from the spec sheet,
making a config option for each multi-purpose pin, then
string the chips together in config macro
