From: Ryuichi Oikawa <roikawa@rr.iij4u.or.jp>
To: marsmail@globegate.utm.edu
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: XF68_FBDev under MkLinux?
Date: Wed, 09 Dec 1998 02:57:52 +0900 [thread overview]
Message-ID: <19981209025752W.roikawa@rr.iij4u.or.jp> (raw)
In-Reply-To: Your message of "Sun, 6 Dec 1998 19:18:18 -0600 (CST)" <Pine.LNX.3.96.981206190751.2542E-100000@globegate.utm.edu>
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 ]]
next prev parent reply other threads:[~1998-12-08 17:57 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
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 [this message]
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=19981209025752W.roikawa@rr.iij4u.or.jp \
--to=roikawa@rr.iij4u.or.jp \
--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).