From: "nsauzede" <nsauzede@online.fr>
To: "Geert Uytterhoeven" <geert@linux-m68k.org>
Cc: "linux-mips" <linux-mips@linux-mips.org>
Subject: Re: linux-mips fbdev
Date: Mon, 23 Dec 2002 15:23:00 +0100 [thread overview]
Message-ID: <004d01c2aa8e$cffc4690$8700a8c0@yak> (raw)
In-Reply-To: Pine.GSO.4.21.0212221454130.11726-100000@vervain.sonytel.be
Hello !
Thank you so much for your response !! :-)
> Yes, you always have to use the graphics accelerator.
Ok
> By using the tricks also used in vga256fb (cfr.
> http://www.kyuzz.org/antirez/vga256fb.html), you can emulate a normal
linear
> frame buffer and use the Indy's graphics accelerator to update the screen.
> But it will be slow.
This link is really interesting, thanks !
> An alternative is to use mmap() tricks to find out what's updated in the
fake
> linear frame buffer, and update the screen afterwards.
>
> Or program the Indy graphics accelerator directly from user space :-)
Hmm, may be that would be the best I have to do for now, at least in order
to get familiarized with the "Indy graphics accelerator" you're talking
about...
Any pointers ?? All I could find about it was kernel code fragments found in
the linux mips source, that crashed my indy
when trying to play with pixels in user mode..
But, maybe you're not implied a lot in Indy graphics, and I'm sorry if I
bother you to much with my problems !!
> Gr{oetje,eeting}s,
>
> Geert
Thank you !
Nicolas Sauzede.
prev parent reply other threads:[~2002-12-23 14:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-11 23:24 linux-mips fbdev nsauzede
2002-12-22 13:58 ` Geert Uytterhoeven
2002-12-23 14:23 ` nsauzede [this message]
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='004d01c2aa8e$cffc4690$8700a8c0@yak' \
--to=nsauzede@online.fr \
--cc=geert@linux-m68k.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.