Potential bug in xf86Elo.c
Hello, this is my first post to the list here so I am not familiar with process so bare with me please. I have two elographics touchscreens connected to Matrox G450 running Fedora Core 1 (whatever version of XFree86 it is using). I have problem that the cursor doesn't correctly follow the touch, that is when I tap in the second touchscreen than where the cursor is currently, it doesn't go there. I have to keep my finger on the touchscreen and eventually the cursor goes to the correct touchscreen. Once it is in correct touchscreen everything works just fine. I poke around the code in xf86Elo.c and it seems like the call to xf86XInputSetScreen doesn't get executed properly. THis calls is made in this driver in xf86EloConvert which is setup as conversion_proc. I read the documentation for xf86XInputSetScreen in xf86XInput.c and it says that this method should be called in ReadInput method which is for this driver method xf86EloReadInput. COuld this be a potential problem causing the xf86XInputSetScreen to don't get executed? I am not sure what is the correct process to fix this and I would like to ask somebody more experienced. Could anybody please help me with this? Thanks in advance, Miro ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: help new driver
On Thu, 26 Feb 2004, dave wrote: >Date: Thu, 26 Feb 2004 12:24:02 +1300 >From: dave <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Reply-To: [EMAIL PROTECTED] >Content-Type: text/plain; > charset="iso-8859-1" >Subject: help new driver > >I am writing a driver and need to now what copyright GPL stuff >I need to put in my source files The existing drivers are under an MIT/X11 style license, which allows their source code to be shared with pretty much anything, including GPL licensed code. Making your driver MIT/X11 licensed, or dual licensing it as MIT/X11 and GPL, would allows other drivers to be able to benefit from sharing code with your driver as well. Of course it is totally up to you what license you would prefer to use. The FSF and/or GNU websites contain information on what you should place in your sources in order to properly legally indicate they are GPL licensed should you decide to not use the traditional MIT/X11 license which is more shareable. Hope this helps. -- Mike A. Harris ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: help new driver
--- dave <[EMAIL PROTECTED]> wrote: > I am writing a driver and need to now what copyright GPL stuff > I need to put in my source files > most XFree86 device drivers has a X11/BSD style license. take a look at the other drivers in xc/programs/Xserver/hw/xfree86/drivers However, how you want to license your driver is up to you. Alex __ Do you Yahoo!? Yahoo! Mail SpamGuard - Read only the mail you want. http://antispam.yahoo.com/tools ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
help new driver
I am writing a driver and need to now what copyright GPL stuff I need to put in my source files ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Get your degree
Get a non ac*(credit-**ed Degree in Any Experienced Field Call USA 1-702-926-4078 Now For More Information! It is a well known fact that people who posses a degree are looked upon as the elite If you have a degree, you are almost assured to gain leverage in the work place There's no testing required Call USA 1-702-926-4078 for more information. If you want to be taken off our mailing list pleasemailto:[EMAIL PROTECTED]"> Here to send email with the subject nothanks Sorry for any inconvenience.
event interface in Xfree86
Hello there guys! I am sitting here with a new desktopset and I can't use all keys on my keyboard nor the tiltwheel on my mouse. The drivers don't report the scancodes for a few keys and the scancode is the same when I tilt the wheel to the left and to the right. When using the event interface it reports different actions for every key... Is there any plans on writing drivers using the event interface with USB-devices? I'm on the verge on writing some myself, but I've never written any drivers before so... I hope my English isn't so bad you don't understand what I'm saying!! -- Jörgen Lidholm [EMAIL PROTECTED] signature.asc Description: Detta =?ISO-8859-1?Q?=E4r?= en digitalt signerad meddelandedel
Re: i855GM: New BIOS breaks i810-driver
Craig Ringer writes: > On Tue, 2004-02-24 at 22:55, Alan Hourihane wrote: > > We could leave the option in, but enable it by default, so that this > > information is displayed, and allow people to turn it off if it hangs. > > Additionally, why not print a log line like > > "Some versions of this video BIOS have a bug that will cause XFree86 to > hang. If you encounter this, try setting the BLAH option in your config > file." > > It should save a bunch of questions on [EMAIL PROTECTED] Yes, this sounds like a good idea. It should be printed right before the offending call so people will see it. The system does not hang hard therefore people should be able to retreive their log. On the other hand they may not know how to do it in this case. Sill, such a message may be worthwhile. I will add it together with the changes Alan suggested. Egbert. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
