On Wed, 3 Mar 2004, wjd wrote:
> Hi All,
>
> I wrote a X11 application to get image of some window by XGetImage(),but after
> i switch to other terminal by Ctrl+Alt+F2,my application can't get correct image of
> windows.Are there any idea to fix this problem? or how can X11 application to
On Tue, 2 Mar 2004, Sottek, Matthew J wrote:
> > Also, I would like to make sure that the new design has a much
> > improved syncing mechanism. Syncing should be, at a minimum,
> > on a per-surface basis. Perhaps even a bounded region of a
> > surface is justified. As GUI's become more "media rich
Hi All,
I wrote a X11 application to get image of some window by XGetImage(),but after
i switch to other terminal by Ctrl+Alt+F2,my application can't get correct image of
windows.Are there any idea to fix this problem? or how can X11 application to know if
desktop has been switch to ano
On Tue, 2 Mar 2004, Sottek, Matthew J wrote:
> > It's currently global because the hardware I work on doesn't
> >have to fall back to software very often. Bookkeeping on a per-
> >surface basis is a simple modification and one I will add. This
> >precludes using XAA2 with hardware that doesn't
We have scheduled a three day X Developer's meeting from
Wednesday, April 28, through Friday, April 30, 2004, at the
Cambridge Research Laboratory (CRL) in Cambridge, Massachusetts.
This meeting is intended to cover a wide variety of topics
about X Window System technologies, and the as yet unmet
>> Smaller is good, but can you give an example of "benchmark
>> rigging"?
>
> Rather than using mi to break down a complex primitive into
>spans and then sending the list of spans to the driver, XAA
>would replace mi so it could send individual spans to the
>driver as soon as it computed them, th
On Tue, 2004-03-02 at 21:06, Mark Vojkovich wrote:
> On Tue, 2 Mar 2004, David Dawes wrote:
>
> > On Tue, Mar 02, 2004 at 10:57:04AM -0800, Mark Vojkovich wrote:
> > >
> > > Well, then I guess I could call the header file xaa2.h
> >
> > Not to be too picky, but won't this be the third version o
On Tue, 2 Mar 2004, Sottek, Matthew J wrote:
> Smaller is good, but can you give an example of "benchmark
> rigging"?
Rather than using mi to break down a complex primitive into
spans and then sending the list of spans to the driver, XAA
would replace mi so it could send individual spans to the
David Dawes wrote:
On Tue, Mar 02, 2004 at 01:18:20AM +0100, Thomas Winischhofer wrote:
Alex Deucher wrote:
I like Option 1. but either is ok with me. Also, FWIW, a lot of the
other mergedfb code could/should be moved into a general mergedfb lib.
Stuff like pseudo-xinerama could be folded into
On Tue, 2 Mar 2004, David Dawes wrote:
> On Tue, Mar 02, 2004 at 10:57:04AM -0800, Mark Vojkovich wrote:
> >On Tue, 2 Mar 2004, [ISO-8859-1] Frank Gießler wrote:
> >
> >> Mark Vojkovich wrote:
> >> >We don't care what the filenames are except for the header files.
> >> > The only reason why we
On Tue, Mar 02, 2004 at 07:18:37PM +0100, Sven Luther wrote:
>On Tue, Mar 02, 2004 at 12:59:52PM -0500, David Dawes wrote:
>> >> Section "Screen"
>> >> Identifier "Screen0"
>> >> Device "Videocard0"
>> >> DefaultDepth 24
>> >> SubSection "Monitor0"
>> >> SubSection "Displa
On Tue, Mar 02, 2004 at 10:57:04AM -0800, Mark Vojkovich wrote:
>On Tue, 2 Mar 2004, [ISO-8859-1] Frank Gießler wrote:
>
>> Mark Vojkovich wrote:
>> >We don't care what the filenames are except for the header files.
>> > The only reason why we care about header files is that a driver
>> > might
On Tue, 2 Mar 2004, Torgeir Veimo wrote:
> On Mon, 2004-03-01 at 18:58 -0800, Mark Vojkovich wrote:
>
> > On Mon, 1 Mar 2004, Sottek, Matthew J wrote:
> >
> > > Will there be open discussion of what makes up Xaa? I know
> > > you have already have a working design but rather than accept
> > > m
On Tue, 2 Mar 2004, Knut J Bjuland wrote:
> Is the Nvidia closed source driver based on a early version off Xaa2?
The NVIDIA binary driver has a stripped-down and slightly hacked up
version of XAA2 in it.
Mark.
___
Devel mai
On Tue, 2 Mar 2004, [ISO-8859-1] Frank Gießler wrote:
> Mark Vojkovich wrote:
> >We don't care what the filenames are except for the header files.
> > The only reason why we care about header files is that a driver
> > might include support for both and may need both include paths.
> > There's
On Tue, Mar 02, 2004 at 12:59:52PM -0500, David Dawes wrote:
> >> Section "Screen"
> >>Identifier "Screen0"
> >>Device "Videocard0"
> >>DefaultDepth 24
> >>SubSection "Monitor0"
> >>SubSection "Display"
> >>Depth 16
> >>
On Tue, Mar 02, 2004 at 12:32:08PM +, Dr Andrew C Aitchison wrote:
>On Tue, 2 Mar 2004, Alan Hourihane wrote:
>
>> I mentioned in a reply to Alex, that maybe the ScreenLayout section should
>> use Monitor's rather than Screens. I think that should fix the orientation
>> issues, as the ScreenLay
--- Ryan Underwood <[EMAIL PROTECTED]> wrote:
>
> On Tue, Mar 02, 2004 at 05:56:01AM -0800, Alex Deucher wrote:
> > > As regards pseudo-xinerama, I think the SiS driver is the only
> one
> > > currently (unsure if Alex took that over, too). The Matrox driver
> has
> > > no
> > > such feature. I
On Tue, Mar 02, 2004 at 01:18:20AM +0100, Thomas Winischhofer wrote:
>Alex Deucher wrote:
>>
>> I like Option 1. but either is ok with me. Also, FWIW, a lot of the
>> other mergedfb code could/should be moved into a general mergedfb lib.
>> Stuff like pseudo-xinerama could be folded into the re
--- "Sottek, Matthew J" <[EMAIL PROTECTED]> wrote:
> >> Will there be open discussion of what makes up Xaa? I know
> >> you have already have a working design but rather than accept
> >> major changes wholesale can we discuss the finer points before
> >> they become defacto-accepted.
> >>
> >> -M
On Mon, Mar 01, 2004 at 04:11:02PM -0800, Mark Vojkovich wrote:
>On Mon, 1 Mar 2004, Alan Hourihane wrote:
>
>> I'm looking to enhance the parser in XFree86 so that a lot of redundant
>> code in the current drivers that implement the 'mergedfb' mode can
>> be eliminated such that they don't have to
On Mon, Mar 01, 2004 at 11:09:23PM +, Alan Hourihane wrote:
>On Mon, Mar 01, 2004 at 02:57:50PM -0800, Alex Deucher wrote:
>> --- Alan Hourihane <[EMAIL PROTECTED]> wrote:
>> > I'm looking to enhance the parser in XFree86 so that a lot of
>> > redundant
>> > code in the current drivers that imp
>> Will there be open discussion of what makes up Xaa? I know
>> you have already have a working design but rather than accept
>> major changes wholesale can we discuss the finer points before
>> they become defacto-accepted.
>>
>> -Matt
>
> It depends what you'd like to discuss. I already hav
Is the Nvidia closed source driver based on a early version off Xaa2?
Mark Vojkovich wrote:
On Mon, 1 Mar 2004, Sottek, Matthew J wrote:
Will there be open discussion of what makes up Xaa? I know
you have already have a working design but rather than accept
major changes wholesale can we disc
On Mon, Mar 01, 2004 at 10:10:40PM +, Alan Hourihane wrote:
>I'm looking to enhance the parser in XFree86 so that a lot of redundant
>code in the current drivers that implement the 'mergedfb' mode can
>be eliminated such that they don't have to do all the monitor munging
>in the driver.
>
>So h
On Tue, Mar 02, 2004 at 05:56:01AM -0800, Alex Deucher wrote:
> > As regards pseudo-xinerama, I think the SiS driver is the only one
> > currently (unsure if Alex took that over, too). The Matrox driver has
> > no
> > such feature. I don't think the OSX implementation is similar enough
> > to
>
Alex Deucher wrote:
I agree. I think metamodes are kind of klunky, but I don't know what
a better solution would be off hand. Another thing about the proposed
solution is that in many drivers certain configurations are assumed,
which can be confusing in the screen setup. For instance in the rad
Alan Hourihane wrote:
So you'd only use the modes for the second monitor that is described for
the primary monitor ?
Well, "described for the first monitor" isn't quite it. Although they
relate to monitor 1 in the config file, they equally descrbe both
monitors. Currently, it looks like this:
On Mon, 2004-03-01 at 18:58 -0800, Mark Vojkovich wrote:
> On Mon, 1 Mar 2004, Sottek, Matthew J wrote:
>
> > Will there be open discussion of what makes up Xaa? I know
> > you have already have a working design but rather than accept
> > major changes wholesale can we discuss the finer points b
--- Thomas Winischhofer <[EMAIL PROTECTED]> wrote:
> Alan Hourihane wrote:
> >>
> >>I prefer option 2 because of its fewer levels of SubSections.
> >>
> >>What's the replacement for the metamodes option/concept? Will this
> survive?
> >
> >
> > No.
>
> Hm.
>
> >>In that case, I don't think thi
On Tue, 2 Mar 2004, Alan Hourihane wrote:
> I mentioned in a reply to Alex, that maybe the ScreenLayout section should
> use Monitor's rather than Screens. I think that should fix the orientation
> issues, as the ScreenLayout is really describing the monitor positions.
I didn't spot this the firs
On Tue, Mar 02, 2004 at 11:43:34AM +0100, Thomas Winischhofer wrote:
> Alan Hourihane wrote:
> >>
> >>I prefer option 2 because of its fewer levels of SubSections.
> >>
> >>What's the replacement for the metamodes option/concept? Will this
> >>survive?
> >
> >
> >No.
>
> Hm.
>
> >>In that case,
Alan Hourihane wrote:
I prefer option 2 because of its fewer levels of SubSections.
What's the replacement for the metamodes option/concept? Will this survive?
No.
Hm.
In that case, I don't think this is a real step forward. It requires
more configuration data instead of less:
Only for simpl
On Tue, Mar 02, 2004 at 01:16:05AM +0100, Thomas Winischhofer wrote:
> Alan Hourihane wrote:
> >I'm looking to enhance the parser in XFree86 so that a lot of redundant
> >code in the current drivers that implement the 'mergedfb' mode can
> >be eliminated such that they don't have to do all the moni
Mark Vojkovich wrote:
We don't care what the filenames are except for the header files.
The only reason why we care about header files is that a driver
might include support for both and may need both include paths.
There's only one exported header file. I'd like to name it Xaa.h
to match the n
35 matches
Mail list logo
