linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Elgin Lee <ehl@funghi.com>
To: "David A. Gatwood" <marsmail@globegate.utm.edu>
Cc: Elgin Lee <ehl@funghi.com>,
	Geert Uytterhoeven <Geert.Uytterhoeven@cs.kuleuven.ac.be>,
	linuxppc-dev@lists.linuxppc.org
Subject: Re: XF68_FBDev under MkLinux?
Date: Sun, 06 Dec 1998 22:33:21 -0800	[thread overview]
Message-ID: <199812070633.WAA00979@porcini.funghi.com> (raw)
In-Reply-To: Message from "David A. Gatwood" <marsmail@globegate.utm.edu> of "Sun, 06 Dec 1998 19:18:18 CST." <Pine.LNX.3.96.981206190751.2542E-100000@globegate.utm.edu>


>>>>> In <Pine.LNX.3.96.981206190751.2542E-100000@globegate.utm.edu> 
>>>>>	"David A. Gatwood" <marsmail@globegate.utm.edu> wrote:

> > >   1. Add frame buffer devices to MkLinux. This requires many kernel
> > >      changes to MkLinux and forces people to upgrade their kernel.
> 
> This would be a better long-term solution, though I would find it more
> palatable to add an FB-style interface to the existing drivers, adding
> whatever additional functionality is necessary rather than dumping the
> existing drivers (since switching to the LinuxPPC drivers would probably
> mean dropping x100 support, or else rewriting those drivers from scratch). 
> Note that this is a couple of notches down in priority for me (as far as
> my time goes), but anyone else interested in working on it can feel free.

Well, I've considered porting the Linux 2.1 framebuffer devices as
part of the current work on porting the gnumach Linux device driver
support to the OSF Mach kernel used by MkLinux.  However, the gnumach
code currently supports only block and network devices, and adding the
video support currently isn't on my personal priority list.  (Porting
MkLinux to Linux 2.1 seems higher priority...)

So, pragmatically, choice #2 still seems more feasible in the short
term.  In the long term, I agree that choice #1 would be better.

--Elgin




[[ 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-07  6:33 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 [this message]
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=199812070633.WAA00979@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).