Samuel Thibault wrote:
> Da Zheng, le Tue 04 Aug 2009 16:15:10 +0800, a écrit :
>> The driver reads the keyboard status from the port 0x64, and it seems OK. It
>> doesn't work when the driver tries to write the command to the port 0x64.
>> The whole process dies. (the port 0x64 is used for both r
Da Zheng, le Tue 04 Aug 2009 16:15:10 +0800, a écrit :
> The driver reads the keyboard status from the port 0x64, and it seems OK. It
> doesn't work when the driver tries to write the command to the port 0x64. The
> whole process dies. (the port 0x64 is used for both read the status and
> writin
Hi,
On Mon, Aug 03, 2009 at 07:12:22PM +0200, Thomas Schwinge wrote:
> There are two ways to use it: either the GNU Mach RPCs
> i386_io_perm_create and i386_io_perm_modify (see
> [gnumach]/i386/include/mach/i386/mach_i386.defs) can directly be used,
> or the more standard (at least on x86) glibc
Hi,
On Tue, Aug 11, 2009 at 11:58:42AM +0200, Thomas Schwinge wrote:
> On Sun, Aug 09, 2009 at 06:48:05PM +0200, olafbuddenha...@gmx.net
> wrote:
> But iopl is a all-or-nothing-like thing (all I/O ports),
I see...
I guess though that fixing that would still be easier than writing a
proper ioper
Hello!
On Sun, Aug 09, 2009 at 06:48:05PM +0200, olafbuddenha...@gmx.net wrote:
> On Mon, Aug 03, 2009 at 07:12:22PM +0200, Thomas Schwinge wrote:
> > There are two ways to use it: either the GNU Mach RPCs
> > i386_io_perm_create and i386_io_perm_modify (see
> > [gnumach]/i386/include/mach/i386/ma
Hi,
On Mon, Aug 03, 2009 at 07:12:22PM +0200, Thomas Schwinge wrote:
> There are two ways to use it: either the GNU Mach RPCs
> i386_io_perm_create and i386_io_perm_modify (see
> [gnumach]/i386/include/mach/i386/mach_i386.defs) can directly be used,
> or the more standard (at least on x86) glibc
Hello!
On Tue, Aug 04, 2009 at 04:15:10PM +0800, Da Zheng wrote:
> I am porting the keyboard driver to the user space and here is my problem:
> The driver reads the keyboard status from the port 0x64, and it seems
> OK. It doesn't work when the driver tries to write the command to the
> port 0x64.
Hello,
Thomas Schwinge wrote:
> No. ioperm is expected to work just fine, so please tell us if there are
> problems with it. There are two ways to use it: either the GNU Mach RPCs
> i386_io_perm_create and i386_io_perm_modify (see
> [gnumach]/i386/include/mach/i386/mach_i386.defs) can directly b
Hello!
On Mon, Aug 03, 2009 at 08:23:49PM +0800, Da Zheng wrote:
> There is some code in gnumach that implements ioperm, but it doesn't
> work. I think tschwinge has told me that. But could anyone tell why it
> doesn't work, how much work is left and when it will work?
No. ioperm is expected to
Hello,
There is some code in gnumach that implements ioperm, but it doesn't work. I
think tschwinge has told me that.
But could anyone tell why it doesn't work, how much work is left and when it
will work?
gnumach from the debian repository supports iopl. This gnumach provides an iopl
device a
10 matches
Mail list logo
