olafbuddenha...@gmx.net, le Mon 15 Mar 2010 03:24:08 +0100, a écrit :
> I think this man page is simply outdated.
Mmm, indeed, even 2.6.12 has it up to 2^16. But 2.4.36 has it up to 2^10
only.
Samuel
Hi,
On Sat, Mar 13, 2010 at 02:37:36AM +0100, Jérémie Koenig wrote:
> I think you're right, but apparently ioperm fails at least in my
> setting (the manual page seems to indicate it can only be used for the
> first 0x400 ports on Linux).
I think this man page is simply outdated. Though I couldn
Jérémie Koenig, le Fri 12 Mar 2010 10:44:13 +0100, a écrit :
> The culprit is xf86EnableIO() in hw/xfree86/os-support/hurd/hurd_video.c:
>
> Bool
> xf86EnableIO()
> {
> if (ioperm(0, 0x1, 1)) {
> FatalError("xf86EnableIO: ioperm() failed (%s)\n", strerror(errno));
> return
Jérémie Koenig, le Sat 13 Mar 2010 12:47:26 +0100, a écrit :
> On Sat, Mar 13, 2010 at 12:15 PM, Samuel Thibault
> wrote:
> > Jérémie Koenig, le Sat 13 Mar 2010 02:37:36 +0100, a écrit :
> >> (the manual page seems to indicate it can only be used for the
> >> first 0x400 ports on Linux).
> >
> > Y
On Sat, Mar 13, 2010 at 12:15 PM, Samuel Thibault
wrote:
> Jérémie Koenig, le Sat 13 Mar 2010 02:37:36 +0100, a écrit :
>> (the manual page seems to indicate it can only be used for the
>> first 0x400 ports on Linux).
>
> Yes, but that's precisely what Xorg uses :)
Ah, right, it does both... At f
Jérémie Koenig, le Sat 13 Mar 2010 02:37:36 +0100, a écrit :
> On Fri, Mar 12, 2010 at 8:29 PM, Samuel Thibault
> wrote:
> > Jérémie Koenig, le Fri 12 Mar 2010 19:54:31 +0100, a écrit :
> >> The vesa driver works on Linux, but gains access to the io ports
> >> through iopl(3),
> >
> > Ah, right, i
On Fri, Mar 12, 2010 at 8:29 PM, Samuel Thibault
wrote:
> Jérémie Koenig, le Fri 12 Mar 2010 19:54:31 +0100, a écrit :
>> The vesa driver works on Linux, but gains access to the io ports
>> through iopl(3),
>
> Ah, right, it does both... At first read I thought it was doing iopl()
> only if ioperm
Jérémie Koenig, le Fri 12 Mar 2010 19:54:31 +0100, a écrit :
> On Fri, Mar 12, 2010 at 4:22 PM, Samuel Thibault
> wrote:
> > Jérémie Koenig, le Fri 12 Mar 2010 10:44:13 +0100, a écrit :
> >> Apparently the code in my card's BIOS needs access to both 0x40-0x43
> >> and 0x60-0x63: if I reenable them
On Fri, Mar 12, 2010 at 4:22 PM, Samuel Thibault
wrote:
> Jérémie Koenig, le Fri 12 Mar 2010 10:44:13 +0100, a écrit :
>> Apparently the code in my card's BIOS needs access to both 0x40-0x43
>> and 0x60-0x63: if I reenable them manually from within gdb the vesa
>> driver works.
>
> Mmm, you may wa
Jérémie Koenig, le Fri 12 Mar 2010 10:44:13 +0100, a écrit :
> Bool
> xf86EnableIO()
> {
> if (ioperm(0, 0x1, 1)) {
> FatalError("xf86EnableIO: ioperm() failed (%s)\n", strerror(errno));
> return FALSE;
> }
> ioperm(0x40,4,0); /* trap access to the timer chip */
>
2010/3/11 Jérémie Koenig :
> By the way, some other problems I have (I will investigate those further):
> * Using the VESA driver, the X server crashes with SIGILL. The
> backtrace shown suggests this happens in the int10 code.
The culprit is xf86EnableIO() in hw/xfree86/os-support/hurd/hurd_vide
11 matches
Mail list logo
