Re: XFree86 bugzilla available
On Tue, 18 Mar 2003 20:04:22 -0500 David Dawes [EMAIL PROTECTED] wrote: An XFree86 bugzilla is now available at http://bugs.xfree86.org/. Many thanks to Hewlett-Packard for supplying the hardware, netSweng for hosting, and the many developers who helped configure and test it. This is a very welcome addition, i have personally had problems in finding out if an error i encountered was: a. My fault b. A bug c. Reported already. Enjoy. I will ! David -- David Dawes Release Engineer/President The XFree86 Project www.XFree86.org/~dawes ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel -- .-. /v\ L I N U X // \\ --Phear the Penguin-- /( )\ ^^-^^ ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
siliconmotion driver (4.3.0) issue on NetBSD/i386
hi, i upgraded today from XFree86 4.2.1 to 4.3.0 on a laptop running NetBSD/i386 -current (ASUS L7300-E, Silicon Motion, Inc. LynxEM) but the X server refuses to start (session log attached) and ends in an infinite loop. i can't even cleanly switch to another virtual console because the screen is pitch black, i had to reboot blindly from kernel debugger. i had issues with the siliconmotion driver in previous version (4.2.1) as well: - 'Option NoUseBIOS' had to be specified in the configuration file otherwise the server didn't start. this seems to be working now, since i don't see any indication of the errors seen before in the session log file but i tried both, Use and NoUseBIOS to no avail, - the driver didn't restore VGA palette correctly on exit or switching to another virtual console, leaving black screen. i found a patch on a japanese mailing-list (attached) which fixed this problem for me. i tried building 4.3.0 with and without this patch but apparently it doesn't reach the state where it would take effect so i can't say if it's still needed. i tried disabling acceleration in the configuration file (attached) but the result was the same as with acceleration enabled. any help is greatly appreciated. i can test patches and even fetch XFree86 sources from cvs, if necessary (note: 4.2.99something had the same problem as i see now but i didn't pay much attention since i was using 4.2.1 at the time as the main X release). regards, -- -- Lubomir Sedlacik [EMAIL PROTECTED] -- -- [EMAIL PROTECTED] -- XFree86 Version 4.3.0 Release Date: 27 February 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: NetBSD/i386 1.6P [ELF] The NetBSD Foundation, Inc. Build Date: 19 March 2003 Before reporting problems, check http://www.XFree86.Org/ to make sure that you have the latest version. Module Loader present 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: Wed Mar 19 13:55:45 2003 (==) Using config file: /etc/X11/XF86Config-4 (==) ServerLayout XFree86 Configured (**) |--Screen Screen0 (0) (**) | |--Monitor Monitor0 (**) | |--Device Card0 (**) |--Input Device Mouse0 (**) |--Input Device Keyboard0 (**) Option AutoRepeat 500 30 (**) Option XkbCompat group_led (**) XKB: compat: group_led (**) Option XkbLayout czsk(us_sk_qwerty) (**) XKB: layout: czsk(us_sk_qwerty) (==) Keyboard: CustomKeycode disabled (WW) The directory /usr/X11R6/lib/X11/fonts/intlfonts/ does not exist. Entry deleted from font path. (WW) The directory /usr/X11R6/lib/X11/fonts/Mozilla/ does not exist. Entry deleted from font path. (WW) The directory /usr/X11R6/lib/X11/fonts/biznet/75dpi/ does not exist. Entry deleted from font path. (WW) The directory /usr/X11R6/lib/X11/fonts/biznet/100dpi/ does not exist. Entry deleted from font path. (WW) The directory /usr/X11R6/lib/X11/fonts/biznet/misc/ does not exist. Entry deleted from font path. (**) FontPath set to /usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/CID/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/,/usr/X11R6/lib/X11/fonts/cyrillic/,unix/:7101 (**) RgbPath set to /usr/X11R6/lib/X11/rgb (**) ModulePath set to /usr/X11R6/lib/modules (--) Using wscons driver in pcvt compatibility mode (version 3.32) (II) Module ABI versions: XFree86 ANSI C Emulation: 0.2 XFree86 Video Driver: 0.6 XFree86 XInput driver : 0.4 XFree86 Server Extension : 0.2 XFree86 Font Renderer : 0.4 (II) Loader running on netbsd (II) LoadModule: bitmap (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor=The XFree86 Project compiled for 4.3.0, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.4 (II) Loading font Bitmap (II) LoadModule: pcidata (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor=The XFree86 Project compiled for 4.3.0, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.6 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,7194 card , rev 01 class 06,00,00 hdr 80 (II) PCI: 00:00:1: chip 8086,7195 card 1043,1063 rev 00 class 04,01,00 hdr 00 (II) PCI: 00:02:0: chip 126f,0710 card 126f,0710 rev a3 class 03,00,00 hdr 00 (II) PCI: 00:07:0: chip 8086,7198 card , rev 01 class 06,01,00 hdr 80 (II) PCI: 00:07:1: chip 8086,7199 card , rev 00 class 01,01,80 hdr 00 (II) PCI: 00:07:2: chip
Possible bug in xaaFillPoly.c
Hi,
Possible, there is a bug in the Mono8x8PatternRectHelper() function.
Lets look at XAAFillPolygonStippled():
Assume:
1. type == DO_MONO_8x8,
2. infoRec-Mono8x8PatternFillFlags:
HARDWARE_PATTERN_SCREEN_ORIGIN is NOT set,
HARDWARE_PATTERN_PROGRAMMED_BITS is set,
HARDWARE_PATTERN_PROGRAMMED_ORIGIN is NOT set.
In this case, pCache == NULL, and RectFunc = Mono8x8PatternRectHelper
Later, in Mono8x8PatternRectHelper() we will crash when trying to access
pCache-pat0.
I think that this patch may help, but i'm not sure.
--- xc.orig/programs/Xserver/hw/xfree86/xaa/xaaFillPoly.c Wed Mar 19 20:27:42
2003
+++ xc/programs/Xserver/hw/xfree86/xaa/xaaFillPoly.cWed Mar 19 20:29:26 2003
@@ -535,9 +535,9 @@
yorg = (y - yorg) 0x07;
if(!(infoRec-Mono8x8PatternFillFlags
- HARDWARE_PATTERN_PROGRAMMED_ORIGIN)){
+ HARDWARE_PATTERN_PROGRAMMED_BITS)){
if(infoRec-Mono8x8PatternFillFlags
- HARDWARE_PATTERN_PROGRAMMED_BITS) {
+ HARDWARE_PATTERN_PROGRAMMED_ORIGIN) {
int patx = pCache-pat0;
int paty = pCache-pat1;
XAARotateMonoPattern(patx, paty, xorg, yorg,
Re: Possible bug in xaaFillPoly.c
There's definitely a bug there. I'm not sure if that's the correct solution, or there is a bigger problem. I will review this code tonight. Thanks for pointing this out. Mark. On Wed, 19 Mar 2003, Alexandr Andreev wrote: Hi, Possible, there is a bug in the Mono8x8PatternRectHelper() function. Lets look at XAAFillPolygonStippled(): Assume: 1. type == DO_MONO_8x8, 2. infoRec-Mono8x8PatternFillFlags: HARDWARE_PATTERN_SCREEN_ORIGIN is NOT set, HARDWARE_PATTERN_PROGRAMMED_BITS is set, HARDWARE_PATTERN_PROGRAMMED_ORIGIN is NOT set. In this case, pCache == NULL, and RectFunc = Mono8x8PatternRectHelper Later, in Mono8x8PatternRectHelper() we will crash when trying to access pCache-pat0. I think that this patch may help, but i'm not sure. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: XFree86 bugzilla available
On Wed, 19 Mar 2003, [iso-8859-15] José Fonseca wrote: I know that the current policy on DRI is to post bugs on dri-users or dri-devel, but with XFree86 having a bug database is inevitable that people will eventually post bugs there too. Therefore what's the possibility of: - Setting up a general owner for DRI bugs, which probably would be [EMAIL PROTECTED] - automatically set the owner of DRI bugs, e.g., by the users adding a DRI keyword, or associating the XFree86 Server-DRI extension component. - Add the possibility to add comments to bugs via e-mail. Bugzilla requires a valid authenticated login. Not possible to do that with email-bugzilla at least currently. Basically I would like to be possible that: - An user adds a bug concerning DRI - The owner is (either manually or automatically) set to [EMAIL PROTECTED], which receives the bug - Any developer on the dri-devel list which has an account on XFree86 Bugzilla can reply and that comment is added to the bug database. Click on the URL in the bugzilla email, the bug comes up, and you can enter a comment directly into bugzilla. Even pine can do this easily. -- Mike A. Harris ftp://people.redhat.com/mharris OS Systems Engineer - XFree86 maintainer - Red Hat ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Invitation for public discussion about the future of X
This is an invitation for anyone and everyone with an interest in X, XFree86, and related technologies and their future to participate in a public and open discussion. Any topics are open to discussion, from those related to administrative and management issues through to technical issues. A new mailing list has been created to provide an open forum for this discussion. To subscribe, go to http://www.xfree86.org/mailman/listinfo/forum/. The list is unmoderated, and you don't need to subscribe to the list in order to post to it. An archive of the list is available at http://www.xfree86.org/pipermail/forum/. This announcement has been blind-copied to all of the XFree86 public lists, but please send followups to the new [EMAIL PROTECTED] list. It has been brought to the attention of the XFree86 Core Team that one of its members, Keith Packard, has been actively (but privately) seeking out support for a fork of XFree86 that would be led by himself. He is also in the process of forming a by-invitation-only group of vested interests to discuss privately concerns he has about XFree86 and the future of X. He has consistently refused to even disclose these concerns within the context of the XFree86 Core Team, which makes his membership of that team unviable. As a consequence, Keith Packard is no longer a member of the XFree86 Core Team. The leaders of the XFree86 project feel that discussing the future of XFree86 and related technologies within a closed group of vested interests is contrary to the spirit of openness and community involvement that many of those vested interests claim to espouse. Instead, the involvement of everyone in a truly open discussion is welcomed by The XFree86 Project, and we invite everyone to express their thoughts, opinions and concerns freely in this open forum. We look forward to hearing and responding to them. The XFree86 Project BOD David Dawes Robin Cutshaw Marc Evans Rich Murphey Jon Tombs David Wexelblat ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
detecting keyboard and monitor particulars...
Hello, Iwanted to ask which part of the XFree86 package (source) deals with detecting keyboard and monitor settings on Linux. Could someone please point me to the correct files and functions ? thanks ManishDo you Yahoo!? Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop!
