Re: CRTC scanout buffer types

[Jon Smirl <jonsmirl@gmail.com>]

On 8/7/05, Antonino A. Daplas <adaplas@gmail.com> wrote:
> 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

The offsets are not needed as part of the input, they should be part
of the output display. It is the chip driver that will determine the
offsets, not the user.

The only exception I can think of is that the radeon hardware can
control which nibble is used in 4bpp. I'd say if you need that kind of
control use the ioctl and keep the sysfs input string simpler. If the
config is set from sysfs let the driver pick the nibble order.

This also implies that you don't need to control RGB vs BGR on input,
just let the driver choose and check what you got on output.

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


-- 
Jon Smirl
jonsmirl@gmail.com


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