Re: help new driver
On Wed, Feb 25, 2004 at 07:30:49PM -0500, Mike A. Harris wrote: > 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 What driver are you speaking about ? > 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. Yeah, i would recomend a MIT/X11 & GPL dual licence, that would be nice, so the code could later be shared by the linux kernel, among others. Friendly, Sven Luther ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
(no subject)
Files kai filoi, Sti maxi twn ethinkwn eklogwn, stirizoume neous politikous me orama, politiko logo kai oreksi gia douleia. Theloume i nea autodimiourgiti genia, na exei dinami na mas ekprosopei sti Bouli. Tha xaroume loipon na sas doume tin Kiriaki 29/2 stis 19:00, stin omilia toy Ari Spiliotopoulou, bouleuti tis Neas Dinokratias kai ypopsifiou sti B Athinon sto gipedo SPORTING (Stathmos Hlektrikou Agios Elefuerios, Odos Hlia Zervou 89 Athina). Tha eimaste oloi ekei.
XFree86 4.4.0 RC3 -configure problems
I have a couple of problems when running XFree86 -configure on Solaris 2.5.1 x86, with two Matrox G450 cards. The first is that it exits with: Fatal server error: xf86MapVidMem: mmap failure: No such device or address I have determined that the place that this is happening is line 111 of int10/generic.c, in the xf86ExtendedInitInt10 function: #ifdef _PC if (!sysMem) sysMem = xf86MapVidMem(screen, VIDMEM_MMIO, V_BIOS, BIOS_SIZE + SYS_BIOS - V_BIOS); This function is also called when running the server (with the same values passed to xf86MapVidMem) but with no mmap failure. I assume that there is some other initialization that is not being done with the -configure option. The XF86Config.new file is still produced though. The second problem that I have is that the VendorName and ModelName in the Monitor section get set to "Monitor Vendor" and "Monitor Model" instead of the actual names of the vendor and model like they used to be in 4.3.0. When running the server, the Manufacturer and Model still appear correctly in the log. This is a problem for me because the hsync range of the Kramer VP720-DS Seamless Switcher/Scaler that we use is not detected properly. The log reports it as "Using default hsync range of 41.09-49.31 kHz", where in fact it is 15.36-90. This means that I have to do some post-processing on the config file after XFree86 -configure to manually set the hysnc range based on what the VendorName is. This is not possible any more since VendorName and ModelName are not configured properly. Another thing that I have noticed is that the DPMS option is no longer added. I don't understand why this would not be added anymore either for monitors reporting DPMS capabilities. Are there any reasons why these things are no longer configured by -configure? Can they be put back? Regards, Lindsay Haigh ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
S3 Savage Duoview support - almost there
I've been trying to implement duoview support on savage mx/ix chips on and off for a while now. I've got some info on virge mx and for the most part it seems to apply to savage. There are two crtcs and two dot clocks and either of which can be used to control/drive either or both outputs, flatpanel or crt in this case. I've narrowed the problem down to the second crt controller. no matter which dot clock or output I use it with it, I get no signal. the monitor just goes into powersave mode on the crt port and the FP just blooms. I've verified that both dotclocks work and I can set them up correctly, but the second crtc just refuses to work. I've double checked with register dumps that both crtcs seem to be set up correctly, but only the first one works. CRTC DCLKOutput Result --- crtc1dclk1 FP/CRT/Both Works crtc1dclk2 FP/CRT/Both Works crtc2dclk1 FP/CRT/Both No signal crtc2dclk2 FP/CRT/Both No signal the crtc registers are paried and share the same vga cr io space, you can switch between them using one of the sr regs. Does anyone out there have any idea what I may be missing? maybe some crtc2 enable bit somewhere? You can see my source code and progress here: http://www.botchco.com/alex/new-savage/html/ Thanks, Alex __ Do you Yahoo!? Get better spam protection with Yahoo! Mail. http://antispam.yahoo.com/tools ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Potential bug in xf86Elo.c
Miroslav Halas wrote: 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? This particular file is just about the most I ever knew about X so I am eager to help you how ever I can ;-P My suggestion is to go and pepper up the source with some trace, namely, you want to check if the right modules' methods are getting called for the right file descriptors and start from there ;-) (xf86Elo.c comes with a config file level debugging mechanism just set DebugLevel in the coreponding InputDevice entry and compile with DEBUG defined) Basicly, your module will load up at while X is parsing the XF86Config and X will ask the module to supply a file descriptor, when X recieves SIGIO, it will perform some `select' calls and find which descriptor(s) are ready for IO, then it will proceed to call the ReadInput method of the corresponding module that opened the file descriptor (which will in turn post the events). One thing I noticed: the function: xf86EloAllocate assumes screen number "0" Is it possible that you didn't specify "ScreenNo" in one (or both) of the InputDevice sections for either of your TouchScreen config file entries ? Well, I do have the source hanging around, but I admit I haven't hacked around in it for at least a year... Hope this helps ;-) Cheers, -Tristan ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
