Re: XF68_FBDev under MkLinux?

Re: XF68_FBDev under MkLinux?

[Elgin Lee]

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

Re: XF68_FBDev under MkLinux?

[Geert Uytterhoeven]

On Sat, 5 Dec 1998, Elgin Lee wrote:
> 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.

Nice.

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

No. Xpmac does it without frame buffer devices: it just mmap()s /dev/mem. All
that has to be changed is the interface to the frame buffer device API: instead
of asking the frame buffer device for address and size of frame buffer and MMIO
region, and mmap()ing that, something else has to be done.

One other thing to consider is video mode programming. XF68_FBDev uses
modelines (except for `mode "default"'), while Xpmac can take a vmode and cmode
argument. But I think this can be solved by putting the Modeline <->
vmode/cmode conversion routine in XF68_FBDev (cfr. drivers/video/macmodes.c).

And of course there won't be support for virtual screens, as the vmode/cmode
API doesn't provide for this.

Greetings,

						Geert

--
Geert Uytterhoeven                     Geert.Uytterhoeven@cs.kuleuven.ac.be
Wavelets, Linux/{m68k~Amiga,PPC~CHRP}  http://www.cs.kuleuven.ac.be/~geert/
Department of Computer Science -- Katholieke Universiteit Leuven -- Belgium



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

Re: XF68_FBDev under MkLinux?

[David A. Gatwood]

On Sat, 5 Dec 1998, Elgin Lee wrote:

> Recent (non-official) MkLinux kernels support /dev/adbmouse (busmouse

I wouldn't call them non-official... they're just non-Apple.  They're at
least somewhat sanctioned.  :-)


<snip>

> >   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.


> >   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.
This particular support code needs to be written.  In the process, it
would be logical to make it support both a framebuffer interface and the
traditional interface for compatibility with older vmlinux servers.

> >      This requires no kernel changes. In XF68_FBDev, the video ioctl
> >      and mmap stuff has to be changed slightly.

And the mach kernel has to have a small amount of code added to map that
physical space into the vmlinux server's address space, I believe, or
probably more like additional code in the vmlinux server to request it....
I'm not sure where the line is drawn... I'm still learning the
Mach/vmlinux io mapping stuff, the hard way... by coding something and
then poking around to see why it doesn't work.  :-)

Personally, I don't have any problem with requiring people to upgrade
their kernel for enhanced performance, though adding traditional ioctl
support for people who don't want to upgrade would be a nice touch.  With
the amount of kernel development happening right now, and the number of
bugs being fixed, people would be well advised to try to stay current if
they're using MkLinux anyway.  ;-)


Later,
David

David A. Gatwood                         Visit globegate's internet
dgatwood@globegate.utm.edu                  talker, Deep Space 36
http://globegate.utm.edu                telnet globegate.utm.edu:9624

-----BEGIN GEEK CODE BLOCK-----
Version 3.1
GCS/CC/FA/H/L/MC/M/MU/PA/TW d-@ s:>- a-- C++ ++>$ UBLAS*++ ++>$
P+?>$ L++ +>$ !E--- W++ +>$ N++(++ +)>++ +$ !o? K-? !w--- !O
M++>$ !V-- PS+>$ !PE- Y+>$ PGP+>$ t++ +>$ 5+>++ ++$ !X- !R tv+>$
b++>$ !DI !D- G++(++ +)>$ e>++ ++ h--! r--- !y-
------END GEEK CODE BLOCK------


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

Re: XF68_FBDev under MkLinux?

[Elgin Lee]

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

Re: XF68_FBDev under MkLinux?

[Geert Uytterhoeven]

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?

Greetings,

						Geert (who never ran MkLinux)

--
Geert Uytterhoeven                     Geert.Uytterhoeven@cs.kuleuven.ac.be
Wavelets, Linux/{m68k~Amiga,PPC~CHRP}  http://www.cs.kuleuven.ac.be/~geert/
Department of Computer Science -- Katholieke Universiteit Leuven -- Belgium


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

Re: XF68_FBDev under MkLinux?

[Elgin Lee]

>>>>> In <Pine.LNX.4.03.9812070957590.31794-100000@mercator.cs.kuleuven.ac.be> 
>>>>>	Geert Uytterhoeven <Geert.Uytterhoeven@cs.kuleuven.ac.be> 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?

Yes, MkLinux uses the VC_* ioctls.  I presume that's what you mean...

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

Re: XF68_FBDev under MkLinux?

[David A. Gatwood]

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.  :-)


Later,
David

David A. Gatwood                         Visit globegate's internet
dgatwood@globegate.utm.edu                  talker, Deep Space 36
http://globegate.utm.edu                telnet globegate.utm.edu:9624

-----BEGIN GEEK CODE BLOCK-----
Version 3.1
GCS/CC/FA/H/L/MC/M/MU/PA/TW d-@ s:>- a-- C++ ++>$ UBLAS*++ ++>$
P+?>$ L++ +>$ !E--- W++ +>$ N++(++ +)>++ +$ !o? K-? !w--- !O
M++>$ !V-- PS+>$ !PE- Y+>$ PGP+>$ t++ +>$ 5+>++ ++$ !X- !R tv+>$
b++>$ !DI !D- G++(++ +)>$ e>++ ++ h--! r--- !y-
------END GEEK CODE BLOCK------


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

Re: XF68_FBDev under MkLinux?

[Elgin Lee]

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

Re: XF68_FBDev under MkLinux?

[Geert Uytterhoeven]

On Mon, 7 Dec 1998, Elgin Lee wrote:
> 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.

These ioctls.

> 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?

No problem. That's very similar to `mode "default"' with XF68_FBDev.

> >>>>> 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.  :-)
> 

