Ronald G Minnich <[EMAIL PROTECTED]> writes:
> 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.
I agree up to a point. linuxbios needs to deal with mainboard
specific details. At the minimum linuxbios needs to tell the
kernel mainboard specific details, and I would like to explore to see
if this is possible. As opposed to doing all of the setup ourselves.
> 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?
Sounds like the practical direction for now. I'm going to continue to
be impractical for a while longer and see if there is a good way to
tell the kernel what is going on.
I know windows can do it. I saw it last week. So I'm going to keep
digging.
But it does start to clearly define the line of where linuxBIOS stops.
mainboard specific: linuxBIOS, everthing else: linux
Eric
