linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Elgin Lee <ehl@funghi.com>
To: Geert Uytterhoeven <Geert.Uytterhoeven@cs.kuleuven.ac.be>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: XF68_FBDev under MkLinux?
Date: Sat, 05 Dec 1998 17:54:14 -0800	[thread overview]
Message-ID: <199812060154.RAA01357@porcini.funghi.com> (raw)
In-Reply-To: Message from Geert Uytterhoeven <geert@geert.cs.kuleuven.ac.be> of "Sat, 05 Dec 1998 23:20:33 +0100." <Pine.LNX.4.02.9812052310580.864-100000@cassiopeia.home>


Geert--

Recent (non-official) MkLinux kernels support /dev/adbmouse (busmouse
emulation).  GPM works with it, so I suspect that XF68_FBdev would as
well.  Choice #2 does seem the least amount of work.

One question--would acceleration would still require framebuffer
devices?

--Elgin

>>>>> In <Pine.LNX.4.02.9812052310580.864-100000@cassiopeia.home> 
>>>>>	Geert Uytterhoeven <geert@geert.cs.kuleuven.ac.be> wrote:

> 
> 
> To reduce development efforts, it may be better to start using XF68_FBdev under
> MkLinux too. That way plain XFree86 will work on both MkLinux/PPC and
> Linux/PPC.
> 
> I see two solutions:
> 
>   1. Add frame buffer devices to MkLinux. This requires many kernel changes to
>      MkLinux and forces people to upgrade their kernel.
> 
>   2. Adopt XF68_FBdev so it can use the MkLinux video mode ioctl stuff. This
>      requires no kernel changes. In XF68_FBDev, the video ioctl and mmap stuff
>      has to be changed slightly.
> 
> I think the second solution is the least amount of work.
> 
> Another thing is keyboard and mouse (ADB) handling. Xpmac uses the plain
> /dev/adb device, while XF68_FBDev takes the standard Linux keyboard input and
> uses the adbmouse driver. I assume keyboard won't be a problem. But the mouse
> requires the adbmouse driver.

[[ 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 ]]

       reply	other threads:[~1998-12-06  1:54 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   ` Elgin Lee [this message]
1998-12-06 15:12     ` XF68_FBDev under MkLinux? 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
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=199812060154.RAA01357@porcini.funghi.com \
    --to=ehl@funghi.com \
    --cc=Geert.Uytterhoeven@cs.kuleuven.ac.be \
    --cc=linuxppc-dev@lists.linuxppc.org \
    /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).