> > As far a final solution goes, I don't think Linus will want the
> > kernel to have to support an 8Kb I/O permission bitmap for every
> > task just so we can call the BIOS effectively.
>
> There was a brief discussion a few months ago on ways to give processes
> that need it a full 8k I/O bitmap, using VM hacks. It came about as a
> result of attempts to speed up fork() & clone(). Linus didn't like it.
>
> I would also find this quite useful. I've been programming a PCI card
> from user space, and the I/O addresses are high enough that I have to
> use iopl(3).
So what can we do to make this happen? I am not familiar with the
processes involved in getting something accepted into the kernel, so
if we come up with some mechanism to make this happen?
Linus, do you have any opinions to share on this topic?
Regards,
+--------------------------------------------------------------------------+
| SciTech Software - Building Truly Plug'n'Play Software! |
+--------------------------------------------------------------------------+
| Kendall Bennett | Email: KendallB@scitechsoft.com |
| Director of Engineering | Phone: (530) 894 8400 |
| SciTech Software, Inc. | Fax : (530) 894 9069 |
| 505 Wall Street | ftp : ftp.scitechsoft.com |
| Chico, CA 95928, USA | www : http://www.scitechsoft.com |
+--------------------------------------------------------------------------+
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html