Re: [Xpert]multi-head DVI?
Hi, On Tuesday, 19. March 2002 05:03, Andy Sparrow wrote: > Does anyone happen to know of any cards which will do DVI output @ > 1600x1200, either PCI cards (so I can fit as many as needed) or a quad-head > AGP one? > > If I'm reading their information correctly, Matrox don't do a quad-port AGP > card, and the ATI (and most other cards) top out at 1280x1024 on DVI > output... You're right, Matrox has no quad-port AGP. But they do have quad-port PCI (G200) for up to 16 monitors. regards Roland Schulz ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]4.2.0: build problem on ppc
Hi, when trying to build a static X-Server(#define DoLoadableServer NO) on Linux/PPC the final link of XFree86 fails with: cfb24/libcfb24.a(cfbglblt8.o): In function `cfbPolyGlyphBlt8Clipped': cfbglblt8.o(.text+0x910): undefined reference to `cfb8ComputeClipMasks32' cfbglblt8.o(.text+0x910): relocation truncated to fit: R_PPC_REL24 cfb8ComputeClipMasks32 cfb32/libcfb32.a(cfbglblt8.o): In function `cfbPolyGlyphBlt8Clipped': cfbglblt8.o(.text+0x690): undefined reference to `cfb8ComputeClipMasks32' cfbglblt8.o(.text+0x690): relocation truncated to fit: R_PPC_REL24 cfb8ComputeClipMasks32 cfb8ComputeClipMasks32 is defined in libcfb.a: nm libcfb.a | grep cfb8ComputeClipMasks32 U cfb8ComputeClipMasks32 01e4 T cfb8ComputeClipMasks32 The link fails cause libcfb24 references the symbol but is linked in after libcfb8: gcc -o XFree86 -O2 ... cfb/libcfb.a cfb16/libcfb16.a cfb24/libcfb24.a ... I could work around this by adding cfb/libcfb.a after libcfb24.a. Like: --- xc/programs/Xserver/Makefile.orig Mon Mar 18 17:40:43 2002 +++ xc/programs/Xserver/MakefileMon Mar 18 17:41:27 2002 @@ -909,7 +909,7 @@ MFB = mfb/libmfb.a FB = fb/libfb.a -CFB = cfb/libcfb.a cfb16/libcfb16.a cfb24/libcfb24.acfb32/libcfb32.a +CFB = cfb16/libcfb16.a cfb24/libcfb24.a +cfb32/libcfb32.a cfb/libcfb.a CFB8 = cfb/libcfb.a CFB4 = cfb/libcfb.a cfb4/libcfb4.a Someone with more clues about Imakefiles should be able to fix this easily. I further noticed that lib/GLw will not build without having X11 headers installed in /u/i/X11. At least IntrinsicP.h is missing. I'm building with "#define BuildServersOnly YES". Is this dependency on system headers intended? Do we need the GLw stuff at all for server only builds? -- Guido ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Dual Head on i830MG
Hello all,
I have bought a toshiba Satellite 3000 X11 laptop with an intel i830MG
graphic board. With Windows XP, I can use this computer in a dual-head
configuration: the laptop screen and an external screen on the vga port
can display different pictures. I would like to do the same thing with
linux.
I am using the official binaries of XFree 4.2.0, with the linux kernel
2.4.17 patched by redhat available on rawhide. Looking at the log of the
X server, I found the lines
(--) PCI:*(0:2:0) Intel i830M rev 3, Mem @ 0xe800/27, 0xe000/19
(--) PCI: (0:2:1) Intel i830M rev 0, Mem @ 0xf000/27, 0xe008/19
Does this mean that the i830MG board is like two i830M boards ? To test
this, I write in my XF86Config file:
Section "ServerLayout"
Identifier "Anaconda Configured"
Screen 0 "Screen0" 0 0
Screen 1 "Screen1" RightOf "Screen0"
InputDevice"Mouse0" "CorePointer"
InputDevice"Keyboard0" "CoreKeyboard"
EndSection
[...]
Section "Device"
Identifier "Intel 830 MG"
Driver "i810"
VendorName "Intel"
BoardName "Intel 830"
BusID "PCI:0:2:0"
EndSection
[...]
Section "Device"
Identifier "Intel 830 MG 2"
Driver "i810"
VendorName "Intel"
BoardName "Intel 830"
BusID "PCI:0:2:1"
EndSection
(And, of course, "Screen0" references "Intel 830 MG" and "Screen1"
references "Intel 830 MG 2")
Here are some selected lines of the logs:
(**) I810(0): Depth 24, (--) framebuffer bpp 32
(==) I810(0): RGB weight 888
(==) I810(0): Default visual is TrueColor
(WW) I810(0): Bad V_BIOS checksum
(II) I810(0): Primary V_BIOS segment is: 0xc000
(--) I810(0): Chipset: "i830"
(--) I810(0): Linear framebuffer at 0xE800
(--) I810(0): IO registers at addr 0xE000
(II) I810(0): detected 8192K stolen memory.
(II) I810(0): I810CheckAvailableMemory: 200700k available
(==) I810(0): Will alloc AGP framebuffer: 8192 kByte
(==) I810(0): Using gamma correction (1.0, 1.0, 1.0)
(II) I810(0): Currently active displays on Pipe A:
(II) I810(0): LFP (Local Flat Panel) child device
[...]
(II) I810(1): VESA BIOS detected
(II) I810(1): VESA VBE Version 3.0
(II) I810(1): VESA VBE Total Mem: 8000 kB
(II) I810(1): VESA VBE OEM: Almador Graphics Chip Accelerated VGA BIOS
[...]
(II) I810(0): VESA VBE DDC supported
(II) I810(0): VESA VBE DDC Level 2
(II) I810(0): VESA VBE DDC transfer in appr. 1 sec.
(II) I810(0): VESA VBE DDC read successfully
[...]
(II) Reloading /usr/X11R6/lib/modules/linux/libint10.a
(**) I810(1): Depth 24, (--) framebuffer bpp 32
(==) I810(1): RGB weight 888
(==) I810(1): Default visual is TrueColor
(EE) I810(1): Cannot read V_BIOS
(EE) I810(1): Int10 initialization failed.
And it doesn't work: I only have one screen working. So, what should I do ?
What is this V_BIOS thing ? Am I correct when I assume that the two screens
correspond to the two devices, or has the device on 0:2:1 nothing to do
with a graphic card ? What is this "Pipe A" in the log ("Currently active
displays on Pipe A:") ? Is there a "Pipe B" that I should somehow
activate ?
I am pretty much in the dark and the documentation about the i810 driver
seems a bit outdated.
I am not sure that all of you would love having my full config file and
full log, but, of course, I can send them inprivate to anyone interested.
Thank you for any help,
Éric Brunet
___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert
[Xpert]renaming ati drivers
Hi,
I want to include GATOS driver in my XFree86*.rpm and I need
to rename XFree86 ati* drivers to ati_old, r128_old,
radeon_old.
For now I've changed:
diff -urN ati.old.org/ati.c ati.old/ati.c
--- ati.old.org/ati.c Wed Mar 13 11:18:18 2002
+++ ati.old/ati.c Wed Mar 13 21:05:26 2002
@@ -90,7 +90,7 @@
DriverRec ATI =
{
ATI_VERSION_CURRENT,
-"ati",
+"ati_old",
ATIIdentify,
ATIProbe,
ATIAvailableOptions,
diff -urN ati.old.org/atimisc.c ati.old/atimisc.c
--- ati.old.org/atimisc.c Wed Mar 13 11:18:18 2002
+++ ati.old/atimisc.c Wed Mar 13 11:19:27 2002
@@ -71,7 +71,7 @@
}
/* The following record must be called atimiscModuleData */
-XF86ModuleData atimiscModuleData =
+XF86ModuleData atimisc_oldModuleData =
{
&ATIVersionRec,
ATISetup,
diff -urN ati.old.org/atimodule.c ati.old/atimodule.c
--- ati.old.org/atimodule.cWed Mar 13 11:18:18 2002
+++ ati.old/atimodule.cWed Mar 13 11:19:40 2002
@@ -116,7 +116,7 @@
}
/* The following record must be called atiModuleData */
-XF86ModuleData atiModuleData =
+XF86ModuleData ati_oldModuleData =
{
&ATIVersionRec,
ATISetup,
diff -urN ati.old.org/atiprobe.c ati.old/atiprobe.c
--- ati.old.org/atiprobe.c Wed Mar 13 11:18:44 2002
+++ ati.old/atiprobe.c Mon Mar 11 13:14:51 2002
@@ -2275,10 +2275,10 @@
#ifdef XFree86LOADER
-if (!xf86LoadSubModule(pScreenInfo, "atimisc"))
+if (!xf86LoadSubModule(pScreenInfo, "atimisc_old"))
{
xf86Msg(X_ERROR,
-ATI_NAME ": Failed to load \"atimisc\" module.\n");
+ATI_NAME ": Failed to load \"atimisc_old\" module.\n");
xf86DeleteScreen(pScreenInfo->scrnIndex, 0);
continue;
}
diff -urN ati.old.org/ativersion.h ati.old/ativersion.h
--- ati.old.org/ativersion.h Wed Mar 13 11:18:44 2002
+++ ati.old/ativersion.h Mon Mar 11 13:14:51 2002
@@ -25,7 +25,7 @@
#define ___ATIVERSION_H___ 1
#define ATI_NAME "ATI"
-#define ATI_DRIVER_NAME "ati"
+#define ATI_DRIVER_NAME "ati_old"
#define ATI_VERSION_NAME "6.4.8"
diff -urN ati.old.org/r128_misc.c ati.old/r128_misc.c
--- ati.old.org/r128_misc.cWed Mar 13 11:18:18 2002
+++ ati.old/r128_misc.cWed Mar 13 11:20:02 2002
@@ -74,7 +74,7 @@
}
/* The following record must be called r128ModuleData */
-XF86ModuleData r128ModuleData =
+XF86ModuleData r128_oldModuleData =
{
&R128VersionRec,
R128Setup,
diff -urN ati.old.org/r128_probe.c ati.old/r128_probe.c
--- ati.old.org/r128_probe.c Wed Mar 13 11:18:44 2002
+++ ati.old/r128_probe.c Mon Mar 11 13:14:51 2002
@@ -205,9 +205,9 @@
#ifdef XFree86LOADER
- if (!xf86LoadSubModule(pScrn, "r128")) {
+ if (!xf86LoadSubModule(pScrn, "r128_old")) {
xf86Msg(X_ERROR,
- R128_NAME ": Failed to load \"r128\" module.\n");
+ R128_NAME ": Failed to load \"r128_old\" module.\n");
xf86DeleteScreen(pScrn->scrnIndex, 0);
continue;
}
diff -urN ati.old.org/r128_version.h ati.old/r128_version.h
--- ati.old.org/r128_version.h Wed Mar 13 11:18:18 2002
+++ ati.old/r128_version.h Wed Mar 13 21:07:17 2002
@@ -25,7 +25,7 @@
#define _R128_VERSION_H_ 1
#define R128_NAME "R128"
-#define R128_DRIVER_NAME "r128"
+#define R128_DRIVER_NAME "r128_old"
#define R128_VERSION_NAME "4.0.1"
diff -urN ati.old.org/radeon_misc.c ati.old/radeon_misc.c
--- ati.old.org/radeon_misc.c Wed Mar 13 11:18:18 2002
+++ ati.old/radeon_misc.c Wed Mar 13 11:20:20 2002
@@ -74,7 +74,7 @@
}
/* The following record must be called radeonModuleData */
-XF86ModuleData radeonModuleData =
+XF86ModuleData radeon_oldModuleData =
{
&RADEONVersionRec,
RADEONSetup,
diff -urN ati.old.org/radeon_probe.c ati.old/radeon_probe.c
--- ati.old.org/radeon_probe.c Wed Mar 13 11:18:44 2002
+++ ati.old/radeon_probe.c Mon Mar 11 13:14:51 2002
@@ -203,9 +203,9 @@
{
#ifdef XFree86LOADER
- if (!xf86LoadSubModule(pScrn, "radeon")) {
+ if (!xf86LoadSubModule(pScrn, "radeon_old")) {
xf86Msg(X_ERROR,
- RADEON_NAME ": Failed to load \"radeon\" module.\n");
+ RADEON_NAME ": Failed to load \"radeon_old\" module.\n");
xf86DeleteScreen(pScrn->scrnIndex, 0);
continue;
}
diff -urN ati.old.org/radeon_version.h ati.old/radeon_version.h
--- ati.old.org/radeon_version.h Wed Mar 13 11:18:18 2002
+++ ati.old/radeon_version.h Wed Mar 13 21:07:52 2002
@@ -25,7 +25,7 @@
#define _RADEON_VERSION_H_ 1
#define RADEON_NAME "RADEON"
-#define RADEON_DRIVER_NAME "radeon"
+#define RADEON_DRIVER_NAME "radeon_old"
#define RADEON_VERSION_NAME "4.0.1"
[Xpert]Re: multi-head DVI?
The Radeon series with DVI output will drive 1600x1200 over the digital link. I'm using a Radeon All-in-Wonder right now at 1600x1200 DVI. You can get PCI Radeons, so I presume you could stuff a machine full of as many as you like. At least, this is how Apple used to configure a PowerMac with 4 displays. Maybe you would also like the Matrox G200 MMS, which has 4 digital or analog outputs on a single PCI card. I think they only do 1280x1024 on the digital link, but the analog is likely to look just as good if you have a quality monitor (e.g. samsung). BTW when you get this 6400x1200 monster up and running be sure to send a screen shot :) -jwb ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]problem with ATI mach64 / xpert card
Peter Surda wrote: [replying on list, just to let everyone know that fixed the problem] > There is one, turn off composite sync (just uncomment and set to off). > This was apparently an unfortunate decision in 4.2.0 that has been > reversed afterwards. thanks for that! i will notify the port maintainer as well. everything works perfectly now. sorry that i didn't search the archives in more detail; it's been a frustrating couple of days :> thanks for the quick response. -- Will Yardley input: william < @ hq . newdream . net . > ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Regarding the new 2d drivers for trident
Hi I tried the new drivers posted on alan's page together with xfree 4.2. First I don't have to use the shadowfb so dga works (very nice for movies in mplayer) and I can also change resolution in X. The only wierd thing is that it says it doesn't have enough memory to use double. I tried this with both 8mb allocated for X and 16mb. Xv works just fine, like it did with xfree 4.2. But the new thing is that games is lightning fast now :-) I can run quake2 in software mode 800x600!! Also other games that before used almost 90% cpu only use 6-7% now. Alan and all the others who helped this in any way thank you so much im s happy now :)~ My machine is a Toshiba Tecra 8200 Pentium 3 750mhz, 256mb ram with a trident xp 16mb -- Med venlig Hilsen / Sincerely Anders Rune Jensen (icq: #52926571) ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Xfree86 cross compilation troubles
Hello I have noted that only Kdrive.cf includes cross.def, does that means that only Kdrive's servers could be cross-compiled? Is there a solution to cross compil xfree86 for a loadable server? thanks, Jerome ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]4.2.0: build problem on ppc
On Mon, Mar 18, 2002 at 10:54:05AM -0700, Marc Aurele La France wrote: > On Mon, 18 Mar 2002, Guido Guenther wrote: > > > when trying to build a static X-Server(#define DoLoadableServer NO) on >Linux/PPC > > the final link of XFree86 fails with [..snip..] > > +++ xc/programs/Xserver/MakefileMon Mar 18 17:41:27 2002 > > @@ -909,7 +909,7 @@ > > > > MFB = mfb/libmfb.a > > FB = fb/libfb.a > > -CFB = cfb/libcfb.a cfb16/libcfb16.a >cfb24/libcfb24.acfb32/libcfb32.a > > +CFB = cfb16/libcfb16.a cfb24/libcfb24.a > cfb32/libcfb32.a cfb/libcfb.a > > > > CFB8 = cfb/libcfb.a > > CFB4 = cfb/libcfb.a cfb4/libcfb4.a > > > Someone with more clues about Imakefiles should be able to fix this > > easily. > > I believe this to in fact be the correct fix, although I'm a bit surprised > this doesn't show up on ix86. Maybe nobody built static servers recently, or are these autobuild for testing? -- Guido ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Trident Cyberblade/i1 Virtual Terminal Problems
After much pain I have a Trident Cyberblade/i1 working. Some things I ran into... Mouse was off set, Option "SWCursor" fixed this. Lots of 'flickering/noise' when moving windows, dropping to 16bit from 24bit fixed this. However, I still can not start X then go to vt2 then go back to vt7 w/o X basically freaking out. Its like it doesnt resync properly. The screen is black with top/bottom gnome panels showing in monochrome and having a 'decayed' effect w/o icons. I can jump to all text vt's just fine, its only when I try to come back to an X session vt that it has problems. I am attaching my Xlog and my XF86Config-4 files. I spoke some with Corba in irc.openprojects.net and he couldnt seem to find anything, and thought it was a driver issue, so asked that I post here. Any help is greatly appreciated. Many Thanks, Derek Neighbors XFree86.0.log Description: Binary data XF86Config-4 Description: Binary data
[Xpert]4.2.0: build problem on ppc
Hi, when trying to build a static X-Server(#define DoLoadableServer NO) on Linux/PPC the final link of XFree86 fails with cfb24/libcfb24.a(cfbglblt8.o): In function `cfbPolyGlyphBlt8Clipped': cfbglblt8.o(.text+0x910): undefined reference to `cfb8ComputeClipMasks32' cfbglblt8.o(.text+0x910): relocation truncated to fit: R_PPC_REL24 cfb8ComputeClipMasks32 cfb32/libcfb32.a(cfbglblt8.o): In function `cfbPolyGlyphBlt8Clipped': cfbglblt8.o(.text+0x690): undefined reference to `cfb8ComputeClipMasks32' cfbglblt8.o(.text+0x690): relocation truncated to fit: R_PPC_REL24 cfb8ComputeClipMasks32 cfb8ComputeClipMasks32 is defined in libcfb.a: nm libcfb.a | grep cfb8ComputeClipMasks32 U cfb8ComputeClipMasks32 01e4 T cfb8ComputeClipMasks32 The link fails cause libcfb24 references the symbol but is linked in after libcfb8: gcc -o XFree86 -O2 ... cfb/libcfb.a cfb16/libcfb16.a cfb24/libcfb24.a ... I could work around this by adding cfb/libcfb.a after libcfb24.a. Like: --- xc/programs/Xserver/Makefile.orig Mon Mar 18 17:40:43 2002 +++ xc/programs/Xserver/MakefileMon Mar 18 17:41:27 2002 @@ -909,7 +909,7 @@ MFB = mfb/libmfb.a FB = fb/libfb.a -CFB = cfb/libcfb.a cfb16/libcfb16.a cfb24/libcfb24.acfb32/libcfb32.a +CFB = cfb16/libcfb16.a cfb24/libcfb24.a +cfb32/libcfb32.a cfb/libcfb.a CFB8 = cfb/libcfb.a CFB4 = cfb/libcfb.a cfb4/libcfb4.a Someone with more clues about Imakefiles should be able to fix this easily. I further noticed that lib/GLw will not build without having X11 headers installed in /u/i/X11. At least IntrinsicP.h is missing. I'm building with "#define BuildServersOnly YES". Is this dependency on system headers intended? Do we need the GLw stuff at all for server only builds? -- Guido ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Problem configuring XF86, Glint and Elsa Gloria-L
I had this working previously with Xf86 3.x and thought I'd upgrade everything to XF86 4.x, I can't figure out what could be wrong so I'm pleading for help. Redhat 7.2 (latest KRUD cd), Elsa Gloria L, tried with 17 inch LCD and 17 inch CRT, most attempts result in having to kill the power, Ctrl + Alt + BackSpace/Del isn't enough. I've read most of the glint posts and tried some of the ideas there and that hasn't helped , now I'm hoping that Alan will read this and can help me out. First -scanpci from XFree86 === Probing for PCI devices (Bus:Device:Function) (0:0:0) Intel 82441FX Natoma (0:6:0) IBM 82351 pci-pci bridge (0:8:0) unknown card (0x1048/0x1511) using an unknown chipset(0x14f1/0x1034) (0:11:0) S3 ViRGE (0:11:1) 3Dlabs GLINT Delta (0:11:2) 3Dlabs GLINT 500TX (0:20:0) Compaq unknown card (0xa0f3) using an unknown chip (DeviceId 0xa0f3) from Compaq (0:20:1) Compaq unknown card (0xae33) using an unknown chip (DeviceId 0xae33) from Compaq (1:11:0) Compaq Netellignet 10/100 ProLiant (1:12:0) NCR 53c875 === Then I get a config file using XFree86 -configure. It only has the S3Virge entry in it. I add a device that attaches to the glint driver for the delta chip, and get /root/XF86Config.new === Section "ServerLayout" Identifier "XFree86 Configured" Screen 0 "Screen0" 0 0 InputDevice "Mouse0" "CorePointer" InputDevice "Keyboard0" "CoreKeyboard" EndSection Section "Files" RgbPath "/usr/X11R6/lib/X11/rgb" ModulePath "/usr/X11R6/lib/modules" FontPath "/usr/X11R6/lib/X11/fonts/misc/" FontPath "/usr/X11R6/lib/X11/fonts/Speedo/" FontPath "/usr/X11R6/lib/X11/fonts/Type1/" FontPath "/usr/X11R6/lib/X11/fonts/CID/" FontPath "/usr/X11R6/lib/X11/fonts/75dpi/" FontPath "/usr/X11R6/lib/X11/fonts/100dpi/" EndSection Section "Module" Load "dbe" Load "dri" Load "extmod" Load "glx" Load "pex5" Load "record" Load "xie" EndSection Section "InputDevice" Identifier "Keyboard0" Driver "keyboard" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "PS/2" Option "Device" "/dev/mouse" EndSection Section "Monitor" Identifier "Monitor0" VendorName "DEL" ModelName "DELL 1702FP" HorizSync 30.0 - 80.0 VertRefresh 56.0 - 76.0 EndSection Section "Device" ### Available Driver options are:- ### Values: : integer, : float, : "True"/"False", ### : "String", : " Hz/kHz/MHz" ### [arg]: arg optional #Option "slow_edodram" # [] #Option "slow_dram" # [] #Option "fast_dram" # [] #Option "fpm_vram" # [] #Option "pci_burst" # [] #Option "fifo_conservative" # [] #Option "fifo_moderate" # [] #Option "fifo_aggressive" # [] #Option "pci_retry" # [] #Option "NoAccel" # [] #Option "early_ras_precharge" # [] #Option "late_ras_precharge" # [] #Option "lcd_center" # [] #Option "set_lcdclk" # #Option "set_mclk" # #Option "set_refclk" # #Option "show_cache" # [] #Option "HWCursor" # [] #Option "SWCursor" # [] #Option "ShadowFB" # [] #Option "Rotate" # [] #Option "UseFB" # [] Identifier "Card0" Driver "s3virge" VendorName "S3" BoardName "ViRGE" BusID "PCI:0:11:0" EndSection Section "Device" Identifier "Card1" Driver "glint" VendorName "3Dlabs" BusID "PCI:0:11:1" EndSection Section "Screen" Identifier "Screen0" Device "Card1" Monitor "Monitor0" SubSection "Display" Depth 1 EndSubSection SubSection "Display" Depth 4 EndSubSection SubSection "Display" Depth 8 EndSubSection SubSection "Display" Depth 15 EndSubSection SubSection "Display" Depth 16 EndSubSection SubSection "Display" Depth 24 EndSubSection EndSection === Then when I try to run it (or in this case -probeonly... I hate the power switch) I get this log file (/var/log/XFree86.0.log) === XFree86 Version 4.1.0 (Red Hat Linux release: 4.1.0-15) / X Window System (protocol Version 11, revision 0, vendor release 6510) Release Date: 2 June 2001 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/FAQ) Build Operating System: Linux 2.4.7-0.13.1smp i686 [ELF] Build Host: stripples.devel.redhat.com Module Loader present (==) Log file: "/var/log/XFree86.0.log", Time: Mon Mar 18 12:56:24 2002 (++) Using config file: "/root/XF86Config.new" Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II)
Re: [Xpert]Dual Head on i830MG
Hi Éric!
The Linux i830 driver doesn't support dual-head displays...
> I have bought a toshiba Satellite 3000 X11 laptop with an intel i830MG
> graphic board. With Windows XP, I can use this computer in a dual-head
> configuration: the laptop screen and an external screen on the vga port
> can display different pictures. I would like to do the same thing with
> linux.
>
> I am using the official binaries of XFree 4.2.0, with the linux kernel
> 2.4.17 patched by redhat available on rawhide. Looking at the log of the
> X server, I found the lines
>
> (--) PCI:*(0:2:0) Intel i830M rev 3, Mem @ 0xe800/27, 0xe000/19
> (--) PCI: (0:2:1) Intel i830M rev 0, Mem @ 0xf000/27, 0xe008/19
>
> Does this mean that the i830MG board is like two i830M boards ? To test
> this, I write in my XF86Config file:
>
> Section "ServerLayout"
> Identifier "Anaconda Configured"
> Screen 0 "Screen0" 0 0
> Screen 1 "Screen1" RightOf "Screen0"
> InputDevice"Mouse0" "CorePointer"
> InputDevice"Keyboard0" "CoreKeyboard"
> EndSection
>
> [...]
>
> Section "Device"
> Identifier "Intel 830 MG"
> Driver "i810"
> VendorName "Intel"
> BoardName "Intel 830"
> BusID "PCI:0:2:0"
> EndSection
>
> [...]
>
> Section "Device"
> Identifier "Intel 830 MG 2"
> Driver "i810"
> VendorName "Intel"
> BoardName "Intel 830"
> BusID "PCI:0:2:1"
> EndSection
>
> (And, of course, "Screen0" references "Intel 830 MG" and "Screen1"
> references "Intel 830 MG 2")
>
> Here are some selected lines of the logs:
>
> (**) I810(0): Depth 24, (--) framebuffer bpp 32
> (==) I810(0): RGB weight 888
> (==) I810(0): Default visual is TrueColor
> (WW) I810(0): Bad V_BIOS checksum
> (II) I810(0): Primary V_BIOS segment is: 0xc000
> (--) I810(0): Chipset: "i830"
> (--) I810(0): Linear framebuffer at 0xE800
> (--) I810(0): IO registers at addr 0xE000
> (II) I810(0): detected 8192K stolen memory.
> (II) I810(0): I810CheckAvailableMemory: 200700k available
> (==) I810(0): Will alloc AGP framebuffer: 8192 kByte
> (==) I810(0): Using gamma correction (1.0, 1.0, 1.0)
> (II) I810(0): Currently active displays on Pipe A:
> (II) I810(0): LFP (Local Flat Panel) child device
> [...]
> (II) I810(1): VESA BIOS detected
> (II) I810(1): VESA VBE Version 3.0
> (II) I810(1): VESA VBE Total Mem: 8000 kB
> (II) I810(1): VESA VBE OEM: Almador Graphics Chip Accelerated VGA BIOS
> [...]
> (II) I810(0): VESA VBE DDC supported
> (II) I810(0): VESA VBE DDC Level 2
> (II) I810(0): VESA VBE DDC transfer in appr. 1 sec.
> (II) I810(0): VESA VBE DDC read successfully
> [...]
> (II) Reloading /usr/X11R6/lib/modules/linux/libint10.a
> (**) I810(1): Depth 24, (--) framebuffer bpp 32
> (==) I810(1): RGB weight 888
> (==) I810(1): Default visual is TrueColor
> (EE) I810(1): Cannot read V_BIOS
> (EE) I810(1): Int10 initialization failed.
>
> And it doesn't work: I only have one screen working. So, what should I do ?
> What is this V_BIOS thing ? Am I correct when I assume that the two screens
> correspond to the two devices, or has the device on 0:2:1 nothing to do
> with a graphic card ? What is this "Pipe A" in the log ("Currently active
> displays on Pipe A:") ? Is there a "Pipe B" that I should somehow
> activate ?
>
> I am pretty much in the dark and the documentation about the i810 driver
> seems a bit outdated.
>
> I am not sure that all of you would love having my full config file and
> full log, but, of course, I can send them inprivate to anyone interested.
>
> Thank you for any help,
>
> Éric Brunet
> ___
> Xpert mailing list
> [EMAIL PROTECTED]
> http://XFree86.Org/mailman/listinfo/xpert
--
Regards
Abraham
QOTD:
"The elder gods went to Suggoth and all I got was this lousy T-shirt."
__
Abraham vd Merwe - 2d3D, Inc.
Device Driver Development, Outsourcing, Embedded Systems
Cell: +27 82 565 4451 Snailmail:
Tel: +27 21 761 7549Block C, Antree Park
Fax: +27 21 761 7648Doncaster Road
Email: [EMAIL PROTECTED] Kenilworth, 7700
Http: http://www.2d3d.comSouth Africa
msg05005/pgp0.pgp
Description: PGP signature
Re: [Xpert]A better X mouse cursor acceleration?
On Thu, 2002-03-14 at 21:15, Michael Toomim wrote:
> Does anyone know of any programs, patches, drivers, etc. that allow for
> a better mouse cursor acceleration than what X does?
>
> The current method of multiplying the mouse's velocity by a constant
> whenever the motion exceeds a certain threshold isn't as nice and usable
> as the extremely smooth polynomial, exponential, etc. acceleration
> mechanisms that have been the standard in all the other modern windowing
> systems (windows, macos, etc.).
>
> Alternatively, does anyone know why the X mouse acceleration system
> sucks so much? :)
>
> Michael
>
> ___
> Xpert mailing list
> [EMAIL PROTECTED]
> http://XFree86.Org/mailman/listinfo/xpert
Hi,.
this is what i hacked together a year ago; it works for me,.
have a go with it
I ripped pieces of X / gpm and other sources
can't quite remember which anymore.
I fixed it up nicely once, with runtime configurablity and such
but lost the sources ;-(, and never got motivated enough to do it
again.
for the X pplz out there, this thing supports a 'dragmouse' feature
which turns the mouse movement into wheel/scroller movements when a
sertain button is pressed, trouble with this is that X doesn't support
the 2nd axis.
regards,
Peter Zijlstra
#include
#include
#include
#include
#include
#include "sensmouse.h"
inline void event_set_button( mouse_event_t * event_, int button_, bool state_) {
if ( state_)
event_->buttons |= 1 << button_;
else
event_->buttons &= ~(1 << button_);
}
inline bool event_get_button( const mouse_event_t * event_, int button_) {
return !!(event_->buttons & (1 << button_));
}
static u8 * mouse_read( mouse_dev_t * dev_, int fd_ ) {
size_t read_len = dev_->read_len;
size_t packet_pos = 0;
int rlen;
u8 * packet = dev_->packet_in ?: calloc( 2, dev_->packet_len);
while (packet) {
do {
rlen = read( fd_, packet + packet_pos, read_len);
} while ( rlen && (packet_pos += rlen) < dev_->packet_len);
if ( !rlen) {
if ( !dev_->packet_in) free( packet);
return NULL;
}
if ( (packet[0] & dev_->id[0]) == dev_->id[1] &&
(packet[1] & dev_->id[2]) == dev_->id[3])
return packet;
else {
memmove( packet, packet+1, dev_->packet_len - 1);
read_len = 1;
packet_pos--;
}
}
return NULL;
}
static bool mouse_write( mouse_dev_t * dev_, int fd_) {
return write( fd_, dev_->packet_out, dev_->packet_len) == dev_->packet_len;
}
static bool mouse_null_init( mouse_dev_t * dev_, int fd_) {
return 1;
}
static bool ps2_init( mouse_dev_t * dev_, int fd_) {
unsigned char * param = NULL;
size_t paramlen = 0;
static unsigned char s2[] = {
230, // 1:1 scaling
244, // enable mouse
243, 200, // set sampling rate, 200
232, 3, // set device resolution [0,..,3]
};
switch( dev_->proto) {
case MOUSE_PROTO_IMPS2:
{
static unsigned char s[] = { 243, 200, 243, 100, 243, 80, 242 };
param = s;
paramlen = sizeof( s);
}
break;
case MOUSE_PROTO_EXPPS2:
{
static unsigned char s[] = { 243, 200, 243, 200, 243, 80, 242 };
param = s;
paramlen = sizeof(s);
}
break;
case MOUSE_PROTO_NETPS2:
case MOUSE_PROTO_NETSCPS2:
{
static unsigned char s[] = { 232, 3, 230, 230, 230 };
param = s;
paramlen = sizeof( s);
}
break;
case MOUSE_PROTO_MMPS2:
{
static unsigned char s[] = { 230, 232, 0, 232, 3, 232, 2, 232, 1,
230, 232, 3, 232, 1, 232, 2, 232, 3 };
param = s;
paramlen = sizeof( s);
}
break;
case MOUSE_PROTO_THINKPS2:
{
static unsigned char s[] = { 243, 10, 232, 0, 243, 20, 243, 60,
243, 40, 243, 20, 243, 20, 243, 60,
243, 40, 243, 20, 243, 20 };
param = s;
paramlen = sizeof( s);
}
break;
case MOUSE_PROTO_PS2:
case MOUSE_PROTO_GLIDEPS2:
default:
break;
}
if ( param) {
write (fd_, param, paramlen);
usleep (3);
}
write (fd_, s2, sizeof (s2));
usleep (3);
tcflush (fd_, TCIFLUSH);
return 1;
}
#define RANGE( x, min, max) (((x) > (min)) && ((x) < (max)))
#define CLIP( x, min, max)\
if ( (x) < (min)) (x) = (min); \
if ( (x) > (max)) (x) = (max);
#define PS2_DECODE_MOVE( dx, dy, packet) \
dx = ((packet)[0] & 0x10) ? (int)(packet)[1] - 256 : (int)(packet)[1]; \
dy = -(((packet)[0] & 0x20) ? (int)(packet)[2] - 256 : (int)(packet)[2]);
#define PS2_ENCODE_MOVE( packet, dx, dy)\
{ \
register int _dx = dx, _dy = -dy;\
CLIP( _dx, -255, 255); \
CLIP( _dy, -255, 255); \
(packet)[0] |= (_dx < 0 ? 0x10 : 0) | (_dy < 0 ? 0x20 : 0); \
(packet)[1] = _dx;\
(packet)[2] = _dy;\
}
static mouse_event_t ps2_decode( mouse_dev_t * dev_, u8 * packet_) {
mouse_event_t event;
event.buttons = 0;
event.dz = event.dw = 0;
switch( dev_->proto) {
case MOUSE_PROTO_PS2:
{
int i;
for ( i = 0; i < 3; i++)
event_set_button( &event, i, packet_[0]
Re: [Xpert]Trident Cyberblade/i1 Virtual Terminal Problems
You need to upgrade to XFree86 4.2.0 Alan. On Mon, Mar 18, 2002 at 10:18:13PM -0700, Derek Neighbors wrote: > After much pain I have a Trident Cyberblade/i1 working. Some things I ran into... > > Mouse was off set, Option "SWCursor" fixed this. > Lots of 'flickering/noise' when moving windows, dropping to 16bit from 24bit fixed >this. > > However, I still can not start X then go to vt2 then go back to vt7 w/o X basically >freaking out. Its like it doesnt resync properly. The screen is black with >top/bottom gnome panels showing in monochrome and having a 'decayed' effect w/o icons. > > I can jump to all text vt's just fine, its only when I try to come back to an X >session vt that it has problems. > > I am attaching my Xlog and my XF86Config-4 files. I spoke some with Corba in >irc.openprojects.net and he couldnt seem to find anything, and thought it was a >driver issue, so asked that I post here. > > Any help is greatly appreciated. > > Many Thanks, > > Derek Neighbors ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]RADEONSetupForDashedLine endianess fix
Hi,
attached patch fixes a problem with dashed lines on Radeon/PPC/Linux(which for
example fixes the wrong pattern on the gnome logout screen). It's
basically stolen from the r128 driver. I have 0% knowledge about the
radeon, does this look correct?
-- Guido
--- xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_accel.c Wed Mar 20 13:51:24
2002
+++ xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_accel.c.orig Wed Mar 20
+13:51:08 2002
@@ -605,17 +605,11 @@
unsigned char *RADEONMMIO = info->MMIO;
CARD32pat = *(CARD32 *)(pointer)pattern;
-#if X_BYTE_ORDER == X_LITTLE_ENDIAN
-# define PAT_SHIFT(pat,n) pat << n
-#else
-# define PAT_SHIFT(pat,n) pat >> n
-#endif
-
switch (length) {
-case 2: pat |= PAT_SHIFT(pat,2); /* fall through */
-case 4: pat |= PAT_SHIFT(pat,4); /* fall through */
-case 8: pat |= PAT_SHIFT(pat,8); /* fall through */
-case 16: pat |= PAT_SHIFT(pat,16);
+case 2: pat |= pat << 2; /* fall through */
+case 4: pat |= pat << 4; /* fall through */
+case 8: pat |= pat << 8; /* fall through */
+case 16: pat |= pat << 16;
}
RADEONWaitForFifo(pScrn, 5);
Re: [Xpert]RADEONSetupForDashedLine endianess fix
On Mit, 2002-03-20 at 13:58, Guido Guenther wrote: > attached patch fixes a problem with dashed lines on Radeon/PPC/Linux(which for > example fixes the wrong pattern on the gnome logout screen). It's > basically stolen from the r128 driver. I have 0% knowledge about the > radeon, does this look correct? Yes, I already submitted the same plus a cleanup for r128. BTW your patch is reversed. :) -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Xinerama Problem with XFree86 4.1.0
> > On Tuesday, March 19, 2002, at 06:33 PM, Mark Vojkovich wrote: > >> On Tue, 19 Mar 2002, Josh Hogan wrote: >> >>> Hello. I've recently been trying to get the Xinerama extensions with >>> XFree86 4.1.0 (stock from Redhat 7.2 install, no updates) working. My >>> computer is a P2 233, with two video cards: >>> >>> Onboard Matrox 1064SG, on the PCI bus >>> Matrox 2064W PCI card in PCI slot >>> >>> If I use just the 1064SG onboard card, it works flawlessly. If I >>> place >>> the 2064W card in, it works flawlessly as well. So, I tried to setup >>> the Xinerama extensions. It appears that I have the configuration >>> file >>> setup properly, but here is a copy of it (The 1064 card is labeled as >>> Onboard, the 2064 is labeled as PCI) >> >> Does it work without Xinerama? From the driver's perspective >> Xinerama isn't any different from non-Xinerama multihead. I wouldn't >> expect hangs to be a Xinerama-specific problem, but they might >> be a multicard specific driver problem. > > The onboard card works fine without XInerama, but I have to remove the > 2nd PCI vid card from the machine for it to work. If I specify in the > XF86Config-4 file to use the onboard card (using BusID) it will not > start up. > > So the problem appears to lie with the driver for the 1064SG (I'm > assuming). Would upgrading to 4.2.0 help this problem? Or is there > something else I can try? Maybe using a different driver for the card > besides the "mga" driver? :) > > Thanks, > Josh > ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]RADEONSetupForDashedLine endianess fix
On Wed, Mar 20, 2002 at 02:31:44PM +0100, Michel Dänzer wrote: > On Mit, 2002-03-20 at 13:58, Guido Guenther wrote: > > > attached patch fixes a problem with dashed lines on Radeon/PPC/Linux(which for > > example fixes the wrong pattern on the gnome logout screen). It's > > basically stolen from the r128 driver. I have 0% knowledge about the > > radeon, does this look correct? > > Yes, I already submitted the same plus a cleanup for r128. I'm seeing another endianess bug with Xv. At least in 16bpp red and blue seem to be swapped. I noticed that the r128 has some endianess fixes in R128PutImage. The Radeon driver will need these too, I guess. What is the Radeon equivalent to APER_0_BIG_ENDIAN_16BPP_SWAP? > > BTW your patch is reversed. :) Argh. Another point to not do things in a hurry. -- Guido ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
RE: [Xpert]Xinerama Problem with XFree86 4.1.0
> -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf > Of Josh Hogan > Sent: Tuesday, March 19, 2002 7:25 PM > To: [EMAIL PROTECTED] > Subject: [Xpert]Xinerama Problem with XFree86 4.1.0 > > > Hello. I've recently been trying to get the Xinerama extensions with > XFree86 4.1.0 (stock from Redhat 7.2 install, no updates) working. My > computer is a P2 233, with two video cards: > > Onboard Matrox 1064SG, on the PCI bus > Matrox 2064W PCI card in PCI slot > > If I use just the 1064SG onboard card, it works flawlessly. If I place > the 2064W card in, it works flawlessly as well. So, I tried to setup > the Xinerama extensions. It appears that I have the configuration file > setup properly, but here is a copy of it (The 1064 card is labeled as > Onboard, the 2064 is labeled as PCI) The 2064W (original Millennium) has a vga enable/disable switch right on the card. You may need to change the setting. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Xinerama Problem with XFree86 4.1.0
On Wednesday, March 20, 2002, at 09:23 AM, Randall Watt wrote: > > >> -Original Message- >> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf >> Of Josh Hogan >> Sent: Tuesday, March 19, 2002 7:25 PM >> To: [EMAIL PROTECTED] >> Subject: [Xpert]Xinerama Problem with XFree86 4.1.0 >> >> >> Hello. I've recently been trying to get the Xinerama extensions with >> XFree86 4.1.0 (stock from Redhat 7.2 install, no updates) working. My >> computer is a P2 233, with two video cards: >> >> Onboard Matrox 1064SG, on the PCI bus >> Matrox 2064W PCI card in PCI slot >> >> If I use just the 1064SG onboard card, it works flawlessly. If I place >> the 2064W card in, it works flawlessly as well. So, I tried to setup >> the Xinerama extensions. It appears that I have the configuration file >> setup properly, but here is a copy of it (The 1064 card is labeled as >> Onboard, the 2064 is labeled as PCI) > > The 2064W (original Millennium) has a vga enable/disable switch right > on the > card. You may need to change the setting. > I did find the switch on the 2064W. It was set to "VGA Enable". I changed it over to "VGA Disable". When I did that, the machine booted up with the onboard card flawlessly -- the first time it's done it with the Millenium in a PCI slot :) However . . . I changed back over to my Xinerama-enabled config file and tried to start it up -- the machine then hard-locked (ssh died, no ping, etc.). So I rebooted the machine and tried to start XF86 with just the Millenium (specifying it via BusID) -- it hard-locked the machine again. I currently have the onboard 1064SG (btw, the chip itself on the MoBo reads it as a 1164SG) set in the BIOS to NOT auto-disable. Should the Millenium be set to disable or enable? Thanks again for the help :) Josh ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
RE: [Xpert]Xvfb on solaris 8 using gcc
I put #define BuildServer YES #define XVirtualFramebufferServer YES in xc/config/cf/site.def xc/config/cf/host.def xc/config/cf/sun.cf I also checked to make sure that there were no contradictory commands cd xc/config/cf/; grep -i virtualframe *; There we no defines to say NO to XVirtualFramebufferServer I then issue make World && make install but still no Xvfb. I'm not getting any errors. Why is it thing not compiling? thanks - Chuck >>> Balarama Chandra N R <[EMAIL PROTECTED]> 03/19/02 09:57PM >>> Check out for xc/config/cf files related to the OS on which you want to build, the files with *.cf extensions, maybe here the flag #define BuildVirtualFrameBuffer would be turned off with a value of "NO"and In case you need even more help look, at xc/programs/Xserver/hw/xfree86/doc for your OS related and the Functionalities related README files.. > -- > From: Chuck Pierce[SMTP:[EMAIL PROTECTED]] > Sent: Tuesday, March 19, 2002 2:36 PM > To: [EMAIL PROTECTED] > Subject: [Xpert]Xvfb on solaris 8 using gcc > > Anyone know how to get Xvfb to compile on a solaris 8 system using > gcc?? > > Here's what I am doing.. > tar -zxvf Xsource > add/edited the line to the xc/config/cf/site.def > #ifndef ProjectRoot > #define ProjectRoot /usr/local/X11R6 > #endif > #define XVirtualFramebufferServer YES > typed "make World && make install" > > Everything seems to compile and install, but there is no > /usr/local/X11R6/bin/Xvfb. > What am I missing?? > > thanks in advance. - Chuck > > ___ > Xpert mailing list > [EMAIL PROTECTED] > http://XFree86.Org/mailman/listinfo/xpert > > > DISCLAIMER: Information contained and transmitted by this E-MAIL is proprietary to MASCOT SYSTEMS LTD and is intended for use only by the individual or entity to which it is addressed, and may contain information that is privileged, confidential or exempt from disclosure under applicable law. If this is a forwarded message, the content of this E-MAIL may not have been sent with the authority of the Company. If you are not the intended recipient, an agent of the intended recipient or a person responsible for delivering the information to the named recipient, you are notified that any use, distribution, transmission, printing, copying or dissemination of this information in any way or in any manner is strictly prohibited. If you have received this communication in error, please delete this mail & notify us immediately at [EMAIL PROTECTED] Before opening attachments, "Please scan for Viruses" ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]A better X mouse cursor acceleration?
On Wed, Mar 20, 2002 at 02:42:10PM +0100, Peter Zijlstra wrote: > for the X pplz out there, this thing supports a 'dragmouse' feature > which turns the mouse movement into wheel/scroller movements when a > sertain button is pressed, trouble with this is that X doesn't support > the 2nd axis. XFree86 4 doesn't have any trouble with the 'second axis', I have my second scrollwheel sending button 6 and 7 quite nicely.. The wait now is for the toolkits to pick up on it... -- Frank v Waveren Fingerprint: 0EDB 8787 fvw@[var.cx|dse.nl|stack.nl|chello.nl] ICQ#10074100 09B9 6EF5 6425 B855 Public key: http:[EMAIL PROTECTED] 7179 3036 E136 B85D ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
RE: [Xpert]Xinerama Problem with XFree86 4.1.0
> -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf > Of Josh Hogan > Sent: Wednesday, March 20, 2002 10:54 AM > To: [EMAIL PROTECTED] > Subject: Re: [Xpert]Xinerama Problem with XFree86 4.1.0 > > > > On Wednesday, March 20, 2002, at 09:23 AM, Randall Watt wrote: > > > > > > >> -Original Message- > >> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf > >> Of Josh Hogan > >> Sent: Tuesday, March 19, 2002 7:25 PM > >> To: [EMAIL PROTECTED] > >> Subject: [Xpert]Xinerama Problem with XFree86 4.1.0 > >> > >> > >> Hello. I've recently been trying to get the Xinerama extensions with > >> XFree86 4.1.0 (stock from Redhat 7.2 install, no updates) working. My > >> computer is a P2 233, with two video cards: > >> > >> Onboard Matrox 1064SG, on the PCI bus > >> Matrox 2064W PCI card in PCI slot > >> > >> If I use just the 1064SG onboard card, it works flawlessly. If I place > >> the 2064W card in, it works flawlessly as well. So, I tried to setup > >> the Xinerama extensions. It appears that I have the configuration file > >> setup properly, but here is a copy of it (The 1064 card is labeled as > >> Onboard, the 2064 is labeled as PCI) > > > > The 2064W (original Millennium) has a vga enable/disable switch right > > on the > > card. You may need to change the setting. > > > I did find the switch on the 2064W. It was set to "VGA Enable". I > changed it over to "VGA Disable". When I did that, the machine booted > up with the onboard card flawlessly -- the first time it's done it with > the Millenium in a PCI slot :) However . . . > > I changed back over to my Xinerama-enabled config file and tried to > start it up -- the machine then hard-locked (ssh died, no ping, etc.). > So I rebooted the machine and tried to start XF86 with just the > Millenium (specifying it via BusID) -- it hard-locked the machine again. > > I currently have the onboard 1064SG (btw, the chip itself on the MoBo > reads it as a 1164SG) set in the BIOS to NOT auto-disable. Should the > Millenium be set to disable or enable? Working with onboard graphics adapters can often be a pain. If you want to use Xinerama then I believe the best option would be to enable the onboard 1064 (Mystique) and disable vga on the Millennium, but as it stands when you try to initialize the Millennium it seems to conflict with your onboard Mystique. If you haven't already you may want to try all the combinations you can between the vga switch, the onboard auto-disable settings, and the xinerama enabled config file. Make sure that the Millennium works on its own (use a different system if you have to) As a last resort you might have to try some fun things such as check for resource conflicts (shared IRQ's, overlapping memory ranges), update motherboard and graphics card bioses, etc. You could start by removing other pci/isa devices and trying the Millennium in each of the pci slots... > > Thanks again for the help :) > Josh > > ___ > Xpert mailing list > [EMAIL PROTECTED] > http://XFree86.Org/mailman/listinfo/xpert > ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Writting a Driver for LCD /Touch Screen
On Wed, Mar 20, 2002 at 06:42:43AM -0500, "Latha" <[EMAIL PROTECTED]> wrote: > I want to write an LCD / Touch Screen Driver for Xfree86. > I thought the best approach would be to see a Mouse driver of > Xfree86. But i fail to get the flow of the Xfree86 architecture. It depends on how the touch screen appears to the hardware, but in general the server opens up the device port and processes the data which flows from the pointer. If it's serial, look at how the MuTouch driver works. I've just finished code for the Semtech ScreenCoder. In the case of that device, the interface generates packets as if from a PS/2, Intellimouse PS/2, or Explorer PS/2 pointer, while merging packets from a "real" pointing device into that stream. Because of this design, I chose to extend the mouse.c code. I expect to release the patches in a day or so...now that everything works, I've been spending a little time cleaning them up. This code was developed for the ViewSonic ViewPad 1000, which is the only device I know which uses the Semtech ScreenCoder. If anyone knows of other systems using this device, and would like to check out the code, please contact me. Also, if anyone can give me an overview of how they believe calibration _should_ work, drop me a note. (At the moment, calibration is usable, but incomplete.) Randolph Bentson [EMAIL PROTECTED] ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Xinerama Problem with XFree86 4.1.0
On Wednesday, March 20, 2002, at 10:46 AM, Randall Watt wrote: > > >> -Original Message- >> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf >> Of Josh Hogan >> Sent: Wednesday, March 20, 2002 10:54 AM >> To: [EMAIL PROTECTED] >> Subject: Re: [Xpert]Xinerama Problem with XFree86 4.1.0 >> >> >> >> On Wednesday, March 20, 2002, at 09:23 AM, Randall Watt wrote: >> >>> >>> -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Josh Hogan Sent: Tuesday, March 19, 2002 7:25 PM To: [EMAIL PROTECTED] Subject: [Xpert]Xinerama Problem with XFree86 4.1.0 Hello. I've recently been trying to get the Xinerama extensions with XFree86 4.1.0 (stock from Redhat 7.2 install, no updates) working. My computer is a P2 233, with two video cards: Onboard Matrox 1064SG, on the PCI bus Matrox 2064W PCI card in PCI slot If I use just the 1064SG onboard card, it works flawlessly. If I place the 2064W card in, it works flawlessly as well. So, I tried to setup the Xinerama extensions. It appears that I have the configuration file setup properly, but here is a copy of it (The 1064 card is labeled as Onboard, the 2064 is labeled as PCI) >>> >>> The 2064W (original Millennium) has a vga enable/disable switch right >>> on the >>> card. You may need to change the setting. >>> >> I did find the switch on the 2064W. It was set to "VGA Enable". I >> changed it over to "VGA Disable". When I did that, the machine booted >> up with the onboard card flawlessly -- the first time it's done it with >> the Millenium in a PCI slot :) However . . . >> >> I changed back over to my Xinerama-enabled config file and tried to >> start it up -- the machine then hard-locked (ssh died, no ping, etc.). >> So I rebooted the machine and tried to start XF86 with just the >> Millenium (specifying it via BusID) -- it hard-locked the machine >> again. >> >> I currently have the onboard 1064SG (btw, the chip itself on the MoBo >> reads it as a 1164SG) set in the BIOS to NOT auto-disable. Should the >> Millenium be set to disable or enable? > > Working with onboard graphics adapters can often be a pain. If you want > to > use Xinerama then I believe the best option would be to enable the > onboard > 1064 (Mystique) and disable vga on the Millennium, but as it stands > when you > try to initialize the Millennium it seems to conflict with your onboard > Mystique. If you haven't already you may want to try all the > combinations > you can between the vga switch, the onboard auto-disable settings, and > the > xinerama enabled config file. Make sure that the Millennium works on > its own > (use a different system if you have to) > > As a last resort you might have to try some fun things such as check for > resource conflicts (shared IRQ's, overlapping memory ranges), update > motherboard and graphics card bioses, etc. > You could start by removing other pci/isa devices and trying the > Millennium > in each of the pci slots... > I'm working with the cards now, trying them in different enable/disable modes. I'm afraid I'm going to have to play around with shared IRQ's and overlapping memory ranges. I believe (looking at /proc/pci) I've got a memory overlap, but I'm not sure. Is there anyway to hard-set these in a config file somewhere? I only have two PCI slots in the machine, one for the Enet card, one for the vid card. I suppose I might just see if I can find another video card somewhere else :) Thanks again for your help Randall :) Josh ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]RADEONSetupForDashedLine endianess fix
On Wed, 20 Mar 2002, Guido Guenther wrote: > I'm seeing another endianess bug with Xv. At least in 16bpp red and > blue seem to be swapped. I noticed that the r128 has some endianess > fixes in R128PutImage. The Radeon driver will need these too, I guess. > What is the Radeon equivalent to APER_0_BIG_ENDIAN_16BPP_SWAP? You can turn off framebuffer swapping by clearing the SURFACE_CNTL bits, or you can swap the data in CopyData(). Ofcourse, the first one being quicker. ani ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]A better X mouse cursor acceleration?
Peter Zijlstra wrote: > Hi,. > > this is what i hacked together a year ago; it works for me,. > > have a go with it > > I ripped pieces of X / gpm and other sources > can't quite remember which anymore. > > I fixed it up nicely once, with runtime configurablity and such > but lost the sources ;-(, and never got motivated enough to do it > again. > > for the X pplz out there, this thing supports a 'dragmouse' feature > which turns the mouse movement into wheel/scroller movements when a > sertain button is pressed, trouble with this is that X doesn't support > the 2nd axis. > > regards, > > Peter Zijlstra Thanks for sharing this, Peter. Could you give a brief overview of what it does differently from the current code? Michael ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Radeon Xvideo endianes fix [was Re: [Xpert]RADEONSetupForDashedLine endianess fix]
On Wed, Mar 20, 2002 at 11:04:47AM -0800, Ani Joshi wrote:
>
>
> On Wed, 20 Mar 2002, Guido Guenther wrote:
>
> > I'm seeing another endianess bug with Xv. At least in 16bpp red and
> > blue seem to be swapped. I noticed that the r128 has some endianess
> > fixes in R128PutImage. The Radeon driver will need these too, I guess.
> > What is the Radeon equivalent to APER_0_BIG_ENDIAN_16BPP_SWAP?
>
>
> You can turn off framebuffer swapping by clearing the SURFACE_CNTL bits,
> or you can swap the data in CopyData(). Ofcourse, the first one being
> quicker.
Cool, thanks. That was exactly what I was looking for. Video looks
correct now in 16 and 24bpp. Patch attached and bcc'ed to
[EMAIL PROTECTED]
-- Guido
--- xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_video.c.orig Wed Mar 20
21:14:04 2002
+++ xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_video.c Wed Mar 20 21:17:12
+2002
@@ -761,9 +761,24 @@
s3offset = tmp;
}
nlines = yb + 0x) >> 16) + 1) & ~1) - top;
+ {
+
+#if X_BYTE_ORDER == X_BIG_ENDIAN
+ unsigned char *RADEONMMIO = info->MMIO;
+ CARD32 surface_cntl;
+
+ surface_cntl = INREG(RADEON_SURFACE_CNTL);
+ OUTREG(RADEON_SURFACE_CNTL, (surface_cntl |
+ RADEON_NONSURF_AP0_SWP_32BPP) & ~RADEON_NONSURF_AP0_SWP_16BPP);
+#endif
RADEONCopyMungedData(buf + (top * srcPitch) + left, buf + s2offset,
buf + s3offset, dst_start, srcPitch, srcPitch2,
dstPitch, nlines, npixels);
+#if X_BYTE_ORDER == X_BIG_ENDIAN
+ /* restore byte swapping */
+ OUTREG(RADEON_SURFACE_CNTL, surface_cntl);
+#endif
+ }
break;
case FOURCC_UYVY:
case FOURCC_YUY2:
Re: [Xpert][PATCH]: XftFreetype.h missing typedef struct onXftFontStruct
On Tue, 19 Mar 2002, Shawn Starr wrote:
> After using a recent CVS snapshot GTK+'s pango failed to configure
> properly with errors:
> configure: WARNING: X11/Xft/XftFreetype.h: present but cannot be compiled.
> configure: WARNING: X11/Xft/XftFreetype.h: check for missing prerequisite headers?
> configure: WARNING: X11/Xft/XftFreetype.h: proceeding with the preprocessor's result
> Error in config.log:
> In file included from configure:16193:
> /usr/X11R6/include/X11/Xft/XftFreetype.h:77: parse error before '*' token
> /usr/X11R6/include/X11/Xft/XftFreetype.h:78: warning: type defaults to `int' in
>declaration of `XftFreeTypeOpen'
> Solution: Add typedef struct, error gone.
> Patch below:
> --- XftFreetype.h.old Tue Mar 19 23:36:27 2002
> +++ XftFreetype.h Tue Mar 19 23:28:10 2002
> @@ -57,6 +57,8 @@ struct _XftFontStruct {
>
> _XFUNCPROTOBEGIN
>
> +typedef struct _XftFontStruct XftFontStruct;
> +
> /* xftdir.c */
> Bool
> XftDirScan (XftFontSet *set, const char *dir, Bool force);
As of just over a month ago, this change is no longer needed.
Marc.
+--+---+
| Marc Aurele La France | work: 1-780-492-9310 |
| Computing and Network Services | fax:1-780-492-1729 |
| 352 General Services Building | email: [EMAIL PROTECTED] |
| University of Alberta +---+
| Edmonton, Alberta | |
| T6G 2H1 | Standard disclaimers apply|
| CANADA | |
+--+---+
XFree86 Core Team member. ATI driver and X server internals.
___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert][PATCH]: XftFreetype.h missing typedef struct on XftFontStruct
Shawn Starr <[EMAIL PROTECTED]> writes:
> After using a recent CVS snapshot GTK+'s pango failed to configure
> properly with errors:
>
> configure: WARNING: X11/Xft/XftFreetype.h: present but cannot be compiled.
> configure: WARNING: X11/Xft/XftFreetype.h: check for missing prerequisite headers?
> configure: WARNING: X11/Xft/XftFreetype.h: proceeding with the preprocessor's result
>
> Error in config.log:
>
> In file included from configure:16193:
> /usr/X11R6/include/X11/Xft/XftFreetype.h:77: parse error before '*' token
> /usr/X11R6/include/X11/Xft/XftFreetype.h:78: warning: type defaults to `int' in
>declaration of `XftFreeTypeOpen'
>
>
> Solution: Add typedef struct, error gone.
>
> Shawn.
>
>
> Patch below:
>
>
> --- XftFreetype.h.old Tue Mar 19 23:36:27 2002
> +++ XftFreetype.h Tue Mar 19 23:28:10 2002
> @@ -57,6 +57,8 @@ struct _XftFontStruct {
>
> _XFUNCPROTOBEGIN
>
> +typedef struct _XftFontStruct XftFontStruct;
> +
> /* xftdir.c */
> Bool
> XftDirScan (XftFontSet *set, const char *dir, Bool force);
Pango's Xft support simply doesn't work with current XFree86 CVS which
has a substantially different version of Xft (version 2) from the one that
Pango expects.
Keith has some patches to get it working, see:
http://mail.gnome.org/archives/gtk-devel-list/2002-February/msg00321.html
I hope to work on integrating them into Pango CVS within the next few
weeks.
Regards,
Owen
___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert][PATCH]: XftFreetype.h missing typedef struct on XftFontStruct
Around 18 o'clock on Mar 20, Owen Taylor wrote: > Pango's Xft support simply doesn't work with current XFree86 CVS which > has a substantially different version of Xft (version 2) from the one that > Pango expects. > > Keith has some patches to get it working, see: Note that the intent of my patch is to permit Pango to compile against either version of the source; the new Xft version is largely source compatible. The patch is larger than strictly necessary mostly because Pango has quite a bit of code to work around deficiencies in the old Xft library that have been fixed in the new version. Keith PackardXFree86 Core TeamCompaq Cambridge Research Lab ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]RADEONSetupForDashedLine endianess fix
On Mit, 2002-03-20 at 15:51, Guido Guenther wrote: > > > > BTW your patch is reversed. :) > Argh. Another point to not do things in a hurry. Yep, and to use CVS. :) You also missed the CP case. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: Radeon Xvideo endianes fix [was Re:[Xpert]RADEONSetupForDashedLine endianess fix]
On Mit, 2002-03-20 at 21:34, Guido Guenther wrote:
> + {
> +
> +#if X_BYTE_ORDER == X_BIG_ENDIAN
> + unsigned char *RADEONMMIO = info->MMIO;
> + CARD32 surface_cntl;
> +
> + surface_cntl = INREG(RADEON_SURFACE_CNTL);
> + OUTREG(RADEON_SURFACE_CNTL, (surface_cntl |
> + RADEON_NONSURF_AP0_SWP_32BPP) & ~RADEON_NONSURF_AP0_SWP_16BPP);
> +#endif
> RADEONCopyMungedData(buf + (top * srcPitch) + left, buf + s2offset,
> buf + s3offset, dst_start, srcPitch, srcPitch2,
> dstPitch, nlines, npixels);
> +#if X_BYTE_ORDER == X_BIG_ENDIAN
> + /* restore byte swapping */
> + OUTREG(RADEON_SURFACE_CNTL, surface_cntl);
> +#endif
> + }
> break;
> case FOURCC_UYVY:
> case FOURCC_YUY2:
Mr. Joshi doesn't like this even in r128, and I agree it would probably
be cleaner to set up a surface with byte swapping disabled for the
overlay. Benjamin Herrenschmidt may alreay have code for that.
--
Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer
XFree86 and DRI project member / CS student, Free Software enthusiast
___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Clarification on "X" event sequence for window-handling
Hello, I am currently involved in an effort to make the Sawfish Window Manager multihead-aware. In this regard, I am facing a show-stopper, wherein the window of an application [ say xterm ], appears on the second screen, without the frame around it, whereas the client-window appearing on the DefaultScreen has it's frame appropriately generated. The Client-window is able to receive appropriate events and assumes focus upon a ButtonPress. Moving the cursor from one screen to another is also generating the necessary events of EnterNotify & LeaveNotify. The sequence of X events that occur in the normal case of the appearance of a client-window on the Default Screen [alongwith the frame around it ] is : FocusIn---> MapNotify ---> VisibilityNotify---> Expose event. But, in the case of a client-window appearing on the second screen, the client-window does not get the frame owing to the following sequence of events : FocusIn---> MapNotify --->VisibilityNotify--->FocusOut The above sequence in the second case is suspected to be the cause of my problem. Upon reading through the "X" library calls, it becomes evident that Windows which have "InputOnly" class will not respond to Expose events. Moreover, the border-width in XCreateWindow is supposed to be zero for InputOnly windows. Sawfish uses both classes while using XCreateWindow, but uses border-width of '0' always. Could anyone shed some light on the "X" perspective of this problem. The manner in which appropriate window-creation flags have to be dealt with, hold the key to this problem. - Would be glad to hear some clarifications/solutions/opinions. - Thank you very much Shobhit Mathur **Disclaimer Information contained in this E-MAIL being proprietary to Wipro Limited is 'privileged' and 'confidential' and intended for use only by the individual or entity to which it is addressed. You are notified that any use, copying or dissemination of the information contained in the E-MAIL in any manner whatsoever is strictly prohibited.
[Xpert]HP omnibook 510 + intel 830 = unsupported
Hi all, I try to install linux on this portable (kernel 2.4.18, XFree 4.2) but seems that there is a problem with the detected memory. XFree supports i830 but this chipset uses part of ram memory as video memory. At the boot time the bios assign automatically 1024k of video memory and this the maximum accessible by the linux driver (detected 1024k of stolen memory). The main problem is the restricted number of video mode available. Any one of you have some idea on how to solve this problem? Livio ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert][PATCH]: XftFreetype.h missing typedef struct onXftFontStruct
I see, This patch will fix a bug though in the header ;)
I'll check that thread, thanks.
Shawn.
On Wed, 20 Mar 2002, Owen Taylor wrote:
>
> Shawn Starr <[EMAIL PROTECTED]> writes:
>
> > After using a recent CVS snapshot GTK+'s pango failed to configure
> > properly with errors:
> >
> > configure: WARNING: X11/Xft/XftFreetype.h: present but cannot be compiled.
> > configure: WARNING: X11/Xft/XftFreetype.h: check for missing prerequisite headers?
> > configure: WARNING: X11/Xft/XftFreetype.h: proceeding with the preprocessor's
>result
> >
> > Error in config.log:
> >
> > In file included from configure:16193:
> > /usr/X11R6/include/X11/Xft/XftFreetype.h:77: parse error before '*' token
> > /usr/X11R6/include/X11/Xft/XftFreetype.h:78: warning: type defaults to `int' in
>declaration of `XftFreeTypeOpen'
> >
> >
> > Solution: Add typedef struct, error gone.
> >
> > Shawn.
> >
> >
> > Patch below:
> >
> >
> > --- XftFreetype.h.old Tue Mar 19 23:36:27 2002
> > +++ XftFreetype.h Tue Mar 19 23:28:10 2002
> > @@ -57,6 +57,8 @@ struct _XftFontStruct {
> >
> > _XFUNCPROTOBEGIN
> >
> > +typedef struct _XftFontStruct XftFontStruct;
> > +
> > /* xftdir.c */
> > Bool
> > XftDirScan (XftFontSet *set, const char *dir, Bool force);
>
> Pango's Xft support simply doesn't work with current XFree86 CVS which
> has a substantially different version of Xft (version 2) from the one that
> Pango expects.
>
> Keith has some patches to get it working, see:
>
> http://mail.gnome.org/archives/gtk-devel-list/2002-February/msg00321.html
>
> I hope to work on integrating them into Pango CVS within the next few
> weeks.
>
> Regards,
> Owen
> ___
> Xpert mailing list
> [EMAIL PROTECTED]
> http://XFree86.Org/mailman/listinfo/xpert
>
>
___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert][PATCH]: XftFreetype.h missing typedef struct on XftFontStruct
just curious? why have we seperated the xft code and put it under the pango directory itself? one of the reasons where i think it will be useful is when people are using xfree86 3.x series but as such pango checks for the XftConfig file which will be present only with xfree86 4.1.x and later versions ( am i right on this?) so why cant we use the Xft library which come bundled along with xfree86 rather than compiling pango seperately. since this discussion happened over here i am posting it here, i guess i should take this discussion on the gtk development list. regards bharat - Original Message - From: "Keith Packard" <[EMAIL PROTECTED]> To: "Owen Taylor" <[EMAIL PROTECTED]> Cc: "Shawn Starr" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; "Keith Packard" <[EMAIL PROTECTED]> Sent: Thursday, March 21, 2002 4:58 AM Subject: Re: [Xpert][PATCH]: XftFreetype.h missing typedef struct on XftFontStruct > > Around 18 o'clock on Mar 20, Owen Taylor wrote: > > > Pango's Xft support simply doesn't work with current XFree86 CVS which > > has a substantially different version of Xft (version 2) from the one that > > Pango expects. > > > > Keith has some patches to get it working, see: > > Note that the intent of my patch is to permit Pango to compile against > either version of the source; the new Xft version is largely source > compatible. The patch is larger than strictly necessary mostly because > Pango has quite a bit of code to work around deficiencies in the old Xft > library that have been fixed in the new version. > > Keith PackardXFree86 Core TeamCompaq Cambridge Research Lab > > > ___ > Xpert mailing list > [EMAIL PROTECTED] > http://XFree86.Org/mailman/listinfo/xpert **Disclaimer Information contained in this E-MAIL being proprietary to Wipro Limited is 'privileged' and 'confidential' and intended for use only by the individual or entity to which it is addressed. You are notified that any use, copying or dissemination of the information contained in the E-MAIL in any manner whatsoever is strictly prohibited.
Re: [Xpert][PATCH]: XftFreetype.h missing typedef struct on XftFontStruct
"bharat tewari" <[EMAIL PROTECTED]> writes: > just curious? why have we seperated the xft code and put it under the pango > directory itself? one of the reasons where i think it will be useful is when > people are using xfree86 3.x series but as such pango checks for the > XftConfig file which will be present only with xfree86 4.1.x and later > versions ( am i right on this?) so why cant we use the Xft library which > come bundled along with xfree86 rather than compiling pango seperately. > since this discussion happened over here i am posting it here, i guess i > should take this discussion on the gtk development list. Pango-1.0 uses Xft code in two different places: - The Xft backend compiles against the system copy of Xft if the system has Xft, and is not built otherwise. - the FT2 backend (which is used for rendering independent of X on all systems) uses a portion of Xft separated out as "MiniXft" for handling font configuration. This setup is designed so that if you have Xft on your system, the two backends share a single configuration file. If you don't have Xft installed then you would have to create an XftConfig file specifically for the FT2 backend, but this is no worse than if the FT2 backends configuration file was called pangoft2.aliases and custom contents. For Pango-1.2, I need to decide between: - Keeping MiniXft/Xft1 support and adding in addition support for new fontconfig library (the official version of MiniXft) and for Xft2. - Require fontconfig and Xft2 for all installations of Pango that want to use the backends. (fontconfig is independent of X, Xft2 supports servers without the RENDER extension.) This would clean up the code a _lot_ and make it a easier to share memory between the two backends, but on the other hand adds yet one dependency to an an already complex build process. Regards, Owen ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert][PATCH]: XftFreetype.h missing typedef struct on XftFontStruct
Around 23 o'clock on Mar 20, Owen Taylor wrote: > - Require fontconfig and Xft2 for all installations of Pango that >want to use the backends. (fontconfig is independent of X, Xft2 >supports servers without the RENDER extension.) This would clean up >the code a _lot_ and make it a easier to share memory between the >two backends, but on the other hand adds yet one dependency to an >an already complex build process. Note that Xft1 now uses fontconfig as well, but still requires the Render extension (I can't fix that in a binary compatible way). This will make MiniXft a configuration liability once this version of Xft1 becomes widely available. If it would help, I can release both Xfts and Fontconfig sooner than XFree86 4.3. That would give distributions a chance to integrate them into build processes along with Gtk+ 2.x as needed. Keith PackardXFree86 Core TeamCompaq Cambridge Research Lab ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Re: Acceleration not working S3 Virge MX
Many thanks to Fred Heitkamp! Although his suggestion did not work verbatim on my machine, I got the idea and experimented with partial turning off of the acceleration. (I was unaware of these possibilities.) It turns out that the one and only adjustment I need to do is to add Option "XaaNoOffscreenPixmaps" to my XF86Config file, in the "Device" section. By the way, it turns out that the pixel corruption at the KDE logo does not occur at all with the latest version of Xfree. So as far as my machine (and experience with it) is concerned, the above line is only necessary to avoid pixel clouds when turning on the grid in xfig. I also took a closer look at these pixel clouds. They come in neat parallel horizontal strips, so it looks very much as if something xfig is trying to do would work vertically but not horizontally. I wonder whether this is an issue of my video card, or the driver. Under Windows I never had to turn down the acceleration, even when I run touchy programs like Civilization 3. So I would think, this may be a driver issue. Best regards, Gabor Hetyei Mathematics Department Phone: (704) 687-2543 UNC Charlotte Fax: (704) 687-6415 Charlotte NC 28223-0001 E-mail: [EMAIL PROTECTED] Office: 335FWebpage: www.math.uncc.edu/~ghetyei ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Writting a Driver for LCD /Touch Screen
> Latha wrote: > > Hi, > I want to write an LCD / Touch Screen Driver for Xfree86. > I thought the best approach would be to see a Mouse driver of Xfree86. > But i fail to get the flow of the Xfree86 architecture. It is very disorganized at this time. There are no documents on it's current state, and it still has not stabilized from major 4.0 changes. Do not follow the mouse or keyboard. They are very stable, but special cases and complex. > > I am not able to get the entry points and the interface between the X and >linux-kernel. The only interface to the kernel is opening a serial I/O port. If it is USB, you will need some updates to the server code first. > > Can anyone tell where do i start about with this... > Start from the current CVS code, and find another touchscreen driver with the most recent source code changes -- it will be most likely to be up to date. Not all drivers are. After hacking on this for a bit, send me some Email for further advice. Joe Krahn ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Writting a Driver for LCD /Touch Screen
Hi, I want to write an LCD / Touch Screen Driver for Xfree86. I thought the best approach would be to see a Mouse driver of Xfree86. But i fail to get the flow of the Xfree86 architecture. I am not able to get the entry points and the interface between the X and linux-kernel. Can anyone tell where do i start about with this... thanks latha **Disclaimer Information contained in this E-MAIL being proprietary to Wipro Limited is 'privileged' and 'confidential' and intended for use only by the individual or entity to which it is addressed. You are notified that any use, copying or dissemination of the information contained in the E-MAIL in any manner whatsoever is strictly prohibited.
Re: [Xpert]Writting a Driver for LCD /Touch Screen
there is already a document on the XFree86 architecture and how the driver is written inside the source tree. I have forgotten the path but that is the best place to start. regards bharat Content-Type: multipart/alternative; boundary="=_NextPart_000_00EF_01C1CE86.3A313F10" --=_NextPart_000_00EF_01C1CE86.3A313F10 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, I want to write an LCD / Touch Screen Driver for Xfree86.=20 I thought the best approach would be to see a Mouse driver of Xfree86. But i fail to get the flow of the Xfree86 architecture. I am not able to get the entry points and the interface between the X = and linux-kernel.=20 Can anyone tell where do i start about with this... thanks latha --=_NextPart_000_00EF_01C1CE86.3A313F10 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, I want to write an LCD / Touch = Screen=20 Driver for Xfree86. I thought the best approach would be to see a Mouse = driver of=20 Xfree86. But i fail to get the flow of the Xfree86=20 architecture. I am not able to get the entry points and the = interface=20 between the X and linux-kernel. Can anyone tell where do i start about with=20 this... thanks latha --=_NextPart_000_00EF_01C1CE86.3A313F10-- **Disclaimer Information contained in this E-MAIL being proprietary to Wipro Limited is 'privileged' and 'confidential' and intended for use only by the individual or entity to which it is addressed. You are notified that any use, copying or dissemination of the information contained in the E-MAIL in any manner whatsoever is strictly prohibited.
