From: "nsauzede" <nsauzede@online.fr>
To: "linux-mips" <linux-mips@linux-mips.org>
Subject: linux-mips fbdev
Date: Thu, 12 Dec 2002 00:24:07 +0100 [thread overview]
Message-ID: <013b01c2a16c$68385f60$0100a8c0@yak> (raw)
[-- Attachment #1: Type: text/plain, Size: 1337 bytes --]
Hi list !
I've got an Indy running linux-mips and I wonder if fbdev exists/is possible on this platform.
If I remember well, direct framebuffer mmaping like on intel platforms for example is not possible because Video Ram is hidden behind SGI custom video chips, and video accesses are done by some magic incantations..
But the fact is that I can run linux on my box, a gfx penguin logo appears at boot, and I can enjoy a huge beautifull mc on the console, so I guess some "kind" of framebuffer is there, but not the full-blown Geert's-et-al stuff.
So my question is : would it be feasible/easy to implement some kind of "stubs" to, at least, simulate a straight framebuffer, with full /dev/fb0 stuff, so I could port my fbdev userspace stuff to my Indy ???
Sorry if the answer is obvious..
Thanks so much to all of you linux-mips-gurus for what has been done !!
Nicolas Sauzede.
ps : in case the answer is : No; would it be hard for newbies like me to enable userspace apps to access video screen (just like with fbdev, but without it), ie : be able to do some bitblt() or such ? I've tried to copy/paste some kernel fragments that "seems" to do the voodoo-like video accesses, just to set some pixels on screen, but all I could obtain was : entire screen corrupted or even crash (no BSOD here though <whew> ;)
[-- Attachment #2: Type: text/html, Size: 2410 bytes --]
next reply other threads:[~2002-12-11 23:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-11 23:24 nsauzede [this message]
2002-12-22 13:58 ` linux-mips fbdev Geert Uytterhoeven
2002-12-23 14:23 ` nsauzede
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='013b01c2a16c$68385f60$0100a8c0@yak' \
--to=nsauzede@online.fr \
--cc=linux-mips@linux-mips.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