linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: James Simmons <jsimmons@edgeglobal.com>
Cc: Linux MM <linux-mm@kvack.org>, Stephen Tweedie <sct@redhat.com>
Subject: Re: MMIO regions
Date: Mon, 11 Oct 1999 18:09:09 +0100 (BST)	[thread overview]
Message-ID: <14338.6581.988257.647691@dukat.scot.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.10.9910061600520.29637-100000@imperial.edgeglobal.com>

Hi,

On Wed, 6 Oct 1999 16:15:59 -0400 (EDT), James Simmons
<jsimmons@edgeglobal.com> said:

>> Look at http://www.precisioninsight.com/dr/locking.html for a
>> description of the cooperative lightweight locking used in the DRI 

> I have read those papers. Its not compatible with fbcon. It would
> require a massive rewrite which would break everything that works with
> fbcon. 

Sure.  It requires that people cooperate in order to take advantage of
the locking protection.

> When people start writing apps using DRI and it locks their machine or
> damages the hardware. Well the linux kernel mailing list will have to
> hear those complaints. You know people will want to write their own
> stuff. Of course precisioninsight should make a licence stating it
> illegal to write your own code using their driver or a warning so they
> don't get their asses sued. These are the kinds of people who will
> look for other solutions like I am. So expect more like me.

You seem to be looking for a solution which doesn't exist, though. :)

It is an unfortunate, but true, fact that the broken video hardware
doesn't let you provide memory mapped access which is (a) fast, (b)
totally safe, and (c) functional.  Choose which of a, b and c you are
willing to sacrifice and then we can look for solutions.  DRI sacrifices
(b), for example, by making the locking cooperative rather than
compulsory.  The basic unaccelerated fbcon sacrifices (c).  Using VM
protection would sacrifice (a).  It's not the ideal choice, sadly.

--Stephen

--
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/

  reply	other threads:[~1999-10-11 17:09 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-04 14:38 James Simmons
1999-10-04 15:31 ` Stephen C. Tweedie
1999-10-04 15:52   ` James Simmons
1999-10-04 16:02     ` Benjamin C.R. LaHaise
1999-10-04 17:27       ` James Simmons
1999-10-04 17:56         ` Benjamin C.R. LaHaise
1999-10-04 18:26           ` James Simmons
1999-10-04 19:19         ` Stephen C. Tweedie
1999-10-06 20:15           ` James Simmons
1999-10-11 17:09             ` Stephen C. Tweedie [this message]
1999-10-11 17:26               ` Jeff Garzik
1999-10-11 23:14                 ` James Simmons
1999-10-11 17:57               ` James Simmons
1999-10-04 16:11     ` Stephen C. Tweedie
1999-10-04 18:29       ` James Simmons
1999-10-04 19:35         ` Stephen C. Tweedie
1999-10-07 19:40           ` James Simmons
1999-10-10 11:24             ` Rik Faith
1999-10-10 14:03               ` Eric W. Biederman
1999-10-10 18:46                 ` Rik Faith
1999-10-11  0:21                   ` James Simmons
1999-10-11 10:59                     ` Rik Faith
1999-10-11  3:38                   ` Eric W. Biederman
1999-10-10 14:21               ` James Simmons
1999-10-11 17:22             ` Stephen C. Tweedie
1999-10-04 16:58 ` Marcus Sundberg
1999-10-04 18:27   ` James Simmons

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=14338.6581.988257.647691@dukat.scot.redhat.com \
    --to=sct@redhat.com \
    --cc=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