Printer-builtin fontpaths broken / was: Re: CVS Update: xc (branch: trunk)
David Dawes wrote: CVSROOT:/home/x-cvs Module name:xc Changes by: [EMAIL PROTECTED] 04/02/11 13:11:26 Log message: 799. Some more font path checks. Modified files: xc/lib/font/fontfile/: dirfile.c encparse.c fontfile.c xc/programs/Xserver/hw/xfree86/: CHANGELOG Revision ChangesPath 3.18 +17 -1 xc/lib/font/fontfile/dirfile.c 1.20 +7 -2 xc/lib/font/fontfile/encparse.c 3.22 +30 -11xc/lib/font/fontfile/fontfile.c 3.3139+2 -1 xc/programs/Xserver/hw/xfree86/CHANGELOG David: Somehow these changes broke Xprt's handing of printer builtin fonts (e.g. font paths prefixed with PRINTER: which are enabled dynamically on per-model-config basis). Bye, Roland -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, CJAVASunUnix programmer /O /==\ O\ TEL +49 2426 901568 FAX +49 2426 901569 (;O/ \/ \O;) ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: radeon dri lockup
On Sun, 15 Feb 2004, Jonathan Isom wrote: I have a Radeon 8500 that also locks up hard. I enabled sysrq in my kernel and lockup makes kernel too broken even for that. I am currently using 2.6.3-rc3, but all other kernels I tried lockup too. It appears the lockup is in the dri somewhere as the machine runs for days when no GUI has been used. I suspect that the problem may be in the OpenGL somewhere because most of the time the machine is frozen on a OpenGL xscreensaver. I haven't noticed a particular one though. What I have been doing is using the GUI for a while and then changing back to the console so the machine does not lock up, but I have noticed that the machine is becoming unstable even without the GUI running and a reboot is still necessary eventually. What I mean is that running the GUI eventually makes the machine unstable even if it is not allowed to actually lockup. I have tried various window managers and it does not seem to matter which one, eventually all have locked up when left on for several hours. I am going to try uninstalling xscreensaver and leaving the GUI up to see what happens. I've got a Radeon 7000 that locks up hard on a linux 2.4.23. no logs are written requiring power cycle. It locks in Quake3 in less that 7 minutes most times. some xscreensaver work fine,but havn't tried them all jisom at inbox dot lv ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel Fred Error Loading Explorer.exe You must reinstall Windows. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: radeon dri lockup
On Mon, 2004-02-16 at 05:45, Jonathan Isom wrote: I've got a Radeon 7000 that locks up hard on a linux 2.4.23. no logs are written requiring power cycle. It locks in Quake3 in less that 7 minutes most times. some xscreensaver work fine,but havn't tried them all If radeon_dri.so isn't at least from XFree86 4.3.0, please try a newer version. -- Earthling Michel Dnzer | Debian (powerpc), X and DRI developer Libre software enthusiast| http://svcs.affero.net/rm.php?r=daenzer ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Modifications to linuxPci.c to optimize PCI scan
Hi all,
I'm trying to optimize an embedded system based on
ARM9 CPU, which is running a cross-compiled version of
XFree86 4.3.0 on linux 2.4.18.
I noticed that XFree86, at start-up, makes a complete
scan of 256 possible PCI buses, looking for devices,
without checking (e.g. from /proc/bus/pci) how many
buses are actually present on the system.
I thought that in my system, where I have one bus
only, this could lead to a high startup time, so I
tried to make a patch (reported below) that detects
the actual number of buses by parsing
/proc/bus/pci/devices.
The results were not amazing, because the saved time
is really little.
Anyway I wanted to let you know about that. Maybe
someone can give me a feedback about the possible
drawbacks of this solution.
And, do you have other ideas of possible solutions to
speed up the XFree86 startup time on embedded systems
with limitations in filesystem speed and clock rate?
Thank you
--
Pier Paolo Glave
patch follows:
---
./xc/programs/Xserver/hw/xfree86/os-support/bus/linuxPci.c
2002-11-17 19:42:01.0 +0100
+++
./build/programs/Xserver/hw/xfree86/os-support/bus/linuxPci.c
2004-02-16 17:09:12.0 +0100
@@ -59,6 +59,7 @@
static CARD32 linuxPciCfgRead(PCITAG tag, int off);
static void linuxPciCfgWrite(PCITAG, int off, CARD32
val);
static void linuxPciCfgSetBits(PCITAG tag, int off,
CARD32 mask, CARD32 bits);
+static unsigned int linuxPciGetMaxBus(void);
static pciBusFuncs_t linuxFuncs0 = {
/* pciReadLong */ linuxPciCfgRead,
@@ -86,6 +87,7 @@
linuxPciInit()
{
struct stat st;
+ unsigned int newMaxBus;
if ((xf86Info.pciFlags == PCIForceNone) ||
(-1 == stat(/proc/bus/pci, st))) {
/* when using this as default for all linux
architectures,
@@ -96,6 +98,11 @@
pciBusInfo[0] = linuxPci0;
pciFindFirstFP = pciGenFindFirst;
pciFindNextFP = pciGenFindNext;
+ /* Get the real max bus number */
+ newMaxBus = linuxPciGetMaxBus();
+ if (newMaxBus) {
+ pciMaxBusNum = newMaxBus;
+ }
}
static int
@@ -167,6 +174,43 @@
}
}
+/*
+ * Returns the actual max number of buses present in
the system, taken
+ * from the info in /proc/bus/pci.
+ * Returns zero if something went wrong.
+ */
+static unsigned int linuxPciGetMaxBus(void)
+{
+ FILE *file;
+ char *res;
+ char c[0x200];
+ unsigned int num;
+ unsigned int bus, devfn;
+ unsigned int maxbus = 0;
+
+ if (!(file = fopen(/proc/bus/pci/devices,r)))
+ return maxbus;
+
+ do {
+ res = fgets(c,0x1ff,file);
+ if (res) {
+ num = sscanf(res,%02x%02x,bus,devfn);
+ if (num != 2) {
+ fclose(file);
+ return maxbus;
+ }
+ if (maxbus = bus) {
+ maxbus = bus+1;
+ }
+ }
+
+ } while(res);
+
+ fclose(file);
+ return maxbus;
+}
+
+
#ifndef INCLUDE_XF86_NO_DOMAIN
/*
end of patch
__
Do you Yahoo!?
Yahoo! Finance: Get your refund fast by filing online.
http://taxes.yahoo.com/filing.html
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel
Re: Printer-builtin fontpaths broken / was: Re: CVS Update: xc (branch: trunk)
On Mon, Feb 16, 2004 at 01:41:30PM +0100, Roland Mainz wrote: David Dawes wrote: CVSROOT:/home/x-cvs Module name:xc Changes by: [EMAIL PROTECTED] 04/02/11 13:11:26 Log message: 799. Some more font path checks. Modified files: xc/lib/font/fontfile/: dirfile.c encparse.c fontfile.c xc/programs/Xserver/hw/xfree86/: CHANGELOG Revision ChangesPath 3.18 +17 -1 xc/lib/font/fontfile/dirfile.c 1.20 +7 -2 xc/lib/font/fontfile/encparse.c 3.22 +30 -11xc/lib/font/fontfile/fontfile.c 3.3139+2 -1 xc/programs/Xserver/hw/xfree86/CHANGELOG David: Somehow these changes broke Xprt's handing of printer builtin fonts (e.g. font paths prefixed with PRINTER: which are enabled dynamically on per-model-config basis). Can you isolate which of the changes causes the problem by adding them in one at a time? David ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: radeon dri lockup
On 2004-02-16 09:36:22 -0600 Michel Dänzer [EMAIL PROTECTED] wrote: On Mon, 2004-02-16 at 05:45, Jonathan Isom wrote: I've got a Radeon 7000 that locks up hard on a linux 2.4.23. no logs are written requiring power cycle. It locks in Quake3 in less that 7 minutes most times. some xscreensaver work fine,but havn't tried them all If radeon_dri.so isn't at least from XFree86 4.3.0, please try a newer version. 4.3.0 doesn't lockup. 4.4.0 rc2 locks up and only when running GL. 4.4.0 runs faster though. the instability i have found is gl related. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: radeon dri lockup
On Tue, 2004-02-17 at 00:06, Jonathan Isom wrote: On 2004-02-16 09:36:22 -0600 Michel Dnzer [EMAIL PROTECTED] wrote: On Mon, 2004-02-16 at 05:45, Jonathan Isom wrote: I've got a Radeon 7000 that locks up hard on a linux 2.4.23. BTW, what about older (or 2.6) kernels or the DRM from XFree86? no logs are written requiring power cycle. It locks in Quake3 in less that 7 minutes most times. some xscreensaver work fine,but havn't tried them all If radeon_dri.so isn't at least from XFree86 4.3.0, please try a newer version. 4.3.0 doesn't lockup. 4.4.0 rc2 locks up and only when running GL. 4.4.0 runs faster though. the instability i have found is gl related. Are you using any AGP or otherwise DRI related X server options? -- Earthling Michel Dnzer | Debian (powerpc), X and DRI developer Libre software enthusiast| http://svcs.affero.net/rm.php?r=daenzer ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
cheapest sugper viagrga ! buss poke
Did you know That the normal cost for Super Vkiagra is $20, per dose? We are running a hot special!! T0DAY Its only an amazing $3.00 Shipped world wide! http://drishere.com/sv/index.php?pid=evaph6163 dank carbide
Re: radeon dri lockup
On 2004-02-16 18:34:54 -0600 Michel Dänzer [EMAIL PROTECTED] wrote: On Tue, 2004-02-17 at 00:06, Jonathan Isom wrote: On 2004-02-16 09:36:22 -0600 Michel Dänzer [EMAIL PROTECTED] wrote: On Mon, 2004-02-16 at 05:45, Jonathan Isom wrote: I've got a Radeon 7000 that locks up hard on a linux 2.4.23. BTW, what about older (or 2.6) kernels or the DRM from XFree86? I'm using DRM frm Xfree86 no logs are written requiring power cycle. It locks in Quake3 in less that 7 minutes most times. some xscreensaver work fine,but havn't tried them all If radeon_dri.so isn't at least from XFree86 4.3.0, please try a newer version. 4.3.0 doesn't lockup. 4.4.0 rc2 locks up and only when running GL. 4.4.0 runs faster though. the instability i have found is gl related. Are you using any AGP or otherwise DRI related X server options? Section Device Option Accel # [bool] Option AGPMode 2 Option EnableDepthMoves True# [bool] Option AGPFastWrite False Option HWCursor True Identifier Card0 Driver radeon VendorName ATI BoardName Radeon RV100 QY [Radeon 7000/VE] BusID PCI:1:0:0 VideoRam65536 EndSection ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
