Re: XFree86 driver
Thanks, Marc. Is there no way in which socket() system call and other socket related API be implemented in a XFree86 input driver? When I try to implement the same, while loading the driver module the XFree86 module loader gives Unresolved symbol for each of the functions. Even dlopen() cannot be used as it results in the same error. Could you provide any way to resolve the above issue, as we would like the driver to take input from socket (i.e. from a remote touchscreen). Thank you. Marc Aurele La France [EMAIL PROTECTED] wrote: On Sat, 9 Jun 2007, Pankaj S wrote: Has anyone implemented sockets in an XFree86 input driver? Please let me know. Not to my knowledge. Marc. +--+--+ | Marc Aurele La France | work: 1-780-492-9310 | | Academic Information and | fax: 1-780-492-1729 | | Communications Technologies | email: [EMAIL PROTECTED] | | 352 General Services Building +--+ | University of Alberta | | | Edmonton, Alberta | Standard disclaimers apply | | T6G 2H1 | | | CANADA | | +--+--+ XFree86 developer and VP. ATI driver and X server internals. ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel - Choose the right car based on your needs. Check out Yahoo! Autos new Car Finder tool.
Re: XFree86 driver
On Mon, 11 Jun 2007, Pankaj S wrote: Thanks, Marc. Is there no way in which socket() system call and other socket related API be implemented in a XFree86 input driver? When I try to implement the same, while loading the driver module the XFree86 module loader gives Unresolved symbol for each of the functions. Even dlopen() cannot be used as it results in the same error. Modules are deliberately only allowed to call a restricted list of system calls which are known to work (the same way ?) on (all ?) operating systems that XFree86 runs on. The idea is (or at least was) that *binary* modules could be built on one OS and run on any other. dlopen() is definitely not allowed and I don't think that system() is either. To add a system call you would need to add them to every server that your module is to work with. *If* you were to do that it would be best to collaborate with Xorg as well as XFree86. Could you provide any way to resolve the above issue, as we would like the driver to take input from socket (i.e. from a remote touchscreen). x2x ( ftp://gatekeeper.dec.com/pub/DEC/SRC/x2x/x2x-1.27.tar.gz ) uses the XTEST extension to drive the input of a remote X display. Could you run something on the machine with the touchscreen which uses XTEST to send data to the display you were writing an input driver for ? ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel
Re: [XFree86] Driver issue.
On Tue, 5 Jun 2007, Lucio Lastra wrote: I don't see my graphic card driver listed. The graphic card is onboard on a DG945GTP Intel motherboard. It's based on the Intel 945G Express Chipset. http://www.intel.com/products/chipsets/945g/index.htm - My questions are: ¿ Is the chipset backward compatible so i can run the i8xx driver ? If not, ¿ Which driver do you recommend ? ¿ Is it possible at all to configure XFree86 in this motherboard ? The driver appears to support the 945G, so it should work right out of the box. Marc. +--+--+ | Marc Aurele La France | work: 1-780-492-9310 | | Academic Information and| fax:1-780-492-1729 | |Communications Technologies | email: [EMAIL PROTECTED] | | 352 General Services Building +--+ | University of Alberta | | | Edmonton, Alberta |Standard disclaimers apply| | T6G 2H1 | | | CANADA | | +--+--+ XFree86 developer and VP. ATI driver and X server internals.
Re: XFree86 driver for touchscreen
Hi Pankaj, I was looking for the same online. These are some of the documents that I found. http://www.msu.edu/~huntharo/xwin/docs/xwindows/strat.pdfhttp://www.msu.edu/%7Ehuntharo/xwin/docs/xwindows/strat.pdf http://www.msu.edu/~huntharo/xwin/docs/xwindows/ddx.pdfhttp://www.msu.edu/%7Ehuntharo/xwin/docs/xwindows/ddx.pdf http://www.xfree86.org/current/specindex.html Although the documents are kinda out dated .. they give a certain direction to work on! @ Others ... If I am wrong please correct me! :) Regards Vishal On 4/24/07, Pankaj S [EMAIL PROTECTED] wrote: Hi, I need to develop a XFree86 driver for a touchscreen. There is no driver for this touchscreen in XFree86 nor in Linux. All I have is: 1. The hardware touchscreen controller's protocol document 2. The source code of other touch screen drivers ELO and 3M. The only documentation we've been able to find for this sort of thing is the actual XFree86 source code. Can anyone tell me how I could get started with the XFree86 driver development. Or, any suggestions on which website or book to refer to is most welcome. Thanks. pankaj. -- Ahhh...imagining that irresistible new car smell? Check out new cars at Yahoo! Autos.http://us.rd.yahoo.com/evt=48245/*http://autos.yahoo.com/new_cars.html;_ylc=X3oDMTE1YW1jcXJ2BF9TAzk3MTA3MDc2BHNlYwNtYWlsdGFncwRzbGsDbmV3LWNhcnM- -- Regards, Vishal Sagar Mob - 09860154127 I don't want to be a product of my environment. I want my environment to be a product of me.
Re: [XFree86] Driver H/W init delay
Thank you for usuful advices. Things like getting monitor information through DDC take a long time. Also, because clocks are being set there are PLL settling times that need to be observed least you mess things up by touching the hardware before the PLLs lock. I have heard about this issue, but, in my env, doing DDC probe is very fast. It is done instantaneously. Is DDC really a cause? It may be that particular drivers have unnecessary waits here and there, but you really have to address them one by one, profiling to find the wait and then investigating whether or not it's really necessary. Then, the VESA driver of current XFree86 has unnecessary waits? If so, I will try to get rid of. But, as far as I have glanced the code, it just does call a VESA BIOS and it is all it does. So, even there are unnecessary waits, they seems to be in a BIOS code, I suppose. I have worked on systems with boot times times on the order of a few seconds but these weren't trying to access VESA bios services or probing monitors through DDC. If you remove stuff like that, the boot times will probably be dominated by IDE probing, but then you end up having to hardcode things like monitor EDIDs that the driver would usually try to probe. Well, in MACH BOOT, it is possible to hard-code IDE params, because most PCs has same param. But not possible to hard-code DDC (EDID or...) because there are so many kind of monitor. Any idea? --- Okajima, Jun. Tokyo, Japan. http://www.digitalinfra.co.jp/ http://www.machboot.com/ ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Driver H/W init delay
On Tue, 30 May 2006, Jun OKAJIMA wrote: Thank you for usuful advices. Things like getting monitor information through DDC take a long time. Also, because clocks are being set there are PLL settling times that need to be observed least you mess things up by touching the hardware before the PLLs lock. I have heard about this issue, but, in my env, doing DDC probe is very fast. It is done instantaneously. Is DDC really a cause? It may be that particular drivers have unnecessary waits here and there, but you really have to address them one by one, profiling to find the wait and then investigating whether or not it's really necessary. Then, the VESA driver of current XFree86 has unnecessary waits? If so, I will try to get rid of. But, as far as I have glanced the code, it just does call a VESA BIOS and it is all it does. So, even there are unnecessary waits, they seems to be in a BIOS code, I suppose. I have worked on systems with boot times times on the order of a few seconds but these weren't trying to access VESA bios services or probing monitors through DDC. If you remove stuff like that, the boot times will probably be dominated by IDE probing, but then you end up having to hardcode things like monitor EDIDs that the driver would usually try to probe. Well, in MACH BOOT, it is possible to hard-code IDE params, because most PCs has same param. But not possible to hard-code DDC (EDID or...) because there are so many kind of monitor. Any idea? You really just need to profile it and find where all the time is spent. If the video BIOS is doing all the initialization then it's likely that all the waiting is done there. It's undoubtedly all the monitor probing and clock setting and the associated delays and timeouts related to that. If the video card has multiple connectors it will probably be looking for devices on all connectors and trying that until it's convinced that it has found them all. Mark. ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Driver H/W init delay
Things like getting monitor information through DDC take a long time. Also, because clocks are being set there are PLL settling times that need to be observed least you mess things up by touching the hardware before the PLLs lock. It may be that particular drivers have unnecessary waits here and there, but you really have to address them one by one, profiling to find the wait and then investigating whether or not it's really necessary. I have worked on systems with boot times times on the order of a few seconds but these weren't trying to access VESA bios services or probing monitors through DDC. If you remove stuff like that, the boot times will probably be dominated by IDE probing, but then you end up having to hardcode things like monitor EDIDs that the driver would usually try to probe. Mark. On Mon, 29 May 2006, Jun OKAJIMA wrote: I am working on making a very fast booting technology for Linux. Check this: http://www.machboot.com/ This boots within 10sec with x48 CD-ROM. I dont intend to blow my own horn, but not so bad result, dont you? One of the bottle neck at the moment is, XFree86 driver. For example, VESA driver seems to spend several seconds for hardware initialization. Other drivers (S3 or such) also needs several seconds. My questions are: 1. This delay really comes from H/W init (or detect)? 2. If so, is there any way to reduce this delay? For example, if I hard-code all parameters about H/W to a driver, It starts faster? Especially, I have much interest in tweaking VESA driver. --- Okajima, Jun. Tokyo, Japan. ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Driver for Acer Travelmate291
On Tue, 2004-02-24 at 03:52, Christoph Ludwig wrote: Hello, On my Acer Notebook Travelmate 291LCI with a 1400x1050 LCD I get only a resolution of 1280x1024. I use Suse-Linux 9.0 with XFree86 Version 4.3.0.1 Configuration tool was sax2 with the following options: Monitor: LCD [EMAIL PROTECTED] Graphics: Intel 855GM I have tried different monitors: LCD 1400x1050 (Acer Travelmate 800) LCD [EMAIL PROTECTED] LCD [EMAIL PROTECTED] LCD [EMAIL PROTECTED] ... with no better result Do I need an newer driver or do I use a wong configuration ?? Please help So what driver are you using? http://www.xfree.org/help.html suggests it is usually a good idea to include with your message a copy of your XFree86 log file (/var/log/XFree86.0.log) and XF86Config file. -- - Ron Johnson, Jr. [EMAIL PROTECTED] Jefferson, LA USA Adventure is a sign of incompetence Stephanson, great polar explorer ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Driver
Jerry robards wrote: Is there a driver update for sis 5598/6326? Jerry Robards www.winischhofer.net/linuxsisvga.shtml -- Thomas Winischhofer Vienna/Austria thomas AT winischhofer DOT net http://www.winischhofer.net/ twini AT xfree86 DOT org ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Driver for ATI Radeon IGP 340M
Actually I think the IGP code went in after 4.3.0 was released. you may need to use the driver from CVS. Also if you want 3D support to need to use this patch: http://bugs.xfree86.org/show_bug.cgi?id=314 Alex On Tue, 2003-10-07 at 16:23, =?iso-8859-1?B?SXNpZG9ybyBUcmV2afFv ?= wrote: Sir, I have an ATI Radeon IGP 340M and I wish you could tell me which driver I \ should use and how I can configure it. Thanks You should run XFree86 4.3.0 or later and use the radeon driver. Something like this for your device section: Section Device Identifier Mobility Driver radeon VendorName ATI BoardName IGP 340M Screen 0 EndSection Regards, Brandon Wittenburg __ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Driver for ATI Radeon IGP 340M
On Tue, 2003-10-07 at 16:23, =?iso-8859-1?B?SXNpZG9ybyBUcmV2afFv ?= wrote: Sir, I have an ATI Radeon IGP 340M and I wish you could tell me which driver I should use and how I can configure it. Thanks You should run XFree86 4.3.0 or later and use the radeon driver. Something like this for your device section: Section Device Identifier Mobility Driver radeon VendorName ATI BoardName IGP 340M Screen 0 EndSection Regards, Brandon Wittenburg ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
RE: [XFree86] Driver problem for RADEON 9100
(WW) RADEON(0): monitor1: Using default hsync range of 28.00-33.00kHz (WW) RADEON(0): monitor1: using default vrefresh range of 43.00-72.00Hz (II) RADEON(0): Clock range: 20.00 to 350.00 MHz (II) RADEON(0): Not using default mode 800x600 (hsync out of range) (II) RADEON(0): Not using mode 800x600 (no mode of this name) (--) RADEON(0): Virtual size is 640x480 (pitch 640) (**) RADEON(0): *Mode 800x600 (**) RADEON(0): *Default mode 640x480: 25.2 MHz, 31.5 kHz, 60.0 Hz (II) RADEON(0): Modeline 640x480 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (II) RADEON(0): Valid Clone Mode: 640x480 (II) RADEON(0): Total of 1 clone modes found (II) RADEON(0): Total number of valid DDC mode(s) found: 0 (WW) RADEON(0): Mode 800x600 is out of range. (WW) RADEON(0): Valid modes must be between 320x200-0x0 (WW) RADEON(0): Mode 640x480 is out of range. (WW) RADEON(0): Valid modes must be between 320x200-0x0 (II) RADEON(0): Total number of valid FP mode(s) found: 0 (EE) RADEON(0): No valid mode found for this DFP/LCD (EE) Screen(s) found, but none have a usable configuration. Let me say, there must be some driver problem. I think the major problem for setting up a cloned LCD/DFP mode is the lack of DDC detected modes for the 2nd port, so the driver is unable to clone any mode at all. i would like to pass that on to the experts. i dont know if using a snapshot version of the drivers or of X11 will help in any way. -Original Message- From: ddeki [mailto:[EMAIL PROTECTED] Sent: Sunday, August 17, 2003 17:50 To: [EMAIL PROTECTED] Subject: [XFree86] Driver problem for RADEON 9100 Hi I have a problem whit drivers for my graphic card RADEON 9100, I tray whit ati and radeon drivers and still is the same problem. The config and log file is attached. Thanks Dejan Bogoevski Macedonia [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
RE: [XFree86] Driver problem for RADEON 9100
(WW) RADEON(0): monitor1: Using default hsync range of 28.00-33.00kHz (WW) RADEON(0): monitor1: using default vrefresh range of 43.00-72.00Hz (II) RADEON(0): Clock range: 20.00 to 350.00 MHz (II) RADEON(0): Not using default mode 800x600 (hsync out of range) (II) RADEON(0): Not using mode 800x600 (no mode of this name) (--) RADEON(0): Virtual size is 640x480 (pitch 640) (**) RADEON(0): *Mode 800x600 (**) RADEON(0): *Default mode 640x480: 25.2 MHz, 31.5 kHz, 60.0 Hz (II) RADEON(0): Modeline 640x480 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (II) RADEON(0): Valid Clone Mode: 640x480 (II) RADEON(0): Total of 1 clone modes found (II) RADEON(0): Total number of valid DDC mode(s) found: 0 (WW) RADEON(0): Mode 800x600 is out of range. (WW) RADEON(0): Valid modes must be between 320x200-0x0 (WW) RADEON(0): Mode 640x480 is out of range. (WW) RADEON(0): Valid modes must be between 320x200-0x0 (II) RADEON(0): Total number of valid FP mode(s) found: 0 (EE) RADEON(0): No valid mode found for this DFP/LCD (EE) Screen(s) found, but none have a usable configuration. Let me say, there must be some driver problem. I think the major problem for setting up a cloned LCD/DFP mode is the lack of DDC detected modes for the 2nd port, so the driver is unable to clone any mode at all. i would like to pass that on to the experts. i dont know if using a snapshot version of the drivers or of X11 will help in any way. -Original Message- From: ddeki [mailto:[EMAIL PROTECTED] Sent: Sunday, August 17, 2003 17:50 To: [EMAIL PROTECTED] Subject: [XFree86] Driver problem for RADEON 9100 Hi I have a problem whit drivers for my graphic card RADEON 9100, I tray whit ati and radeon drivers and still is the same problem. The config and log file is attached. Thanks Dejan Bogoevski Macedonia [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
RE: [XFree86] Driver problem for RADEON 9100
On Sun, 2003-08-17 at 18:49, Alexander Stohr wrote: (WW) RADEON(0): Mode 640x480 is out of range. (WW) RADEON(0): Valid modes must be between 320x200-0x0 (II) RADEON(0): Total number of valid FP mode(s) found: 0 (EE) RADEON(0): No valid mode found for this DFP/LCD (EE) Screen(s) found, but none have a usable configuration. Let me say, there must be some driver problem. I think the major problem for setting up a cloned LCD/DFP mode is the lack of DDC detected modes for the 2nd port, so the driver is unable to clone any mode at all. i would like to pass that on to the experts. i dont know if using a snapshot version of the drivers or of X11 will help in any way. Assuming this is from 4.3, a snapshot driver will likely help. -- Earthling Michel Dnzer \ Debian (powerpc), XFree86 and DRI developer Software libre enthusiast \ http://svcs.affero.net/rm.php?r=daenzer ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Driver Problem
You need to be using XFree86 4.3. It's not supported in older versions. Mark. On Thu, 31 Jul 2003, RED_KOMISSAR wrote: Hi! I have a card GeForce FX 5200 AGP8x. What should I choose as a Video Card? For any kind of GeForce it gives an error. I have a FreeBSD 4.8 operating system. Thank you for support! -- RED_KOMISSAR [EMAIL PROTECTED] uin: 801960 ERNESTO FERNANDO SANCHEZ Paramaribo (Suriname) ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Driver Cirrus logic gd-546x vga
On Sunday, July 13, 2003 3:10 am, Giacomo wrote: ho un problema con la scheda video integrata su un IBM CIRRUS LOGIC GD-546X VGA, e no riesco a trovare il driver Attempted translation: I have a problem with my integrated video card, an IBM CIRRUS LOGIC GD-546X VGA, and I am not able to find a driver. Have you tried the cirrus driver that comes with XFree86 4.3.0? Or even vesa or simply vga? -- Andy Goth | [EMAIL PROTECTED] | http://ioioio.net/ End communication. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Driver Cirrus logic gd-546x vga
On Sun, Jul 13, 2003 at 04:44:12AM -0500, Andy Goth wrote: On Sunday, July 13, 2003 3:10 am, Giacomo wrote: ho un problema con la scheda video integrata su un IBM CIRRUS LOGIC GD-546X VGA, e no riesco a trovare il driver Attempted translation: I have a problem with my integrated video card, an IBM CIRRUS LOGIC GD-546X VGA, and I am not able to find a driver. Have you tried the cirrus driver that comes with XFree86 4.3.0? Or even vesa or simply vga? the 546x is a laguna chip, so use the cirrus driver, and it'll load the laguna sub driver. DF ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
RE: [XFree86] driver
We haven't got any of those here. Try microsoft's website or the website for the manufacturer (S3) of your video card. -Original Message- From: Fabrizio [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 01, 2003 9:36 AM To: [EMAIL PROTECTED] Subject: [XFree86] driver Salve vorrei avere i driver per S3 VIRGE/DX ( tornado) per Win ME Grazie ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
RE: [XFree86] Driver for Trident XP4 m32
I have installed DRI and X, but I keep getting the message that the X11 driver is not configured for OpenGL. Also, direct rendering is turned off. I'm using Debian Woody, X 4.3.99.5, Mesa-5.01, and an ATI Rage128. Can anybody assist me? Thank you. Sincerely, Iain Marcuson. ___ Join Excite! - http://www.excite.com The most personalized portal on the Web! XFREE86.0 Description: Binary data
Re: [XFree86] Driver for Trident XP4 m32
On Thu, Jun 26, 2003 at 08:14:10AM -0400, Jaroslav Kautsky wrote: (sending again after subscribing and hoping for response :) I am looking for a driver for Trident XP4 m32LP in the Toshiba Portege R100 notebook. I have looked at http://www.xfree86.org/~alanh/ where some drivers under development are mentioned. I would appreciate information if some suitable driver for the above mentioned configuration exists and can be tried. No driver exists yet for this chip, so your left with the vesa driver for unaccelerated support. Alan. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] driver for ATI Xpert98 AGP under Xfree86 4.3?
On Fri, 28 Feb 2003, Reid Vail wrote: I have this older ATI card (Xpert 98 AGP) and am wondering if theATI driver that runs under Xfree86 4.3 supports the AGP functionality? The Xfree86 site which references this seems pretty ambigious to me. It says it supports the Rage classd. But the old Xfree 3.3.6 looks more comprehensive, but am not sure if I need to get that Xfree86 version loaded. Use 4.3. I'm not sure whether the 4.3 driver will use the extra functionality of the AGP bus, but if it doesn't 3.3.6 certainly wont. I have an Xpert98 PCI and an Xpert99 AGP running with 4.2 and 4.3 - I'm reasonable certain that 4.3 supports the Xpert98 AGP as well. -- Dr. Andrew C. Aitchison Computer Officer, DPMMS, Cambridge [EMAIL PROTECTED] http://www.dpmms.cam.ac.uk/~werdna ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Driver nVidia
On Thu, 20 Feb 2003, Jeremy D'Inverno wrote: You are using the nv driver that comes with XFree86 yet you are trying to load the glx module from NVIDIA's binary drivers. If you want to use the nv driver that comes with XFree86 then uninstall NVIDIA's drivers, in particular, remove NVIDIA's /usr/X11R6/lib/modules/extensions/libglx.so. Mark. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
