Date: Wed, 05 May 1999 12:01:16 -0700 From: Mike Smith <mike@smith.net.au> To: CyberPsychotic <fygrave@tigerteam.net> Cc: Doug Rabson <dfr@nlsystems.com>, freebsd-hackers@freebsd.org, tech@openbsd.org Subject: Re: io ports reading/writing Message-ID: <199905051901.MAA01404@dingo.cdrom.com> In-Reply-To: Your message of "Wed, 05 May 1999 14:01:44 %2B0500." <Pine.GSO.4.05.9905051359030.632-100000@kyrnet.kg>
next in thread | previous in thread | raw e-mail | index | archive | help
> ~ > ~ The access control for io ports is controlled by the file-system > ~ permissions on /dev/io. In a standard setup, only root can access this > ~ device. > ~ > > yes. But I was refering to linux scheme, where you can set the port-range, > so the code wouldn't make any unintentional damage. (like if you're working > with cmos you could only permit 0x70/0x71 ports, so even if code goes nuts, > your disks will be safe). This is basically programmer's problem of course, > but the feature is very handy. Try i386_get_ioperm/i386_set_ioperm -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199905051901.MAA01404>