Greetings,

						Geert

--
Geert Uytterhoeven                     Geert.Uytterhoeven@cs.kuleuven.ac.be
Wavelets, Linux/{m68k~Amiga,PPC~CHRP}  http://www.cs.kuleuven.ac.be/~geert/
Department of Computer Science -- Katholieke Universiteit Leuven -- Belgium


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

status of multiprocessor support?

[Wesley Horner]

I am thinking about picking up a duel 604e/200 for Linuxppc and BeOS but I
am worried that BeOS will be the only one to see any benefit.  Has anybody
gotten linuxppc working on two processors yet.  If so what was required.

wes

~~~~wesman@gladstone.uoregon.edu~~~~~~~~~~NeXTMail OK!~~~~~~~~~~~~~~~~
Vax  a vicious creature known to eat 110AC and quotes through its 
*DCL*.  Vax are usually found in groups of Vaxen called clusters where 
they lay in wait to ravage thier prey known as users.



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

Re: status of multiprocessor support?

[Troy Benjegerdes]

On Mon, 7 Dec 1998, Wesley Horner wrote:

> 
> I am thinking about picking up a duel 604e/200 for Linuxppc and BeOS but I
> am worried that BeOS will be the only one to see any benefit.  Has anybody
> gotten linuxppc working on two processors yet.  If so what was required.

is this a Mac or some other board? I'll be working on SMP for the Motorola
MTX in a few weeks.

Mac SMP is partially/mostly supported, AFAIK

--------------------------------------------------------------------------
| Troy Benjegerdes    |    troybenj@iastate.edu    |    hozer@drgw.net   |
|    Unix is user friendly... You just have to be friendly to it first.  |
| This message composed with 100% free software.    http://www.gnu.org   |
--------------------------------------------------------------------------


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

Re: XF68_FBDev under MkLinux?

[anthony tong]

David A. Gatwood (Mon, Dec 07, 1998 at 11:46:40AM -0600):
> On Mon, 7 Dec 1998, Geert Uytterhoeven wrote:
> > 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.  :-)

