legacy vga ... what do you think?
rminnich at lanl.gov
Thu Jan 15 17:50:00 CET 2004
On 15 Jan 2004, Eric W. Biederman wrote:
> ron minnich <rminnich at lanl.gov> writes:
> > On 14 Jan 2004, Eric W. Biederman wrote:
> > > Yes but you should not need to know which device it is.
> > > Looking at the code though there is a bug. When it finds a device
> > > to give the legacy vga resources to it does not allocate any MMIO
> > > resources. For bridges this is a normal resource so this looks
> > > a real bug in the generic code. If that is why you need
> > > the vgadev, let's fix the generic code to handle that part properly.
> > yes, that's the bug. I waffled between a generic fix and the simple fix I
> > outlined, but if you want the generic fix we can look at that too.
> Please. Mostly it requires finding the vga card first and giving it
> the appropriate resource, in a format the resource allocator can
> This is a subset of a more general case that working on the superio code
> made me realize needs to be done. Ultimately we need to make a scan
> of devices with known programming interfaces and to assign them legacy
> resources. serial ports, parallel ports, ide, etc. But vga is a
> good first small step.
The second problem is that the PCIO is not correctly set up for legacy vga
either. OK, we'll look.
More information about the coreboot