> > Ok, thanks for explanation. I'll drop this patch and rebase the others. Cool, >> You won't be able to make this work for vga16fb from what I can see >> since it access 0xa000 directly, not via any of the defined apertures >> that vesafb/offb use. vga16fb will need a different approach I suspect. > > Yeah, there's an idea to claim 0xa0000 as an aperture of vga16fb and then > do the same in KMS driver but only if it's the primary card. > (You hinted to use SHADOW resource bit to check whether card is primary) > I think I'll try this approach soon. Yeah as long as we kick it off once, certain things like vga switcheroo change who the primary gpu is at runtime. but it should be okay if both drivers have the kickoff paths. Dave.
