On Mon, Oct 01, 2001 at 05:12:17PM -0400, Roland McGrath wrote: > I believe that everything should already be in place in Mach (both flavors) > and in the Hurd for mapping physical device memory such as the frame buffer. > mmap on /dev/mem ought to dtrt already. If not, it's a bug. > > The only reason to have a more specific device for this is security, > e.g. /dev/vga that can mmap only a constrained range. We can do this by > Hurdish means if we ever care to. Theoretically one could use a remap > store on top of /dev/mem, whos runs give mostly holes and only map the > address ranges you want to allow for the frame buffer.
Yes, this is much better than frobbing mach devices directly. I include a patch for colortext below, maybe somebody wants to try that. There is another issue I didn't mention... colortext pokes io ports to set the cursor position. There is a bug report against gnumach which allows all tasks to write to io ports. If I read oskit/x86/main.c correctly, requesting access to ioports is not implemented yet, but will it allow all accesses like GNU Mach or none at all? Thanks, Marcus -- `Rhubarb is no Egyptian god.' Debian http://www.debian.org [EMAIL PROTECTED] Marcus Brinkmann GNU http://www.gnu.org [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.marcus-brinkmann.de _______________________________________________ Bug-hurd mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-hurd
