[Fwd: xorg Digest, Vol 36, Issue 12]
Regina
regina.apel at gmx.de
Thu Jul 3 02:39:03 PDT 2008
-------- Original-Nachricht --------
Betreff: xorg Digest, Vol 36, Issue 12
Datum: Wed, 02 Jul 2008 06:52:16 -0700
Von: xorg-request at lists.freedesktop.org
Antwort an: xorg at lists.freedesktop.org
An: xorg at lists.freedesktop.org
Send xorg mailing list submissions to
xorg at lists.freedesktop.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.freedesktop.org/mailman/listinfo/xorg
or, via email, send a message with subject or body 'help' to
xorg-request at lists.freedesktop.org
You can reach the person managing the list at
xorg-owner at lists.freedesktop.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of xorg digest..."
Today's Topics:
1. using mesa git with xorg-server-1.5 branch (Tobias Jakobi)
2. Re: using mesa git with xorg-server-1.5 branch (Peter Hutterer)
3. Re: Remapping Ctrl-Alt-Backspace? (Johannes Truschnigg)
4. radeon driver and DRI (Florian Echtler)
5. Re: Further notes on 7.4 (core fonts) (Markus Kuhn)
6. Re: Further notes on 7.4 (Dan Nicholson)
7. Re: Further notes on 7.4 (core fonts) (Nicolas Mailhot)
8. Re: ati-6.9.0 unstable dualhead (Alex Deucher)
9. Re: Current tinderbox regression (xserver) (Adam Jackson)
10. Re: radeon driver and DRI (Alex Deucher)
----------------------------------------------------------------------
Message: 1
Date: Wed, 02 Jul 2008 13:42:26 +0200
From: Tobias Jakobi <liquid.acid at gmx.net>
Subject: using mesa git with xorg-server-1.5 branch
To: xorg at lists.freedesktop.org
Message-ID: <486B69A2.1070504 at gmx.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Hi folks,
shouldn't it be possible now to use a server from the xorg-server-1.5
branch (currently using 1.4.99.905) together with mesa git?
I have downgraded yesterday from xorg-server git to 1.4.99.905 because
MPX was giving me real headaches (like addititonal mouse cursors
appearing upon leaving quake3) and now I don't have acceleration through
TTM anymore.
Could it be that something is broken there? I remeber that mesa git
should now work with the 1.5 branch...
Greets,
Tobias
------------------------------
Message: 2
Date: Wed, 2 Jul 2008 21:45:59 +0930
From: Peter Hutterer <peter.hutterer at who-t.net>
Subject: Re: using mesa git with xorg-server-1.5 branch
To: Tobias Jakobi <liquid.acid at gmx.net>
Cc: xorg at lists.freedesktop.org
Message-ID: <20080702121559.GA6192 at emu>
Content-Type: text/plain; charset=us-ascii
On Wed, Jul 02, 2008 at 01:42:26PM +0200, Tobias Jakobi wrote:
> I have downgraded yesterday from xorg-server git to 1.4.99.905 because
> MPX was giving me real headaches (like addititonal mouse cursors
> appearing upon leaving quake3) [...]
are we talking about rendering artefacts here or actual new cursors popping
up? can you describe it in a bit more detail? Is there a way to reproduce it
that doesn't require quake3?
Cheers,
Peter
------------------------------
Message: 3
Date: Wed, 2 Jul 2008 14:28:23 +0200
From: Johannes Truschnigg <johannes.truschnigg at gmx.at>
Subject: Re: Remapping Ctrl-Alt-Backspace?
To: xorg at lists.freedesktop.org
Message-ID: <200807021428.23837.johannes.truschnigg at gmx.at>
Content-Type: text/plain; charset="iso-8859-1"
Hello again.
On Wednesday 02 July 2008 13:03:58 Simon Thum wrote:
> Joerg Sonnenberger wrote:
> > On Wed, Jul 02, 2008 at 10:20:33AM +0200, Johannes Truschnigg wrote:
> >> I as wondering if there is a way to conveniently (as in "don't have to
> >> mess around with the source") remap the three-finger-salute to kill the
> >> X-server.
> >
> > Do you really want to remap it? Why not just set Option "DontZap" True?
>
> If I got it right he wanted to make it *easier* to restart... Though
> your suggestion is probaby the better idea for a public place.
Yes, I actually do want to make it easier to restart the server ;-)
The keyboard is in another place, not publicly accessible anyway. Therefore,
only "authorized personell" would be able to operate it, yet aforementioned
staff has been having troubles executing the Ctrl-Alt-Backspace-keystroke.
So DontZap isn't going to solve my problem, I think.
--
with best regards:
- Johannes Truschnigg ( johannes.truschnigg at gmx.at )
www: http://johannes.truschnigg.info/
phone: +43 650 2 133337
jabber: johannes.truschnigg at gmail.com
Please do not bother me with HTML-eMail or attachments. Thank you.
------------------------------
Message: 4
Date: Wed, 02 Jul 2008 14:35:20 +0200
From: Florian Echtler <floe at butterbrot.org>
Subject: radeon driver and DRI
To: xorg at lists.freedesktop.org
Message-ID: <1215002120.10133.5.camel at pancake>
Content-Type: text/plain
Hello everybody,
I have a Radeon Mobility X1400 and just wanted to give the radeon driver
a shot to finally get rid of fglrx. It works fine, with the exception of
DRI. xorg.log shows:
(--) RADEON(0): Chipset: "ATI Mobility Radeon X1400" (ChipID = 0x7145)
(WW) RADEON(0): R500 support is under development. Please report any
issues to xorg-driver-ati at lists.x.org
(--) RADEON(0): Linear framebuffer at 0x00000000d8000000
(II) RADEON(0): PCIE card detected
(II) Loading sub module "int10"
(II) LoadModule: "int10"
(II) Loading /usr/lib/xorg/modules//libint10.so
(II) Module int10: vendor="X.Org Foundation"
compiled for 1.3.0, module version = 1.0.0
ABI class: X.Org Video Driver, version 1.2
(II) RADEON(0): initializing int10
(II) RADEON(0): Primary V_BIOS segment is: 0xc000
(II) RADEON(0): ATOM BIOS detected
(II) RADEON(0): ATOM BIOS Rom:
SubsystemVendorID: 0x17aa SubsystemID: 0x2006
IOBaseAddress: 0x2000
Filename:
BIOS Bootup Message: M64CSP/M62CSP/M54CSP/M52CSP
BIOS
(II) RADEON(0): Framebuffer space used by Firmware (kb): 20
(II) RADEON(0): Start of VRAM area used by Firmware: 0x7ffb000
(II) RADEON(0): Framebuffer space used by Firmware (kb): 20
(II) RADEON(0): Start of VRAM area used by Firmware: 0x7ffb000
(II) RADEON(0): AtomBIOS requests 20kB of VRAM scratch space
(II) RADEON(0): AtomBIOS VRAM scratch base: 0x7ffb000
(II) RADEON(0): Cannot get VRAM scratch space. Allocating in main memory
instead
(II) RADEON(0): Default Engine Clock: 452000
(II) RADEON(0): Default Memory Clock: 352000
(II) RADEON(0): Maximum Pixel ClockPLL Frequency Output: 1100000
(II) RADEON(0): Minimum Pixel ClockPLL Frequency Output: 0
(II) RADEON(0): Maximum Pixel ClockPLL Frequency Input: 13500
(II) RADEON(0): Minimum Pixel ClockPLL Frequency Input: 1000
(II) RADEON(0): Maximum Pixel Clock: 400000
(II) RADEON(0): Reference Clock: 27000
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: Searching for BusID pci:0000:01:00.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -19
drmOpenDevice: node name is /dev/dri/card1
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -19
drmOpenDevice: node name is /dev/dri/card2
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
... and so on until card14. /dev/dri is really empty, although I have
loaded the radeon and drm kernel modules. My kernel is 2.6.22, and the
radeon driver is 6.9.0 ..
Thanks, Yours, Florian
--
0666 - Filemode of the Beast
------------------------------
Message: 5
Date: Wed, 02 Jul 2008 14:10:56 +0100
From: Markus Kuhn <Markus.Kuhn at cl.cam.ac.uk>
Subject: Re: Further notes on 7.4 (core fonts)
To: xorg at lists.freedesktop.org
Message-ID: <20080702131056.5FC8153F90 at viterbi.cl.cam.ac.uk>
Content-Type: text/plain; charset=us-ascii
Glynn Clements wrote on 2008-06-30 21:55 UTC:
> Adam Jackson wrote:
> > The core fonts are still listed there, but really, don't. The only one
> > you want is font-misc-misc for fixed/cursor, expect the rest to leave
> > the list in 7.5.
Please don't cull all of them, for the following reasons:
- Some of the BDF fonts have reached unparalleled non-EastAsian Unicode
coverage, especially among the monospaced fonts suitable for use in
terminal emulators.
- Equal coverage cannot even closely be approximated by mixing glyphs
from different outline fonts, and such attempts fail in ugly ways
to preserve the monospacedness of the font on which many terminal
applications rely. Just try
http://www.cl.cam.ac.uk/~mgk25/ucs/examples/UTF-8-demo.txt
on a terminal emulator with outline fonts and compare the result
to simply using the good old 6x13 misc-fixed font in xterm instead.
- There are lots of people (including myself) who strongly prefer
using a handcrafted single monospaced bitmap font over a mix of
TrueType or Type1 fonts in terminal emulators
- Lots of popular applications rely on their presence
In addition to font-misc-misc, I would at least also like to see
bh-lucidatypewriter-75dpi preserved, if only because because
"-b&h-lucidatypewriter-medium-r-normal-sans-12-120-75-75-m-70-iso10646-1"
is a rather beautiful xterm font.
On the other hand, I won't object strongly to removing non-monospaced
BDF fonts (Adobe Helvetica, etc.), although I note that even these have
a vocal fan community, e.g.
http://bugs.freedesktop.org/show_bug.cgi?id=1401
and lots of applications will break without them.
> Why? It's not as if they require a lot of maintenance. Or any
> maintenance at all, really.
At least the misc-fixed-fixed core fonts *are* actively maintained. I
regularly receive contributions and bug fixes which I add in occasional
larger batches to git. And I was about to make substantial additions to
some of the fonts to improve Unicode 5.1 coverage (which you won't find
for a very long time in most freely available Type1 or TrueType fonts;
where else will you get the glyph for U+1E9E LATIN CAPITAL LETTER SHARP S
from?). Bitmap fonts are so much easier to maintain than outline fonts,
therefore they can follow the Unicode standard much faster and thereby help
to speahead its implementation in many ways.
For more information on the ongoing maintenance of fonts-misc-misc:
http://www.cl.cam.ac.uk/~mgk25/ucs-fonts.html
http://en.wikipedia.org/wiki/Misc-fixed
Markus
--
Markus Kuhn, Computer Laboratory, University of Cambridge
http://www.cl.cam.ac.uk/~mgk25/ || CB3 0FD, Great Britain
------------------------------
Message: 6
Date: Wed, 2 Jul 2008 06:30:49 -0700
From: "Dan Nicholson" <dbn.lists at gmail.com>
Subject: Re: Further notes on 7.4
To: " R?mi Cardona " <remi at gentoo.org>
Cc: xorg at lists.freedesktop.org
Message-ID:
<91705d080807020630u6d9bb9f3w80284225be7db688 at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
On Wed, Jul 2, 2008 at 12:31 AM, R?mi Cardona <remi at gentoo.org> wrote:
> Dan Nicholson a ?crit :
>> I remembered a good reason why these should still be installed. Tons
>> of autotooled X programs (certainly in GNOME) use the autoconf macros
>> AC_PATH_X or AC_PATH_XTRA to find the X installation.
>
> Having looked at a good number of Gnome packages' configure.ac scripts,
> I don't recall seeing any of those macros being called for a long time.
http://svn.gnome.org/viewvc/metacity/trunk/configure.in?view=markup
http://svn.gnome.org/viewvc/gnome-control-center/trunk/configure.in?view=markup
http://svn.gnome.org/viewvc/gnome-keyring-manager/trunk/configure.ac?view=markup
http://svn.gnome.org/viewvc/gnome-mag/trunk/configure.in?view=markup
http://svn.gnome.org/viewvc/gnome-screensaver/trunk/configure.ac?view=markup
That was just from a brief browsing. I was pleasantly surprised to
find that many of the packages I looked at were only using
AC_PATH_XTRA after checking pkg-config first. I would say you haven't
been looking at GNOME configure.ac scripts very closely because
AC_PATH_XTRA is in nearly every single one. It has to be, after all,
since Xorg isn't the only X implementation, but it is the only one
that uses pkg-config.
--
Dan
------------------------------
Message: 7
Date: Wed, 2 Jul 2008 15:43:04 +0200 (CEST)
From: "Nicolas Mailhot" <nicolas.mailhot at laposte.net>
Subject: Re: Further notes on 7.4 (core fonts)
To: "Markus Kuhn" <Markus.Kuhn at cl.cam.ac.uk>
Cc: xorg at lists.freedesktop.org
Message-ID:
<41391.192.54.193.59.1215006184.squirrel at rousalka.dyndns.org>
Content-Type: text/plain;charset=utf-8
Le Mer 2 juillet 2008 15:10, Markus Kuhn a ?crit :
> And I was about to make substantial additions to
> some of the fonts to improve Unicode 5.1 coverage (which you won't
> find
> for a very long time in most freely available Type1 or TrueType fonts;
> where else will you get the glyph for U+1E9E LATIN CAPITAL LETTER
> SHARP S from?).
It's already available in currently published Linux Libertine,
http://linuxlibertine.sourceforge.net/Libertine-EN.html#spezial
in SIL roadmaps for the next releases of their fonts, discussed on the
DejaVu list, etc
> Bitmap fonts are so much easier to maintain than outline
> fonts,
> therefore they can follow the Unicode standard much faster and thereby
> help to speahead its implementation in many ways.
Please don't ressort to this kind of FUD-ind to support your positions.
Outline font projects are perfectly capable to integrate unicode
changes timely, and in fact it's not unknown-of to ask contributors to
sit on proposed glyphs while unicode.org determines their final
codepoint attribution (because it helps not one to seed the internet
with fonts that use a codepoint that's changed a few months later).
People update the fonts they use and bitmap fonts are not special in
this regard (actually since fewer people use bitmap fonts their
contributor pool is more limited).
--
Nicolas Mailhot
------------------------------
Message: 8
Date: Wed, 2 Jul 2008 09:46:47 -0400
From: "Alex Deucher" <alexdeucher at gmail.com>
Subject: Re: ati-6.9.0 unstable dualhead
To: "Simon Thum" <simon.thum at gmx.de>
Cc: Sebastian Glita <glseba at yahoo.com>, xorg at lists.freedesktop.org
Message-ID:
<a728f9f90807020646w407da396o1437fe06ddcc85da at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
On Wed, Jul 2, 2008 at 2:31 AM, Simon Thum <simon.thum at gmx.de> wrote:
> Alex Deucher wrote:
>>
>> On Tue, Jul 1, 2008 at 11:45 AM, Sebastian Glita <glseba at yahoo.com> wrote:
>>>
>>> I'm using dualhead an ASUS with ATI Radeon Xpress 1100 200M against a
>>> Belinea SVGA monitor.
>>> The latest version now of xf86-video-ati drives the second monitor in an
>>> unstable state of shivering, trembling, flickering very fast (or something
>>> like that).
>>
>> Please try git master. There was a problem with the DAC setup on
>> RS4xx chips in 6.9.0. I may roll a 6.9.1 soon to pickup the fallout
>> from 6.9.0 testing.
>
> I have a RV280 + LVDS, and 6.9.0 screwed my LCD worse than pre-6.3 did. So
> it can't be only DAC. (6.8.0 is fine!)
>
When you say LCD, do you mean LVDS or an LCD connected via VGA/DVI?
How is it screwed?
Can you file a bug? https://bugs.freedesktop.org
> Also, though EXA improved a lot, there arew still lots of (fairly
> unpredictable, but generally likely during tab or window switches)
> occassions where it seems to spin. XAA still has better perf for me.
>
To really get the full potential of EXA you need a recent xserver (>=
1.5 optimally).
> For some reason I can't switch on AGP fast writes. May this be the cause?
>
Don't use fastwrites. They are disabled by default for a reason.
> If you want I can send logs etc.
>
Sure. Attach them to the bug if you file one.
Alex
> Regards,
>
> Simon
>
------------------------------
Message: 9
Date: Wed, 02 Jul 2008 09:46:45 -0400
From: Adam Jackson <ajax at redhat.com>
Subject: Re: Current tinderbox regression (xserver)
To: Chris Ball <cjb at laptop.org>
Cc: xorg at lists.freedesktop.org
Message-ID: <1215006405.24769.173.camel at localhost.localdomain>
Content-Type: text/plain; charset="us-ascii"
On Tue, 2008-07-01 at 20:18 -0400, Chris Ball wrote:
> Hi,
>
> > koffscreen.c:319: error: 'pKaaPixmap' undeclared
>
> Since kdOffscreenMarkUsed()'d callers are gone, I think this is the
> right idea, and it fixes the build:
I agree. Pushed, thanks!
- ajax
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url : http://lists.freedesktop.org/archives/xorg/attachments/20080702/a98d1bb9/attachment-0001.pgp
------------------------------
Message: 10
Date: Wed, 2 Jul 2008 09:52:14 -0400
From: "Alex Deucher" <alexdeucher at gmail.com>
Subject: Re: radeon driver and DRI
To: "Florian Echtler" <floe at butterbrot.org>
Cc: xorg at lists.freedesktop.org
Message-ID:
<a728f9f90807020652y2507cf76ld909f9490c24822a at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
On Wed, Jul 2, 2008 at 8:35 AM, Florian Echtler <floe at butterbrot.org> wrote:
> Hello everybody,
>
> I have a Radeon Mobility X1400 and just wanted to give the radeon driver
> a shot to finally get rid of fglrx. It works fine, with the exception of
> DRI. xorg.log shows:
<snip>
>
> ... and so on until card14. /dev/dri is really empty, although I have
> loaded the radeon and drm kernel modules. My kernel is 2.6.22, and the
> radeon driver is 6.9.0 ..
you need the drm from freedesktop.org git master or the latest
pre-release kernel from Linus for drm with r5xx support.
Alex
------------------------------
_______________________________________________
xorg mailing list
xorg at lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
End of xorg Digest, Vol 36, Issue 12
************************************
More information about the xorg
mailing list