nanogui: Thread: Problems with ioctl_getpalette() and ioctl_setpalette()


[<<] [<] Page 1 of 1 [>] [>>]
Subject: Problems with ioctl_getpalette() and ioctl_setpalette()
From: David Douthitt ####@####.####
Date: 29 Jun 2001 17:40:24 -0000
Message-Id: <3B3CAF74.E3887D0B@mailbag.com>

I figured the problem.... but the solution is beyond me.

The definition to the ioctl_getpalette() and ioctl_setpalette()
functions are in fb.h (prototypes) and scr_fb.c; however, if one is
using SVGAlib (as I am trying to do) then these are not used, and thus
the functions are never defined, even though they are used in
kbd_ttyscan.c and vtswitch.c.

My "fix" has been to remove calls to these functions, but that's not the
real answer I suspect.
Subject: Re: [nanogui] Problems with ioctl_getpalette() and ioctl_setpalette()
From: Jordan Crouse ####@####.####
Date: 29 Jun 2001 18:06:48 -0000
Message-Id: <01062912075209.25408@cosmic>

If you are running with the SVGAlib, you probably don't care about VT 
switching as much as the framebuffer users do, so if you just define VTSWITCH 
to be N in the config, then you should eliminate most of your problems.

Or, if you *do* care about VT switching, then define your own versions of the 
two calls for the SVGAlib and use them instead.

Jordan

On Friday 29 June 2001 10:40, David Douthitt mentioned:
> I figured the problem.... but the solution is beyond me.
>
> The definition to the ioctl_getpalette() and ioctl_setpalette()
> functions are in fb.h (prototypes) and scr_fb.c; however, if one is
> using SVGAlib (as I am trying to do) then these are not used, and thus
> the functions are never defined, even though they are used in
> kbd_ttyscan.c and vtswitch.c.
>
> My "fix" has been to remove calls to these functions, but that's not the
> real answer I suspect.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
[<<] [<] Page 1 of 1 [>] [>>]


Powered by ezmlm-browse 0.20.