Re: Re: Sis6326 register unlock problem
Thx for the info, in fact, I guessed that I used a wrong IO port address for sis on Mips, but I don't know where can I find the correct IO address and video memory mapping address. Thanks Harry === 2004-04-28 07:31:00 您在来信中写道：=== >--- Thomas Winischhofer <[EMAIL PROTECTED]> wrote: >> harry wrote: >> > Hi,all >> > >> > I met a problem while porting xfree86 to mips, it seems that I >> can't unlock the sis6326 registers. SR5 is used as password register >> in sis6326, if 86h is written into this register, then A1h will be >> read from this register, and unlock all the extension registers.If >> the value other than 86h is written into this register, then 21h will >> be read from this register,and lock all the extension registers. >> > But now when I wrote 86h to this register, I always get ffh, so the >> display can't be initialized. >> > Is there anyone met this problem? >> >> You have more than this locking/unlocking problem. It seems that none >> of >> the registers can be written or read, or they are being read >> from/written to wrong addresses. (For example, the memory clock is >> never >> 14 MHz, and there are no 2MB versions of the 6326.). >> >> Looks like a general register addressing problem. I have no >> experience >> whatsoever with mips hardware, so I can't help you further. >> >> You can, however, try the most recent driver from my website. It uses >> >> exclusivly relocated i/o ports, so perhaps this helps. > >You will need support for legacy IO in the kernel for using vgahw. I >have no idea if the MIPS kernel supports this at the moment. See this >thread for more info: >http://marc.theaimsgroup.com/?t=9900895891&r=1&w=2 >You may want to ask on the linux-mips ML. > >Alex > >> >> Thomas >> >> >> -- >> Thomas Winischhofer >> Vienna/Austria >> thomas AT winischhofer DOT net *** http://www.winischhofer.net >> twini AT xfree86 DOT org > > > > > >__ >Do you Yahoo!? >Win a $20,000 Career Makeover at Yahoo! HotJobs >http://hotjobs.sweepstakes.yahoo.com/careermakeover >___ >Devel mailing list >[EMAIL PROTECTED] >http://XFree86.Org/mailman/listinfo/devel = = = = = = = = = = = = = = = = = = = = 致 礼！ harry [EMAIL PROTECTED] 2004-05-11 ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Sis6326 register unlock problem
Hi,all I met a problem while porting xfree86 to mips, it seems that I can't unlock the sis6326 registers. SR5 is used as password register in sis6326, if 86h is written into this register, then A1h will be read from this register, and unlock all the extension registers.If the value other than 86h is written into this register, then 21h will be read from this register,and lock all the extension registers. But now when I wrote 86h to this register, I always get ffh, so the display can't be initialized. Is there anyone met this problem? Here is the log file I got. Thanks XFree86 Version 4.2.1 / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 3 September 2002 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/) Build Operating System: Linux 2.4.20-8 i686 [ELF] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/XFree86.0.log", Time: Sun Aug 7 04:42:25 2016 (==) Using config file: "/etc/X11/XF86Config-4" (==) ServerLayout "XFree86 Configured" (**) |-->Screen "Screen0" (0) (**) | |-->Monitor "Monitor0" (**) | |-->Device "Card0" (**) |-->Input Device "Mouse0" (**) |-->Input Device "Mouse1" (**) |-->Input Device "Keyboard0" (==) Keyboard: CustomKeycode disabled (**) FontPath set to "/usr/X11R6/lib/X11/fonts/misc" (**) RgbPath set to "/usr/X11R6/lib/X11/rgb" hawenUsing vt 7 (--) using VT number 7 (WW) Open APM failed (/dev/apm_bios) (No such device) IOPortBase = 2aac6000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 1283,8172 card , rev 20 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 1283,0801 card 1283,1283 rev b1 class 04,01,00 hdr 80 (II) PCI: 00:01:1: chip 1283,8172 card , rev 10 class 08,01,00 hdr 00 (II) PCI: 00:01:2: chip 1283,8172 card , rev 10 class 08,01,03 hdr 00 (II) PCI: 00:01:3: chip 1283,1234 card 1283,1234 rev 07 class 0c,03,10 hdr 80 (II) PCI: 00:01:4: chip 1283,8172 card , rev 11 class 06,01,00 hdr 00 (II) PCI: 00:01:5: chip 1283,8172 card , rev 01 class 01,01,8f hdr 00 (II) PCI: 00:01:6: chip 1283,8172 card , rev 10 class 06,80,00 hdr 80 (II) PCI: 00:01:7: chip 1283,8172 card , rev 01 class 01,01,8f hdr 00 (II) PCI: 00:10:0: chip 10ec,8139 card 10ec,8139 rev 10 class 02,00,00 hdr 00 (II) PCI: 00:11:0: chip 1039,6326 card , rev 92 class 03,00,00 hdr 00 (II) PCI: End of PCI scan (II) Host-to-PCI bridge: (II) PCI-to-ISA bridge: (II) Bus 0: bridge is at (0:0:0), (-1,0,0), BCTRL: 0x08 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0x - 0x (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0x - 0x (0x0) MX[B] (II) Bus -1: bridge is at (0:1:4), (0,-1,0), BCTRL: 0x08 (VGA_EN is set) (II) Bus -1 I/O range: (II) Bus -1 non-prefetchable memory range: (II) Bus -1 prefetchable memory range: (--) PCI:*(0:17:0) SiS 6326 rev 146, Mem @ 0x1080/23, 0x1100/16, I/O @ 0x14000380/7, BIOS @ 0x137c/16 (II) Addressable bus resource ranges are [0] -1 0x - 0x (0x0) MX[B] [1] -1 0x - 0x (0x1) IX[B] (II) OS-reported resource ranges: [0] -1 0x - 0x (0x1) MX[B] [1] -1 0x - 0x (0x1) MX[B] [2] -1 0x - 0x (0x1) IX[B] [3] -1 0x - 0x (0x1) IX[B] (II) Active PCI resource ranges: [0] -1 0x137e - 0x137f (0x2) MX[B] [1] -1 0x10101000 - 0x101010ff (0x100) MX[B] [2] -1 0x1010 - 0x10100fff (0x1000) MX[B] [3] -1 0x137c - 0x137c (0x1) MX[B](B) [4] -1 0x1100 - 0x1100 (0x1) MX[B](B) [5] -1 0x1080 - 0x10ff (0x80) MX[B](B) [6] -1 0x14018000 - 0x140180ff (0x100) IX[B] [7] -1 0x14017800 - 0x1401780f (0x10) IX[B] [8] -1 0x14017b74 - 0x14017b77 (0x4) IX[B] [9] -1 0x14017970 - 0x1401797f (0x10) IX[B] [10] -1 0x14017bf4 - 0x14017bf7 (0x4) IX[B] [11] -1 0x140179f0 - 0x140179ff (0x10) IX[B] [12] -1 0x14017800 - 0x1401780f (0x10) IX[B] [13] -1 0x14017b74 - 0x14017b77 (0x4) IX[B] [14] -1 0x14017970 - 0x1401797f (0x10) IX[B] [15] -1 0x14017bf4 - 0x14017bf7 (0x4) IX[B] [16] -1 0x140179f0 - 0x140179ff (0x10) IX[B] [17] -1 0x14016800 - 0x140168ff (0x100) IX[B] [18] -1 0x14016000 - 0x1401603f (0x40) IX[B] [19] -1 0x14017000 - 0x1401707f (0x80) IX[B] [20] -1 0x14000380 - 0x140003ff (0x80) IX[B](B) (II) Active PCI resource ranges a
Re: redhat-config-xfree86
Of course, it is resulted by Driver.(SiS 661) It may be resulted by "someone" touch wrong bits during programing DDC info That "someone" should be not contained in driver,because I had inspected during all of outb micro in the driver. May XFree86 provide get DDC info function.(maybe XFree86 get which registers contral I2C)?? Does any tool have break point I/O address in Linux? Thanks for suggesting - Original Message - From: "Mike A. Harris" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, January 16, 2004 7:02 AM Subject: Re: redhat-config-xfree86 > On Thu, 15 Jan 2004, harry wrote: > > >Date: Thu, 15 Jan 2004 13:56:18 +0800 > >From: harry <[EMAIL PROTECTED]> > >To: [EMAIL PROTECTED] > >Reply-To: [EMAIL PROTECTED] > >Content-Type: multipart/alternative; > > boundary="=_NextPart_000_001B_01C3DB6F.5971F840" > >Subject: redhat-config-xfree86 > > > >Hello all, > >I have a problem during run redhat-config-xfree86 under Xwindow : monitor will be closed (include sync). > >But run it normally under text console mode. I think that may be brought by driver , because it's ok under Xwindow if using vesa driver. > >I found exec redhat-config-xfree86 will run "python2.2 xconf.py" > >and monitor will closed in "cv = FX86HardwareState(xconf)" this step > >May someone know Which XFree86 functions will be called by FX86HardwareState(xconf).Or Where may I find hints? > > Doesn't sound like an XFree86 problem per se, unless the X server > is crashing when r-c-x starts up possibly. What video hardware > (brand and model) are you using, and what version of Red Hat > Linux? > > Also try doing: redhat-config-xfree86 --reconfig > > After this, try to start up X using "startx" and if it fails, > please put your X server log and config file somewhere viewable > via http or ftp, and post URLs to the files here. > > It's possible your particular video card model is not supported, > however I'll need the above info first in order to > determine/advise. > > TTYL > > > -- > Mike A. Harris > > ___ > Devel mailing list > [EMAIL PROTECTED] > http://XFree86.Org/mailman/listinfo/devel ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
redhat-config-xfree86
Hello all, I have a problem during run redhat-config-xfree86 under Xwindow : monitor will be closed (include sync). But run it normally under text console mode. I think that may be brought by driver , because it's ok under Xwindow if using vesa driver. I found exec redhat-config-xfree86 will run "python2.2 xconf.py" and monitor will closed in "cv = FX86HardwareState(xconf)" this step May someone know Which XFree86 functions will be called by FX86HardwareState(xconf).Or Where may I find hints? Thanks Harry
the log file 2nd time enter Xwindow
attached file is the log file created second time enter Xwindow Harry XFree86.0.log Description: Binary data
Re: Help: gdb xfree86 video card driver on rh9
Using gdb-xfreemod 6.0 instead of gdb-xfreemod 5.11-2.0 , I could use gdb to debug XFree86 430 under redhat 9.0. Following is the way what i am using. Using attach process ID after Xwindow had running, still could not break during what i setted breakpoints. But direct debug XFree86 "gdb /usr/X11R6/bin/XFree86" then "run :0",could certainty break at breakpoints. Thanks for suggest Harry - Original Message - From: "Alex Deucher" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, December 30, 2003 1:21 AM Subject: Re: Help: gdb xfree86 video card driver on rh9 > try one of these module enabled versions of gdb: > > http://www.logix.cz/michal/devel/gdb-xfreemod/ > http://www.dawa.demon.co.uk/xfree-gdb/ > > Alex > > --- Thomas Winischhofer <[EMAIL PROTECTED]> wrote: > > harry wrote: > > > > > I am debuging a video card driver on XFree86.I was using gdb > > > 5.1.1-2.0xfree on radhat 9.0. And I had tried : > > > (1) I was using "gdb /usr/X11R6/bin/XFree86" , then run. It result > > as > > > "Segmentation fault". > > > (2) During build sis_drv.o, I had using para "-g" for gcc. > > >"startx" open Xwindow fristly, then using "ps ax" gets the > > processid > > > of "X :0". > > > use SSH login > > >and "gdb /usr/X11R6/lib/modules/drivers/sis_drv.o processid". > > > By this way, i could see source codes and function symbols of the > > > sis_drv.o , and could set breakpoints. But Xwindow will not break > > at > > > those points that i setted.What's wrong on my ways to debug video > > driver > > > of xfree86 bu gdb? > > > > > > Now i only could use print message to debug,but that is > > troublesome. > > > If anybody has some suggestion as how to debug I would gladly > > > appreciate any suggestions. > > > > Nice to see that a SiS employee is dealing with XFree86. > > > > I am no gdb expert myself, but here is my $.02: > > > > 1) You need a patched gdb which is capable of dealing with XFree86's > > modules. I don't have a link at hand, but I'm sure someone else > > reading > > this has. > > > > 2) If you want to attach to the running XFree86 process: sis_drv.o is > > not the process, but part of the X process. You need to attach to the > > X > > process. > > > > In case you are "debugging" the official XFree86 sis driver, I'd > > appreciate if you told me what problems you experience (since I am > > the > > author and maintainer of this driver). > > > > Thomas > > > > -- > > Thomas Winischhofer > > Vienna/Austria > > thomas AT winischhofer DOT net *** > > http://www.winischhofer.net/ > > twini AT xfree86 DOT org > > > > > > > > ___ > > Devel mailing list > > [EMAIL PROTECTED] > > http://XFree86.Org/mailman/listinfo/devel > > > __ > Do you Yahoo!? > New Yahoo! Photos - easier uploading and sharing. > http://photos.yahoo.com/ > ___ > Devel mailing list > [EMAIL PROTECTED] > http://XFree86.Org/mailman/listinfo/devel ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Help: gdb xfree86 video card driver on rh9
I am debuging a video card driver on XFree86.I was using gdb 5.1.1-2.0xfree on radhat 9.0. And I had tried : (1) I was using "gdb /usr/X11R6/bin/XFree86" , then run. It result as "Segmentation fault". (2) During build sis_drv.o, I had using para "-g" for gcc. "startx" open Xwindow fristly, then using "ps ax" gets the processid of "X :0". use SSH login and "gdb /usr/X11R6/lib/modules/drivers/sis_drv.o processid". By this way, i could see source codes and function symbols of the sis_drv.o , and could set breakpoints. But Xwindow will not break at those points that i setted.What's wrong on my ways to debug video driver of xfree86 bu gdb? Now i only could use print message to debug,but that is troublesome. If anybody has some suggestion as how to debug I would gladly appreciate any suggestions.Thanks Harry Cheng [EMAIL PROTECTED]
