Christian Gmeiner wrote:
I did some more research and came up with the following idea/plan:
- search for valid edid binary blob (maybe this can be done with cbfs
from coreboot)
- extend vgasrc/geodevga.c to make use of edid information's
- extend vgasrc/vbe.c to support edid calls (104f15)
What do you think?
I think it sounds good, but perhaps also consider storing the edid not in binary but in a format easier to work with, like text?
//Peter
I did some more research and came up with the following idea/plan:
- search for valid edid binary blob (maybe this can be done with cbfs
from coreboot)
- extend vgasrc/geodevga.c to make use of edid information's
- extend vgasrc/vbe.c to support edid calls (104f15)
What do you think?
I think it sounds good, but perhaps also consider storing the edid not in binary but in a format easier to work with, like text?
Lets see how I proceed :)
As I have never done any BIOS interrupt programming I run into the following issue:
http://nopaste.info/2b38ef0a54.html
As far as I understood this sub interrupt I need to copy/fill in the edid data to the pointer provided via es/edi. But I am not really sure how to do it :/
thanks -- Christian Gmeiner, MSc
-
Christian Gmeiner -
Peter Stuge