The framework is already in the mach kernel. In fact, there is video
initialization code for the pdm (the [6-8]100's)?? The other drivers
are only partially implemented.


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

Re: XF68_FBDev under MkLinux?

[Ryuichi Oikawa]

From: "David A. Gatwood" <marsmail@globegate.utm.edu>
Subject: Re: XF68_FBDev under MkLinux? 
..snip..
> > >      This requires no kernel changes. In XF68_FBDev, the video ioctl
> > >      and mmap stuff has to be changed slightly.
> 
> And the mach kernel has to have a small amount of code added to map that
> physical space into the vmlinux server's address space, I believe, or
> probably more like additional code in the vmlinux server to request it....
> I'm not sure where the line is drawn... I'm still learning the
> Mach/vmlinux io mapping stuff, the hard way... by coding something and
> then poking around to see why it doesn't work.  :-)
 I have an mmap and ioctl stuff patch for MkLinux at:
  ftp://ppc.linux.or.jp/pub/users/oikawa/mklinux/AccelX_interface/981017/AccelX_support.patch
that makes ioctl(, VC_GETMODE, (struct vc_mode *)&mode) be able to fill out
mode.disp_reg_address field with mmappable graphic chip's MMIO address.

Sorry, but you have to apply this patch manually because this is not
to GENERIC ## kernel but to Apple's DR3 and it contains unnecessary
code appended.
 This patch doesn't do any address alignment even if MMIO address is
not page aligned. Please fix it before use such a graphic chip.


Regards,

Ryuichi Oikawa
roikawa@rr.iij4u.or.jp

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

Re: XF68_FBDev under MkLinux?

[anthony tong]

Geert Uytterhoeven (Sat, Dec 05, 1998 at 11:20:33PM +0100):
>   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.

Agreed.

> 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.

Mark Hatle ported /dev/adbmouse to mklinux last february. It wasn't
available in DR3 but I believe that it's available in the GENERIC
mklinux kernels.


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

Re: XF68_FBDev under MkLinux?

[Ryuichi Oikawa]

From: anthony tong <atong@uiuc.edu>
Subject: Re: XF68_FBDev under MkLinux?
> 
> Geert Uytterhoeven (Sat, Dec 05, 1998 at 11:20:33PM +0100):
> >   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.
> 
> Agreed.

Simple question: What is the advantage of fbdev server without
 frame buffer device ?

Please note I am NOT against this project. More possible selection
is better.


Regards,

Ryuichi Oikawa
roikawa@rr.iij4u.or.jp

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

Re: XF68_FBDev under MkLinux?

[Geert Uytterhoeven]

On Mon, 7 Dec 1998, Ryuichi Oikawa wrote:
> From: anthony tong <atong@uiuc.edu>
> Subject: Re: XF68_FBDev under MkLinux?
> > 
> > Geert Uytterhoeven (Sat, Dec 05, 1998 at 11:20:33PM +0100):
> > >   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.
> > 
> > Agreed.
> 
> Simple question: What is the advantage of fbdev server without
>  frame buffer device ?

This is indeed a very good question!

I think the most important reason is that you're integrated with XFree86 (like
all the other Linux ports), and get all its extra features for free.

Another approach would be to create a new subdirectory
xc/programs/Xserver/hw/xfree68/xpmac/, that only differs from the xfree68/fbdev
directory by the differences between the frame buffer device API and the
MkLinux graphics API. The disadvantage of this is that you still have two
server binaries, though.

Greetings,

						Geert

--
Geert Uytterhoeven                     Geert.Uytterhoeven@cs.kuleuven.ac.be
Wavelets, Linux/{m68k~Amiga,PPC~CHRP}  http://www.cs.kuleuven.ac.be/~geert/
Department of Computer Science -- Katholieke Universiteit Leuven -- Belgium




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

XF68_FBDev

[nathan ingersoll]

Could anyone successfully running XF68_FBDev with a ATI 3D RAGE II video
card please send me a copy of their XF86Config file? I've been having a
tough time getting things set up right.

Thank you,

Nathan




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

Re: XF68_FBDev under MkLinux?

[Tom Rini]

On Sat, 5 Dec 1998, Geert Uytterhoeven wrote:

> 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.

Well, globegate GENERIC kernels have the slightly-better then current
adbmouse driver from linuxpmac (does macx mice w/o problem).

---
Tom Rini (TR1265)
http://dobbstown.yeti.edu/


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

Re: XF68_FBDev under MkLinux?

[Martin Costabel]

Geert Uytterhoeven wrote:
> 
[]
> 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.

Did you fix the problem with the non-working option (alt) keys?
In the XF68_FBDev of the new R5beta linuxppc, it is still there.
For me (PM6400, standard Apple keyboard and 1-button mouse), XF68_FBDev
is pretty much useless. 

If you need more information to get to the bottom of this problem, just
say what kind of tests to perform.

--
Martin

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

Re: XF68_FBDev under MkLinux?

[Geert Uytterhoeven]

On Sun, 6 Dec 1998, Martin Costabel wrote:
> Geert Uytterhoeven wrote:
> > 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.
> 
> Did you fix the problem with the non-working option (alt) keys?
> In the XF68_FBDev of the new R5beta linuxppc, it is still there.
> For me (PM6400, standard Apple keyboard and 1-button mouse), XF68_FBDev
> is pretty much useless. 

What about the XF68_FBDev from XFree86 3.3.3?

> If you need more information to get to the bottom of this problem, just
> say what kind of tests to perform.

