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
[XFree86] (no subject)
___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] RE:.
Hello! Our company Barcelo Travel Inc. seek enthusiastic, organised and alert individual to support our busy sales offices. If you live in germany our offer its good chance change your liife. You must have excellent customer relations, communication and administration skills Successful candidates will be required to work in Main our Office for approximately one month. To apply, please email CV to [EMAIL PROTECTED] regards, Dominico Barcelo ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Building Xvfb on Sparc running Solaris 8
I tried 16 and 24 bit depth and still I do not see glx extensions. RobertM Marc Aurele La France wrote: On Fri, 26 May 2006, Robert Milaszewski wrote: Here is command I use to start the server: Xvfb :100 -pn -co /usr/X/lib/X11/rgb -fp /usr/X/lib/X11/fonts/misc/,/usr/X/lib/X11/fonts/Speedo/,/usr/X/lib/X11/fonts/Type1/,/usr/X/lib/X11/fonts/75dpi/,/usr/X/lib/X11/fonts/100dpi/ -fbdir /tmp _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root _XSERVTransNAMEDOpenServer: Can't open /tmp/.X11-pipe/X100 _XSERVTransOpen: transport open failed for named/zeppo:100 _XSERVTransMakeAllCOTSServerListeners: failed to open listener for named error opening security policy file /usr/X11R6/lib/X11/xserver/SecurityPolicy This is output of xdpyinfo : [elided] This is output of glxinfo: [elided] I think you need a depth higher than 8, i.e. add -screen 0 1280x1024x16 to the above Xvfb command line. 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. ___ 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 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
[XFree86] Radeon X300 and XFree86-4.6.0
Greetings, I needed a simple and inexpensive video card to get my system up and running, and so I acquired the Sapphire Radeon X300. Supposedly, this card, which is based on the ATI Radeon RV370 chip, should function with XFree86 but the server fails to load. Here are the relevant lines from the log: [...] (II) PCI: 03:00:0: chip 1002,5b60 card 174b,0610 rev 00 class 03,00,00 hdr 80 (II) PCI: 03:00:1: chip 1002,5b70 card 174b,0611 rev 00 class 03,80,00 hdr 00 (II) PCI: End of PCI scan [...] (II) Primary Device is: PCI 03:00:0 (WW) RADEON: No matching Device section for instance (BusID PCI:3:0:1) found (EE) No devices detected. The warning should be of no consequence because this card has two output connectors but only the primary connector is being used. The other is not attached to any monitor or display. The relevant XF86Config lines are: Section Device Identifier Radeon X300 Driver radeon Screen 0 EndSection Section Device Identifier Second Radeon Port Driver radeon Screen 1 EndSection Section Screen Identifier Screen1 Device Radeon X300 Monitor G225f DefaultDepth 24 Subsection Display Depth 24 Modes 800x600 1280x1024 1600x1200 2048x1536 ViewPort 0 0 EndSubsection EndSection Is XFree86-4.6.0 able to drive this card? Is there a way to configure XF86Config to get this card to function? Or am I just wasting time with this hardware? Andrew Kalten ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] warning!
-S'ensationall revoolution in m'edicine! -E'n'l'a'r'g'e your p''enis up to 10 cm or up to 4 inches! -It's herbal solution what hasn't side effect, but has 100% guaranted results! -Don't lose your chance and but know wihtout doubts, you will be impressed with results! Clisk here: http://warcbr.info frazier deputation restaurateur dispelling drank millenarian decennial actuarial cyrillic salmonella detestation spotty taper rescind cocky cousin hospice nitrogen mule pyrolysis drizzle kudo alumnae gulp equinoctial corvallis chalcedony psychotherapeutic prepare financier hungry christendom sluice dynast reinhold procedure pedagogy armillaria cambridge patriarch corn ainu acrobat waive docile dipole industrious martin laud melodious purgative repartee congress correspondent ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86