From: Andrey Volkov <andreyvolkov@users.sourceforge.net>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: hwd accel framebuffer: Newbi question (sleep in sync)
Date: Mon, 11 Jul 2005 12:04:25 +0400 [thread overview]
Message-ID: <42D22809.8070800@users.sourceforge.net> (raw)
Hi all,
Anyone could explain me, could I or couldn't
use process sleep (i.e. wait_for..., sleep_on...)
in fb_info->fb_sync and/or in any hwd accelerated routines (i.e. blit,
cursor and rectfill)?
Code, which now in kernel, look terrible for me (counter based pooling).
Must it be so?
--
Regards,
Andrey Volkov
-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP,
AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar
next reply other threads:[~2005-07-11 8:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-11 8:04 Andrey Volkov [this message]
2005-07-22 3:58 ` hwd accel framebuffer: Newbi question (sleep in sync) Antonino A. Daplas
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=42D22809.8070800@users.sourceforge.net \
--to=andreyvolkov@users.sourceforge.net \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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).