Problem is that I don't know anything about ADB, nor have ADB devices :-(

Greetings,

						Geert

--
Geert Uytterhoeven                     Geert.Uytterhoeven@cs.kuleuven.ac.be
Wavelets, Linux/{m68k~Amiga,PPC~CHRP}  http://www.cs.kuleuven.ac.be/~geert/
Department of Computer Science -- Katholieke Universiteit Leuven -- Belgium



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

Re: XF68_FBDev under MkLinux?

[Kohkichi Hosoda]

>>>>> On Sun, 6 Dec 1998 16:13:38 +0100 (MET), Geert Uytterhoeven <geert@geert.cs.kuleuven.ac.be> said:

>> Did you fix the problem with the non-working option (alt)
>> keys?  In the XF68_FBDev of the new R5beta linuxppc, it
>> is still there.  For me (PM6400, standard Apple keyboard
>> and 1-button mouse), XF68_FBDev is pretty much useless.

Geert> What about the XF68_FBDev from XFree86 3.3.3?

Hi,

I just installed Xfree86-3.3.3 and XF68_FBDev on PowerMac
8500/120 (standard Apple keyboard, 1-button mouse and
linuxpmac 2.1.125).  The situation was the same as Martin.
So, I added adb_buttons=1 in boot-file and restarted the
system.  Then it seems to me that option key itself acts
like right button.  However, there is no middle button
emulation.

Somebody in this list I can't remember (sorry) wrote that
adb_buttons=1 option enable the right option- and control-
keys to emulate mouse buttons.  Unfortunately, my standard
Apple keyboard has left option- and control- keys but does
not have right ones. :-(

Kohkichi Hosoda

E-mail address: khosoda@venus.dti.ne.jp

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

Re: XF68_FBDev under MkLinux?

[Martin Costabel]

On Sun, 6 Dec 1998, Geert Uytterhoeven wrote:
>On Sun, 6 Dec 1998, Martin Costabel wrote:
>> Geert Uytterhoeven wrote:
>> > 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.
>> 
>> Did you fix the problem with the non-working option (alt) keys?
>> In the XF68_FBDev of the new R5beta linuxppc, it is still there.
>> For me (PM6400, standard Apple keyboard and 1-button mouse), XF68_FBDev
>> is pretty much useless. 
>
>What about the XF68_FBDev from XFree86 3.3.3?

I must confess that I am a bit lost among the many different versions of 
XF68_FBDev. For the one from XFree86 3.3.3, do I have to install all of 
XFree86 3.3.3, or does it work with XFree86 3.3.2 which is in linuxppc-pre-R5?
I tried several versions, and both on R4 and on pre-R5, the result was the same.
Except that some versions did not want to run on pre-R5.

I would be the first to assume that this is a problem with my configuration,
except that there were some reports by others who had the same problems,
and I am pretty sure that there is a large silent majority of linuxppc users on power Macs who never tried XF68_FBDev so far.
>
>> If you need more information to get to the bottom of this problem, just
>> say what kind of tests to perform.
>
>Problem is that I don't know anything about ADB, nor have ADB devices :-(

If XF68_FBDev is going to be the standard for everybody, one should make sure
that it works on PowerMacs, too.

--
Martin



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

Re: XF68_FBDev under MkLinux?

[Geert Uytterhoeven]

On Mon, 7 Dec 1998, Martin Costabel wrote:
> >What about the XF68_FBDev from XFree86 3.3.3?
> 
> I must confess that I am a bit lost among the many different versions of 
> XF68_FBDev. For the one from XFree86 3.3.3, do I have to install all of 
> XFree86 3.3.3, or does it work with XFree86 3.3.2 which is in linuxppc-pre-R5?
> I tried several versions, and both on R4 and on pre-R5, the result was the same.
> Except that some versions did not want to run on pre-R5.

The X server doesn't use any of the X11 shared libs. All it needs is libc and
libm. So if you have to correct glibc, it's supposed to work.

> If XF68_FBDev is going to be the standard for everybody, one should make sure
> that it works on PowerMacs, too.

Sure it has to!

Greetings,

						Geert

--
Geert Uytterhoeven                     Geert.Uytterhoeven@cs.kuleuven.ac.be
Wavelets, Linux/{m68k~Amiga,PPC~CHRP}  http://www.cs.kuleuven.ac.be/~geert/
Department of Computer Science -- Katholieke Universiteit Leuven -- Belgium


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