I have S3 Trio64V2 with VBE 1.2 and I want to add the possibility of
display autodetection via DDC to s3 driver. There is two ways to deal
with DDC: (i) VESA BIOS Extension and (ii) directly from videochip's DDC
registers. The later method currently is impossible to implement due to
the lack of
Simon Thum simon.t...@gmx.de writes:
AFAIK the DDC stuff was endorsed in 2.0, so it's probably just a
heuristic, not a hard limit. I'm not the maintainer but I guess a good
patch is appreciated. IIRC the vbe bios does advertise if it has the
DDC extension, which should be a preferable
Evgeny M. Zubok evgeny.zu...@tochka.ru writes:
So I conclude that the VBE version in vbeDoEDID can be lowered to 1.2
as soon as the procedure for verifying the presence of subfunction
(15h in the case of DDC) is defined in VESA 1.2 and VESA 2.0 specs.
If my arguments are right
I have made the first attempt to implement basic `Copy' and `Solid' EXA
functions in xf86-video-s3, but soon came to intention that EXA support
is not possible. Is there mistake in my thinking below?
S3's Graphic Processor (S3 GP) is able to copy areas only in terms of
coordinates, i. e. it can
Looks like no dice for EXA. Fixed pitches, no offsets... ouch.
Yes, I think the same. 'Solid' and 'Copy' is the only functionality that
would be possible with this hardware. There is no reason to waste a time
further. BTW, both 'Solid' and 'Copy' work fine only when operate on
framebuffer
Ville Syrjälä syrj...@sci.fi writes:
Why wouldn't it work if you just allocate everything using the same
pitch? Or does the allocator make some assumptions about the pitches
the hardware can handle?
The allocator make the assumption that hardware is able to copy
offscreen pixmaps with any
Ville Syrjälä syrj...@sci.fi writes:
Just set the alignment to your fixed pitch value and it should work,
shouldn't it?
Great! Good idea! I have tried to set up pitch align
pEXA-pixmapPitchAlign = pScrn-displayWidth * pS3-s3Bpp;
and got almost normal working screen (with artefacts though)
Michel Dänzer mic...@daenzer.net writes:
EXA bug: Calling FinishAccess on pixmap 0x9278d68 with index 1 while
it should have been (nil).
This may indeed be a bug, Maarten? Might be interesting to see gdb
backtraces for when these trigger.
Is the
Michel Dänzer mic...@daenzer.net writes:
I think that it may be bug somewhere in EXA or driver bacause
server's log is full of error messages.
EXA bug: Calling FinishAccess on pixmap 0x9278d68 with index 1 while
it should have been (nil).
This may indeed be a bug, Maarten? Might be
Ajay Jain ajay...@gmail.com writes:
I want to start xterm in maximized mode. For example: xterm
-maximized. Could you suggest me a way (either via command line or via
Xdefaults or anything else)?
Hm, if your xterm doesn't support -maximized and if your WM (what's your
WM?) hasn't means to
Ajay Jain ajay...@gmail.com writes:
Hm, if your xterm doesn't support -maximized and if your WM (what's
your WM?) hasn't means to maximize xterm on start, you could try
'devilspie':
I use Gnome. Could you/anybody help on how can WM maximize it? I mean
what command. Meanwhile, I shall look
David Jackson djackson...@gmail.com writes:
The client wouldnt have to be moved between servers at all, it could
be the same proxy server, the proxy server could then open up
connections to actual X servers and forward things to the real X
servers. The proxy would massage and rework data as
David Jackson djackson...@gmail.com writes:
As far as I know NX is a tunneling and compression technology but will
not maintain a persistant X applications or session. The applications
are started when you connect from a remote location.
NX, along with compression and caching technologies,
13 matches
Mail list logo