On Fri, Jan 17, 2014 at 04:50:27PM -0800, Stefan Reinauer wrote:
Yes, I think it's worth having them in upstream SeaBIOS!
I've been thinking about creating a way of passing this information between coreboot and SeaBIOS in the future, so we don't have to keep the handlers around twice. One way of doing that would be to have the handler live in SMM and have SeaBIOS do an SMI command to get the right answers. Would you be open to something like that?
That seems over kill to me. The Intel VGA stuff seems to be pretty stable and it's only a few fields that need to be passed back. What about placing the required info in a coreboot table - then SeaBIOS can just pass back the desired fields and not have to have board by board specific logic.
BTW, I didn't port over "Alex" as it seems to be totally different from the other boards.
-Kevin
On Fri, Jan 17, 2014 at 4:56 PM, Kevin O'Connor kevin@koconnor.net wrote:
On Fri, Jan 17, 2014 at 04:50:27PM -0800, Stefan Reinauer wrote:
Yes, I think it's worth having them in upstream SeaBIOS!
I've been thinking about creating a way of passing this information
between
coreboot and SeaBIOS in the future, so we don't have to keep the handlers around twice. One way of doing that would be to have the handler live in SMM and have SeaBIOS do an SMI command to get the right answers. Would
you
be open to something like that?
That seems over kill to me. The Intel VGA stuff seems to be pretty stable and it's only a few fields that need to be passed back. What about placing the required info in a coreboot table - then SeaBIOS can just pass back the desired fields and not have to have board by board specific logic.
Ok.. Let's see how this goes for future boards. I think that could work
BTW, I didn't port over "Alex" as it seems to be totally different from the other boards.
Great. Alex was an old Atom system that was never shipped with coreboot