> > But what is missing to call the VESA bios is the ability to mmap > > 0xA000--0xFFFF > > physically into the address space of the team. Don't know if this > > is > > aready > > possible... > > I guess you mean identity mapped, right? It should be possible to do > this by mapping the memory in the kernel via map_physical_memory(), > and > then clone that area in userland using B_EXACT_ADDRESS. > Right, though we can also just do it from a kernel thread from a driver, as we don't really use it appart from vesa... Unless we want to play with virtualization stuff but vm86 is probably deprecated for that anyway. François.