XVideo - adding and removing interfaces?
I'd like to be able to add/remove an XVideo interface on the fly during mode switches. Is this possible with the existing interface? I don't see anything in the DESIGN doc other than the xf86XVScreenInit() function for setup. The ViRGE doesn't seem capable of XVideo during doublescan modes (320x200), so I'd like to be able to remove the Xv interfaces when in those modes, then re-add them when a compatible mode is switched back in. -- Kevin ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: register for video memory
There is a standard VESA VGA call. http://freespace.virgin.net/hugo.elias/graphics/x_svga_i.htm There is a different way to do this in XFree. Look at the Adjust() function in the drivers. http://www.xfree86.org/3.3.6/VGADriver6.html#16 Roger On Fri, 2003-01-24 at 11:40, [EMAIL PROTECTED] wrote: > Hi, > > I am looking for the registers that can specify the video memory's > offset where the image is shown on the screen. > > Does this register exist? If it does, can someone tell me > any hint or keyword so that I can search it in related > data sheets? My graphic card is ATI Radeon 7500. > > Thanks in advance, > > jing > ___ > Devel mailing list > [EMAIL PROTECTED] > http://XFree86.Org/mailman/listinfo/devel -- roger <[EMAIL PROTECTED]> ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
urgent assistant
DEAR SIR/MADAM, Compliment of the day, I am JAMES KYARI, The son of late General Kubwa Kyari of the Democratic Republic of Congo. My father was a General in the Congolese Army. In his position (My father) with the office of the presidentcy during the regime of Laurent Kabila, he was assigned on a secret mission to source and acquire arms internationally in order to strengthen the Government forces against the rebels, which already had the support of Rwandan and Uganda Army. Meanwhile, he was still negotiating for the purchase of the arms, he received on the 16th January 2001 news of the assassination of Laurent Kabila which force him to call off the assignment and deposited the sum of US$12.5M, Packed in a diplomatic case in a private security company in the Hague, the Netherlands, though he registered the content as precious stones while the real content is (US12.5M) meant for the purchase of arms for the Congolese Army. My father went home for the funeral of the late president, but on his arrival he was arrested, detained and tortured, unfortunately my father suffer cardiac arrest and died on the 17th of March 2001. However, on one of our numerous visits, my mother and I paid him while in prison, my father was able to reveal this secret to me and advice that i should proceed to the Netherlands to claim the money, he handed me all the relevant documents that will enable me claim the box from the security company.Already, I have made my first visit to the security company and the availability of this box have been confirmed. On our arrival in the Netherlands few months ago, we sought for political asylum; which was granted. My mother and I are making frantic effort on the best way to handle this money. We sought advice from an attorney who advised that we must seek for a trustworthy foreign business partner whom this money could be transferred into his/her (company"s) account. This we view as the best option because our refugee status dose not permit us to operate a bank account, hence we seek your assistance and hope you could be trusted. I got your contact from the commercial section of the congolese embassy in Belgium. Meanwhile, I sincerely ask for your assistance to get this money through your account, Your share for assisting us will be 25% of the total sum, 5% will be use for upsetting all the expenses incurred in the course of concluding this venture and the remaining 70% that will be for me and my family. Also you stand to gain from any investment you might introduce us into after the conclusion of the transfer. Please keep this confidential until we finalize and get this money into your account for security reasons. This is my e-mail address you can reach me:([EMAIL PROTECTED]) Thanks and GOD bless MR, JAMES KYARI. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: 4.2.99.4: unable to use secondary PCI Radeon 7000
On Mon, 27 Jan 2003, Marc Aurele La France wrote: > On Mon, 27 Jan 2003, Wayne Whitney wrote: > > > 2) There is a text mode corruption problem with the PCI Radeon 7000. It > > occurs as soon as XFree86 is run on this card after it has been > > initialized. So if the PCI card is initialized by the BIOS, it occurs the > > first time I run XFree86; if the AGP card is initialized by the BIOS, it > > occurs the second time I run XFree86 on the PCI card. The text mode is > > corrupted to a bunch of flashing half block characters, and this occurs > > before the display enters graphics mode. > > This appears related to issues being discussed on a different thread. > I'll wait to see what happens there, before doing anything about it. Indeed, I hadn't noticed that thread on the xfree86 list (on radeon 7200 support). The patch discussed there, which I include below, gets rid of the text mode corruption I'm seeing. I'm all for it. I also attached the current diff between the log files when I run XFree86 the first and second times on my PCI Radeon 7000. I assume the differences are harmless. Thanks again for all your help! Cheers, Wayne --- radeon_driver.c.~1.81.~ 2003-01-26 18:54:43.0 -0800 +++ radeon_driver.c 2003-01-27 15:56:42.0 -0800 @@ -405,7 +405,7 @@ extern int gRADEONEntityIndex; -#if 0 /* !defined(__alpha__) */ +#if !defined(__alpha__) # define RADEONPreInt10Save(s, p) # define RADEONPostInt10Check(s, p) #else /* __alpha__ */ --- /var/log/XFree86.2.log.old 2003-01-27 15:59:13.0 -0800 +++ /var/log/XFree86.2.log 2003-01-27 15:59:29.0 -0800 @@ -16,7 +16,7 @@ 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.2.log", Time: Mon Jan 27 15:59:08 2003 +(==) Log file: "/var/log/XFree86.2.log", Time: Mon Jan 27 15:59:25 2003 (==) Using config file: "/etc/X11/XF86Config" (++) ServerLayout "Layout1" (**) |-->Screen "Screen1" (0) @@ -344,7 +344,7 @@ (II) Module vgahw: vendor="The XFree86 Project" compiled for 4.2.99.4, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.6 -(II) RADEON(0): vgaHWGetIOBase: hwp->IOBase is 0x03b0, hwp->PIOOffset is 0x +(II) RADEON(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x (II) RADEON(0): PCI bus 0 card 8 func 0 (**) RADEON(0): Depth 16, (--) framebuffer bpp 16 (II) RADEON(0): Pixel depth = 16 bits stored in 2 bytes (16 bpp pixmaps) @@ -358,11 +358,13 @@ compiled for 4.2.99.4, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.6 (II) RADEON(0): initializing int10 -(II) Truncating PCI BIOS Length to 49152 +(EE) RADEON(0): Cannot read V_BIOS (--) RADEON(0): Chipset: "ATI Radeon VE QY (AGP)" (ChipID = 0x5159) (--) RADEON(0): Linear framebuffer at 0xe000 (--) RADEON(0): MMIO registers at 0xeb02 (--) RADEON(0): VideoRAM: 32768 kByte (64-bit DDR SDRAM) +(WW) RADEON(0): Video BIOS not detected in PCI space! +(WW) RADEON(0): Attempting to read Video BIOS from legacy ISA space! (II) RADEON(0): CloneDisplay option not set -- defaulting to auto-detect (II) RADEON(0): Primary Display == Type 3 (II) Loading sub module "ddc" @@ -378,7 +380,7 @@ compiled for 4.2.99.4, module version = 1.2.0 ABI class: XFree86 Video Driver, version 0.6 (II) RADEON(0): I2C bus "DDC" initialized. -(II) RADEON(0): PLL parameters: rf=2700 rd=60 min=12000 max=35000; xclk=15000 +(II) RADEON(0): PLL parameters: rf=2700 rd=12 min=12500 max=35000; xclk=18300 (==) RADEON(0): Using gamma correction (1.0, 1.0, 1.0) (II) RADEON(0): Validating modes on Primary head (DDCType: 2) - (II) RADEON(0): I2C device "DDC:ddc2" registered at address 0xA0. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: 4.2.99.4 Test report : Ctr-Alt-BkSpc status?
David Dawes wrote: > > > On Sun, Jan 26, 2003 at 03:06:36AM -0500, Kevin Brosius wrote: > > >> Does the server work correctly other than the key sequence not > >> working? If it is stuck somewhere, it might explain both why > >> SIGTERM and SIGHUP didn't do anything and why the terminate key > >> sequence didn't work. > > > >Yes, the server seems to work fine, other than ignoring Ctl-Alt-BkSpc. > >Other Alt sequences work, like Ctl-Alt-+. > > Those other sequences are handled in the same way as Ctl-Alt-BkSpc, > so it does point to the mapping for that one getting overriden after > the X server starts. > > >> Could you send the 'xmodmap -pk' output? Are you running any > >> xmodmap script as part of your startx/xdm rc files that might be > >> re-mapping the BackSpace key? > > > >The patch doesn't seem to make a difference. > > > >I've attached xmodmap -pk. > > The only difference I see between yours and mine is that mine has the > following for the backspace key: > > 22 0xff08 (BackSpace) 0xfed5 (Terminate_Server) > > while yours is: > > 22 0xff08 (BackSpace) > > >xmodmap scripts, that may be it. It looks like SuSE uses a .xinitrc > >which may call 'xmodmap /usr/X11R6/lib/X11/Xmodmap' if it exists and > >XSESSION_IS_UP is set. Although it comments that XSESSION_IS_UP is set > >by xdm, which I am not running. If it where set, it would use an old > >Xmodmap, as I've changed ProjectRoot on this machine and that default > >path is an older version, 4.1.0. > > > >Other than that, I don't see anything calling xmodmap. And I don't > >think it's calling that one, since it's xdm related. > > A way to double-check this is to run something like: > > startx /path/to/your/twm > > or just: 'XFree86' > > and see if the server terminate sequence works then. Yes, this case works. So, something in my setup (an xmodmap call I haven't located yet?) is incompatible with the recent changes? When started this way, running xmodmap -pk against the server does show: 22 0xff08 (BackSpace) 0xfed5 (Terminate_Server) -- Kevin ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: 4.2.99.4: unable to use secondary PCI Radeon 7000
On Mon, 27 Jan 2003, Wayne Whitney wrote: > On Mon, 27 Jan 2003, Marc Aurele La France wrote: > > OK, thanks. Please try the attached. > That patch works great! Thank you very much. You're welcome. I'll commit this shortly (meaning that this'll show up in 4.3). >In case it is of interest, > I have appended below the int10 hunk of a diff of the log files with your > patch--XFree86.0.log is on the primary AGP RADEON VE and XFree86.1.log is > on the secondary PCI RADEON 7000. > I thought I would mention the two other problems I still have with my > setup, in case they are of interest to you. > 1) If I attempt to run multihead using both cards with the latest CVS > version (fix 789), I get the following error: > (II) Reloading /usr/X11R6-CVS/lib/modules/drivers/radeon_drv.o > Symbol xf86SetDDCproperties from module >/usr/X11R6-CVS/lib/modules/drivers/radeon_drv.o is unresolved! > This is an improvement from a few days ago, when there were many "Symbol > unresolved" messages. > 2) There is a text mode corruption problem with the PCI Radeon 7000. It > occurs as soon as XFree86 is run on this card after it has been > initialized. So if the PCI card is initialized by the BIOS, it occurs the > first time I run XFree86; if the AGP card is initialized by the BIOS, it > occurs the second time I run XFree86 on the PCI card. The text mode is > corrupted to a bunch of flashing half block characters, and this occurs > before the display enters graphics mode. > In case it is useful, I have included below the full diff between the log > file when I first run XFree86 on the PCI Radeon 7000 and the second time I > run XFree86 on it, when the corruption occurs. This is with the system > BIOS set to initialize the AGP card. This appears related to issues being discussed on a different thread. I'll wait to see what happens there, before doing anything about it. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 Core Team member. ATI driver and X server internals. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Bison/Yacc problems ...
On Mon, Jan 27, 2003 at 03:17:27PM -0500, Jamie Risk wrote: > After opening the 4.2.0 tar balls and applying the 4.2.0-4.2.1 patch, I find > I'm getting a compiling error when bison tries to process the file > "./lib/Xft/xftgram.y". The CVS/RCS ID for the file is: > > $XFree86: xc/lib/Xft/xftgram.y,v 1.5 2001/05/16 10:32:54 keithp Exp $ > > And the error I get is this: > bison -y -d xftgram.y > xftgram.y:168.8: parse error, unexpected ":", expecting ";" or "|" > xftgram.y:169.3-6: $$ of `matrix' has no declared type > make[3]: *** [xftgram.c] Error 1 > > I checked the other "*.y" files in the distro, and there are other instances > of > what appears to be misplaced/missing semicolons in the grammar rules > sections. > > >From the "./xc" directory, I looked for all (six or seven) "*.y" files and > tried > each with BISON version 1.75. > > I modified them all by hand (unwittingly adding semicolons where they made > syntactical sense to me to put them), and the compilation now seems to be > progressing smoothly as I write this. The whole exercise took only a few > minutes. > > As I'm new to X-Windows, particularly to XFree86 and its source code, could > someone verify this? well, sure - bison 1.75 is known to do that sort of thing. (it's possible to write yacc-compatible scripts for bison, but it's getting harder). -- Thomas E. Dickey <[EMAIL PROTECTED]> http://invisible-island.net ftp://invisible-island.net ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Bison/Yacc problems ...
After opening the 4.2.0 tar balls and applying the 4.2.0-4.2.1 patch, I find I'm getting a compiling error when bison tries to process the file "./lib/Xft/xftgram.y". The CVS/RCS ID for the file is: $XFree86: xc/lib/Xft/xftgram.y,v 1.5 2001/05/16 10:32:54 keithp Exp $ And the error I get is this: bison -y -d xftgram.y xftgram.y:168.8: parse error, unexpected ":", expecting ";" or "|" xftgram.y:169.3-6: $$ of `matrix' has no declared type make[3]: *** [xftgram.c] Error 1 I checked the other "*.y" files in the distro, and there are other instances of what appears to be misplaced/missing semicolons in the grammar rules sections. >From the "./xc" directory, I looked for all (six or seven) "*.y" files and tried each with BISON version 1.75. I modified them all by hand (unwittingly adding semicolons where they made syntactical sense to me to put them), and the compilation now seems to be progressing smoothly as I write this. The whole exercise took only a few minutes. As I'm new to X-Windows, particularly to XFree86 and its source code, could someone verify this? Thanks, - Jamie ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Cyberpro 20x0 driver?
At at previous job I was responsible for XFree86 Cyberpro drivers. Tvia (www.tvia.com) had supplied us with source code for their XFree86 4.x Cyberpro driver that worked reasonably well. I did have to make a few fixes and we did add some enhancements. The point of this is that Tvia does develop and maintain XFree86 drivers for their Cyberpro series. Why these are not available at least as binary downloads from their web site eludes me. Tvia does try to earn extra income from selling their SDK's. As of a year ago when I working on this the SDK's did not include the XFree86 driver sources, we had to obtain that separately. I suspect the reason Tvia has not open sourced their driver is a function of their wanting to derive income from the sale of their SDK's. My personal opion of their SDK's and their doc was it was not worth the price they were asking. However, having said that, I did find it essential to have the SDK's in order to work on the driver because the SDK's provided example code to perform certain functions which at the time were not part of the driver. I think Tvia suffers the same type of myopia that many small vendors suffer from. They would generate more income via increased hardware sales by opening up their source pool then the amount of income they generate by selling their marginal SDK's to a handful of partners. Maybe it would be worthwhile for someone to press them on this issue. John ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: 4.2.99.4: unable to use secondary PCI Radeon 7000
On Mon, 27 Jan 2003, Marc Aurele La France wrote: > OK, thanks. Please try the attached. That patch works great! Thank you very much. In case it is of interest, I have appended below the int10 hunk of a diff of the log files with your patch--XFree86.0.log is on the primary AGP RADEON VE and XFree86.1.log is on the secondary PCI RADEON 7000. I thought I would mention the two other problems I still have with my setup, in case they are of interest to you. 1) If I attempt to run multihead using both cards with the latest CVS version (fix 789), I get the following error: (II) Reloading /usr/X11R6-CVS/lib/modules/drivers/radeon_drv.o Symbol xf86SetDDCproperties from module /usr/X11R6-CVS/lib/modules/drivers/radeon_drv.o is unresolved! This is an improvement from a few days ago, when there were many "Symbol unresolved" messages. 2) There is a text mode corruption problem with the PCI Radeon 7000. It occurs as soon as XFree86 is run on this card after it has been initialized. So if the PCI card is initialized by the BIOS, it occurs the first time I run XFree86; if the AGP card is initialized by the BIOS, it occurs the second time I run XFree86 on the PCI card. The text mode is corrupted to a bunch of flashing half block characters, and this occurs before the display enters graphics mode. In case it is useful, I have included below the full diff between the log file when I first run XFree86 on the PCI Radeon 7000 and the second time I run XFree86 on it, when the corruption occurs. This is with the system BIOS set to initialize the AGP card. Thanks again for your help! Cheers, Wayne --- /var/log/XFree86.0.log 2003-01-27 10:10:43.0 -0800 +++ /var/log/XFree86.1.log 2003-01-27 10:11:04.0 -0800 @@ -360,13 +358,10 @@ compiled for 4.2.99.4, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.6 (II) RADEON(0): initializing int10 -(II) RADEON(0): Primary V_BIOS segment is: 0xc000 -(WW) RADEON(0): Restoring MEM_CNTL (), setting to 2d00 -(WW) RADEON(0): Restoring CONFIG_MEMSIZE (0200), setting to 0200 -(WW) RADEON(0): Restoring MPP_TB_CONFIG<31:24> (04), setting to 01 +(II) Truncating PCI BIOS Length to 49152 (--) RADEON(0): Chipset: "ATI Radeon VE QY (AGP)" (ChipID = 0x5159) -(--) RADEON(0): Linear framebuffer at 0xd800 -(--) RADEON(0): MMIO registers at 0xe900 +(--) RADEON(0): Linear framebuffer at 0xe000 +(--) RADEON(0): MMIO registers at 0xeb02 (--) RADEON(0): VideoRAM: 32768 kByte (64-bit DDR SDRAM) (II) RADEON(0): CloneDisplay option not set -- defaulting to auto-detect (II) RADEON(0): Primary Display == Type 3 --- /var/log/XFree86.1.log.old 2003-01-27 10:11:04.0 -0800 +++ /var/log/XFree86.1.log 2003-01-27 10:11:59.0 -0800 @@ -16,7 +16,7 @@ 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.1.log", Time: Mon Jan 27 10:10:59 2003 +(==) Log file: "/var/log/XFree86.1.log", Time: Mon Jan 27 10:11:56 2003 (==) Using config file: "/etc/X11/XF86Config" (++) ServerLayout "Layout1" (**) |-->Screen "Screen1" (0) @@ -344,7 +344,7 @@ (II) Module vgahw: vendor="The XFree86 Project" compiled for 4.2.99.4, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.6 -(II) RADEON(0): vgaHWGetIOBase: hwp->IOBase is 0x03b0, hwp->PIOOffset is 0x +(II) RADEON(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x (II) RADEON(0): PCI bus 0 card 8 func 0 (**) RADEON(0): Depth 16, (--) framebuffer bpp 16 (II) RADEON(0): Pixel depth = 16 bits stored in 2 bytes (16 bpp pixmaps) @@ -358,11 +358,15 @@ compiled for 4.2.99.4, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.6 (II) RADEON(0): initializing int10 -(II) Truncating PCI BIOS Length to 49152 +(EE) RADEON(0): Cannot read V_BIOS +(WW) RADEON(0): Restoring MEM_CNTL (), setting to 2d00 +(WW) RADEON(0): Restoring CONFIG_MEMSIZE (0200), setting to 0200 (--) RADEON(0): Chipset: "ATI Radeon VE QY (AGP)" (ChipID = 0x5159) (--) RADEON(0): Linear framebuffer at 0xe000 (--) RADEON(0): MMIO registers at 0xeb02 (--) RADEON(0): VideoRAM: 32768 kByte (64-bit DDR SDRAM) +(WW) RADEON(0): Video BIOS not detected in PCI space! +(WW) RADEON(0): Attempting to read Video BIOS from legacy ISA space! (II) RADEON(0): CloneDisplay option not set -- defaulting to auto-detect (II) RADEON(0): Primary Display == Type 3 (II) Loading sub module "ddc" @@ -378,7 +382,7 @@ compiled for 4.2.99.4, module version = 1.2.0 ABI class: XFree86 Video Driver, version 0.6 (II) RADEON(0): I2C bus "DDC" initialized. -(II) RADEON(0): PLL parameters: rf=2700 rd=60 min=12000 max=35000; xclk=15000 +(II) RADEON(0): PLL parameters: rf=2700 rd=12 min=12500 max=35000; xclk=18300
Re: 4.2.99.4: unable to use secondary PCI Radeon 7000
On Fri, 24 Jan 2003, Wayne Whitney wrote: > On Fri, 24 Jan 2003, Marc Aurele La France wrote: > > Hummm. Can you re-post that log again? The output from `scanpci -v` > > would also help. > OK, I've included three things below: the original log, the output of > 'scanpci -v', and the patch to getValidBIOSBase() that allows my secondary > PCI Radeon 7000 to be initialized. In case it is important, the 'scanpci > -v' output was generated after booting and running X on my primary AGP > Radeon VE, without using the secondary PCI Radeon 7000. OK, thanks. Please try the attached. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 Core Team member. ATI driver and X server internals. Whitney.diff.gz Description: Binary data
Please unsubscribe me from the mailing list ...
fyiDo you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now
Please unsubscribe me from the mailing list ...
Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now
Please unsubscribe me from the mailing list ...
Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now
