From: James Simmons <jsimmons@edgeglobal.com>
To: linux-mm@kvack.org
Subject: accel handling
Date: Sun, 29 Aug 1999 10:57:00 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.10.9908291055420.28136-100000@imperial.edgeglobal.com> (raw)
Hi!
My name is James Simmons and I'm one of the new core designers for the
framebuffer devices for linux. Well I have redesigned the framebuffer
system and now it takes advantages of accels. Now the problem is that alot
of cards can't have simulanteous access to the framebuffer and the accel
engine. What I need to a way to put any process to sleep when they access
the framebuffer while the accel engine is active. This is for both read
and write access. Then once the accel engine is idle wake up the process.
MM is beyond me. Trust me I tried to find a solution. Anyone have a idea
what needs to be done? Thank you.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
next reply other threads:[~1999-08-29 14:53 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-29 14:57 James Simmons [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-08-31 3:39 Jens Owen
1999-08-31 12:51 ` Stephen C. Tweedie
1999-08-29 14:52 James Simmons
1999-08-29 16:14 ` Stephen C. Tweedie
1999-08-30 1:14 ` James Simmons
1999-08-30 10:44 ` Stephen C. Tweedie
1999-08-30 12:06 ` Marcus Sundberg
1999-08-30 14:18 ` Stephen C. Tweedie
1999-08-30 14:50 ` James Simmons
1999-08-30 15:52 ` Stephen C. Tweedie
1999-08-30 17:51 ` James Simmons
1999-08-30 20:27 ` Stephen C. Tweedie
1999-08-31 0:28 ` Vladimir Dergachev
1999-08-31 10:55 ` Marcus Sundberg
1999-08-31 12:49 ` Stephen C. Tweedie
1999-08-31 17:10 ` James Simmons
1999-08-31 18:44 ` Stephen C. Tweedie
1999-08-30 14:31 ` James Simmons
1999-08-30 18:51 ` Eric W. Biederman
1999-08-30 19:18 ` James Simmons
1999-08-30 21:39 ` Andreas Beck
1999-08-30 20:36 ` Stephen C. Tweedie
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=Pine.LNX.4.10.9908291055420.28136-100000@imperial.edgeglobal.com \
--to=jsimmons@edgeglobal.com \
--cc=linux-mm@kvack.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