| Age | Commit message (Collapse) | Author |
|---|
|
This uses the adapter names reported by the X 2D graphics driver.
(Transplanted from 8c06e053c6dbb2f31c004f6eb615ebbf3f67d667)
|
|
(Transplanted from f03669a2395d97a3e40615db1089af084a69d299)
|
|
(Transplanted from 574fefcee8b1b6456fd8dc9c06191cf4622f07eb)
|
|
(Transplanted from 378582ca7b95e634cb0b04b714df0170b60688b3)
|
|
Also, a few trivial constness cleanups.
(Transplanted from 83c85e349d6d09b06faa6d34c090038d7bd1ac81)
|
|
(Transplanted from b2dd043f187b6332248fd58410ffebf7e7727aeb)
|
|
The xine_xmalloc() function is going to be deprecated, as its
behaviour is rarely needed as such, and it's thus misused.
With this, almost all uses of xine_xmalloc() with static size (for
instance the value returned by sizeof()) or with a size that is
guaranteed not to be zero (like strlen()+1) are replaced with calls to
either calloc(1, ...) or malloc().
malloc() is used whenever the allocated memory is going to be
immediately overwritten, while calloc() is used in every other case,
as it sets the whole memory area to zero.
--HG--
extra : transplant_source : %8F%98%EC%02%1E%83%F0s%06X%83C%205Y%80%B12%CC%E1
|
|
expected.
add code to set this attribute from xine and mention nvidia-settings, since the user may need to select a sync device as well.
|
|
These cheats where hiding a frame allocation bug in FFmpeg decoder
which was previously fixed.
(transplanted from c7cc5ff1e184791683ba13bdc54c53b5887e6587)
--HG--
extra : transplant_source : %C7%CC_%F1%E1%84y%16%83%BA%13%BD%C5LS%B5%88%7Ee%87
|
|
|
|
Some instances of "key colour" remain; ffmpeg is unmodified.
This change has caused two strings with two translations to collide (the
strings have become identical since some instances already used "colour").
I have therefore arbitrarily dropped the first of the differing translations,
the one for the string at src/video_out/video_out_directfb.c:1365.
|
|
--HG--
extra : transplant_source : %E0%D0%C5%8B%BEU%DD%24%5D7%1F%ADV%AD%EB%23%CBU%80%EB
|
|
For contributed code, leave whatever the version we last synced for is using
to make simpler future syncs.
|
|
|
|
A null pointer dereference happens if reading a xv port attribute
(which has been reported as readable) fails. This issue exists for
example with proprietary (and a bit buggy ...) ati drivers;
nevertheless it shouldn't cause a segmentation fault (the non-xcb
version simply stores an unitialised value).
This patches solves the issue in a clean way for both branches.
Fixes debian bug #428612 :-)
|
|
|
|
|
|
CVS patchset: 8770
CVS date: 2007/03/29 18:58:21
|
|
thus reported as 0×0), to avoid disabling shared memory for all others. Patch by Reinhard Nissl.
CVS patchset: 8748
CVS date: 2007/03/25 23:13:53
|
|
CVS patchset: 8746
CVS date: 2007/03/25 23:07:23
|
|
the proper XCB enum.
CVS patchset: 8599
CVS date: 2007/02/19 22:22:32
|
|
Pfister.
CVS patchset: 8596
CVS date: 2007/02/15 18:26:55
|
|
packages for about ten days.
CVS patchset: 8595
CVS date: 2007/02/15 15:19:32
|
