linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@gmail.com>
To: Vladimir Dergachev <volodya@mindspring.com>
Cc: Ian Romanick <idr@us.ibm.com>, Jon Smirl <jonsmirl@gmail.com>,
	linux-fbdev-devel@lists.sourceforge.net,
	DRI developer's list <dri-devel@lists.sourceforge.net>
Subject: Re: CRTC scanout buffer types
Date: Mon, 08 Aug 2005 09:15:10 +0800	[thread overview]
Message-ID: <42F6B21E.1070405@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0508071830270.11306@node2.an-vo.com>

Vladimir Dergachev wrote:
>> I agree that something like the above is acceptable, exept that we need
>> an extra field for offset and another if indexed color or not. So 
>> something like:
>>
>> A:2/0/R:10/2/G:10/12/B:10/22//I
> 
> This is getting more cryptic by the minute.
> 
> Can't we have a simple field: value lines ? Something like:
> AlphaBits: 2
> AlphaOffset: 0
> 

The problem with doing that is you need to set everything in one go.
Separating all those fields into different sysfs attributes will have
a problem with synchronization.

One workaround is to have another attribute 'Activate'. Nothing is set
until the 'Activate' attribute is written to.  There is still the problem
of another process changing the other attributes behind the back of the
original process.

Tony


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

  reply	other threads:[~2005-08-08  1:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-05 20:19 CRTC scanout buffer types Jon Smirl
2005-08-06 23:23 ` Patrick McFarland
2005-08-06 23:27   ` Jon Smirl
2005-08-06 23:45   ` Dave Airlie
2005-08-07  9:43 ` Geert Uytterhoeven
2005-08-07 13:41   ` [Linux-fbdev-devel] " Jon Smirl
2005-08-07 20:42     ` Geert Uytterhoeven
2005-08-07 21:03     ` [Linux-fbdev-devel] " Ian Romanick
2005-08-07 21:45       ` Antonino A. Daplas
2005-08-07 22:31         ` [Linux-fbdev-devel] " Vladimir Dergachev
2005-08-08  1:15           ` Antonino A. Daplas [this message]
2005-08-08  2:05             ` Vladimir Dergachev
2005-08-08  2:33             ` Jon Smirl
2005-08-08  5:52               ` Antonino A. Daplas
2005-08-08  8:39               ` Geert Uytterhoeven
2005-08-08 13:14                 ` [Linux-fbdev-devel] " Jon Smirl
2005-08-07 21:10     ` Antonino A. Daplas
2005-08-08  8:41       ` Geert Uytterhoeven

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=42F6B21E.1070405@gmail.com \
    --to=adaplas@gmail.com \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=idr@us.ibm.com \
    --cc=jonsmirl@gmail.com \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=volodya@mindspring.com \
    /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).