From: Elgin Lee <ehl@funghi.com>
To: Geert Uytterhoeven <Geert.Uytterhoeven@cs.kuleuven.ac.be>
Cc: "David A. Gatwood" <marsmail@globegate.utm.edu>,
Elgin Lee <ehl@funghi.com>,
linuxppc-dev@lists.linuxppc.org
Subject: Re: XF68_FBDev under MkLinux?
Date: Mon, 07 Dec 1998 10:22:46 -0800 [thread overview]
Message-ID: <199812071822.KAA02538@porcini.funghi.com> (raw)
In-Reply-To: Message from "David A. Gatwood" <marsmail@globegate.utm.edu> of "Mon, 07 Dec 1998 11:46:40 CST." <Pine.LNX.3.96.981207114602.20658A-100000@globegate.utm.edu>
Geert--
Perhaps I misunderstand. What ioctls are you proposing to use?
MkLinux (Linux and Mach sides combined) supports ioctls like
VC_GETMODE, VC_SETMODE, VC_INQMODE, VC_SETCMAP, and VC_GETCMAP.
However, I believe that the Mach drivers will currently only allow you
to use the one video mode (width, height, depth, etc.) in effect from
the MacOS side. That one mode should be revealed by the video ioctls.
Would that restriction cause a problem?
--Elgin
>>>>> In <Pine.LNX.3.96.981207114602.20658A-100000@globegate.utm.edu>
>>>>> "David A. Gatwood" <marsmail@globegate.utm.edu> wrote:
> On Mon, 7 Dec 1998, Geert Uytterhoeven wrote:
>
> > On Sun, 6 Dec 1998, David A. Gatwood wrote:
> > > On Sat, 5 Dec 1998, Elgin Lee wrote:
> > > > > 2. Adopt XF68_FBdev so it can use the MkLinux video mode ioctl stuff.
> > >
> > > vmode ioctl stuff? Since when does MkLinux support detecting or changing
> > > video modes? This is where we're going to run into trouble either way.
> >
> > Doesn't the stuff in <asm/vc_ioctl.h> come from MkLinux?
>
> Maybe. I'm not saying the linux server part doesn't have the support,
> just that the mach kernel drivers don't, AFAIK. :-)
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
next prev parent reply other threads:[~1998-12-07 18:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <geert@geert.cs.kuleuven.ac.be>
[not found] ` <Pine.LNX.4.02.9812052310580.864-100000@cassiopeia.home>
1998-12-06 1:54 ` XF68_FBDev under MkLinux? Elgin Lee
1998-12-06 15:12 ` Geert Uytterhoeven
1998-12-07 1:18 ` David A. Gatwood
1998-12-07 6:33 ` Elgin Lee
1998-12-07 8:58 ` Geert Uytterhoeven
1998-12-07 17:16 ` Elgin Lee
1998-12-07 17:46 ` David A. Gatwood
1998-12-07 18:22 ` Elgin Lee [this message]
1998-12-07 20:06 ` Geert Uytterhoeven
1998-12-08 1:03 ` status of multiprocessor support? Wesley Horner
1998-12-09 7:23 ` Troy Benjegerdes
1998-12-08 0:46 ` XF68_FBDev under MkLinux? anthony tong
1998-12-08 17:57 ` Ryuichi Oikawa
1998-12-06 5:12 ` anthony tong
1998-12-06 16:40 ` Ryuichi Oikawa
1998-12-07 10:28 ` Geert Uytterhoeven
1998-12-07 15:20 ` XF68_FBDev nathan ingersoll
1998-12-06 6:11 ` XF68_FBDev under MkLinux? Tom Rini
1998-12-06 7:26 ` Martin Costabel
1998-12-06 15:13 ` Geert Uytterhoeven
1998-12-07 13:57 ` Kohkichi Hosoda
1998-12-07 13:15 Martin Costabel
1998-12-07 13:56 ` Geert Uytterhoeven
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199812071822.KAA02538@porcini.funghi.com \
--to=ehl@funghi.com \
--cc=Geert.Uytterhoeven@cs.kuleuven.ac.be \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=marsmail@globegate.utm.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).