On Thu, 2006-08-10 at 18:23 +0200, jf simon wrote:
> Hi,
>
> For non x86 architecture, I understand that xfree86
> is able to initialize (soft boot) PCI graphic cards, by emulating the VGA
> BIOS extension located on the graphic card.
>
> Does x86 VGA BIOS emulation for powerPC works in xfree86
On Tue, 2006-03-28 at 18:37 +0100, Barry Scott wrote:
> I'm testing the i945G driving a Hitachi panel that has a preferred mode
> of [EMAIL PROTECTED]
> RC2 sets the refresh to 75Hz that is not allowed by the EDID. Attached
> is the config created
> by X -configure and the X log at logverbose 8.
On Thu, 2006-01-26 at 14:31 +, Barry Scott wrote:
> I'm running 4.5.99.18 and having problems with supporting HDReady panels.
> The HDReady panels support [EMAIL PROTECTED] typically.
> Using the i810 driver on a i945G with the i915resolution hack I can
> get the driver to set 1360x768 but not
I thought I'd replied to this, but maybe not.
The current CVS for the intel driver does support gamma correction
on the i865.
Alan.
On Thu, Jun 23, 2005 at 10:35:16AM -0700, Mark Vojkovich wrote:
>While i865G hardware might support gamma correction, the
> XFree86 drivers for it do not. I be
Fixed.
Alan.
On Tue, May 24, 2005 at 07:44:58 +0800, Jeff Chua wrote:
> Latest CVS build has this problem during 'startx' ...
>
> Symbol i830PrintModes from module /usr/X11R6/lib/modules/drivers/i810_drv.o
> is
> unresolved!
>
> Changes prior to May 23 is ok.
>
>
> Thanks,
> Jeff
> _
On Wed, Mar 02, 2005 at 08:27:46AM +, Alan Hourihane wrote:
> On Tue, Mar 01, 2005 at 06:51:54PM -0700, Marc Aurele La France wrote:
> > Hi.
> >
> > I've been auditing various builds and noticed that
> > xc/lib/GL/mesa/drivers/x11 is never built, let al
On Tue, Mar 01, 2005 at 06:51:54PM -0700, Marc Aurele La France wrote:
> Hi.
>
> I've been auditing various builds and noticed that
> xc/lib/GL/mesa/drivers/x11 is never built, let alone referenced. Is this
> an oversight, or can this directory be deleted?
It could be deleted. It's essentially
On Sat, Feb 19, 2005 at 08:17:07PM -0300, Nqnsome wrote:
> Hi Christian,
>
> Thanks for answering.
>
> Christian Zietz wrote:
>
> >I still suppose that your BIOS only recognizes the LCD as a 800x600 one,
> >while the CRT is recognized correctly as being able to display 1024x768.
> >The Windows X
Actually,
>From the look of your log file, the 1024x768 mode isn't supported at all
on your LCD. And although your LCD is reported at 1024x768 it looks
like your BIOS is broken.
ModeAttributes should show 0x9b, whereas it's showing 0x9a.
That first bit is dictating whether XFree86 allows the mod
Can you provide a log with that driver ?
Alan.
On Sat, Feb 19, 2005 at 12:57:38AM -0300, Nqnsome wrote:
> Hi,
>
> I tryed your driver, but could not get 1024x768 on the LCD. XFree does
> not see the "Built-in" 1024x768 mode.
>
> Thanks,
>
> S?rgio
>
On Fri, Feb 18, 2005 at 03:39:28PM -0800, Bukie Mabayoje wrote:
> Alan Hourihane wrote:
>
> >
> > >
> > > I became aware of this problem few years back (since 2003). The first
> > > time I experienced it was with a DELL laptop, and I didn't h
On Fri, Feb 18, 2005 at 02:11:48PM -0800, Bukie Mabayoje wrote:
> Nqnsome wrote:
>
> > Hi,
> >
> > Thanks again.
> >
> > Alex Deucher wrote:
> >
> > >>Alex is correct. Let focus on the primary display controller on
> > >>PCI:0:2:0 with Display Pipe A and Display Pipe B.
> > >>In your case you ca
On Fri, Feb 18, 2005 at 06:15:16PM -0300, Nqnsome wrote:
> Thanks a lot for the explanations, but I would like to return to the
> question "why the CRT works under 1024x768 and the LCD not". Can this be
> related to the VESA VBE DCC that does not work on the LCD?
If you boot up on the LCD and ha
Hi Jong,
You can submit it via [EMAIL PROTECTED] or via bugzilla database at
http://bugs.xfree86.org and create an attachment with the patch.
Use the 'diff -u' command to create a unified diff makes it easier to
see the changes you made.
Thanks for your future submission,
Alan.
On Fri, Feb 18,
On Tue, Feb 08, 2005 at 08:14:59PM -0500, David Dawes wrote:
> On Tue, Feb 08, 2005 at 11:52:27PM +0000, Alan Hourihane wrote:
> >On Tue, Feb 08, 2005 at 06:40:07PM -0500, David Dawes wrote:
> >> On Tue, Feb 08, 2005 at 11:24:43PM +0000, Alan Hourihane wrote:
> >> >
On Tue, Feb 08, 2005 at 06:40:07PM -0500, David Dawes wrote:
> On Tue, Feb 08, 2005 at 11:24:43PM +0000, Alan Hourihane wrote:
> >On Tue, Feb 08, 2005 at 06:17:50PM -0500, David Dawes wrote:
> >> On Tue, Feb 08, 2005 at 05:12:29PM +0000, Alan Hourihane wrote:
> >> >
On Tue, Feb 08, 2005 at 06:17:50PM -0500, David Dawes wrote:
> On Tue, Feb 08, 2005 at 05:12:29PM +0000, Alan Hourihane wrote:
> >On Tue, Feb 08, 2005 at 11:59:15AM -0500, David Dawes wrote:
> >> On Tue, Feb 08, 2005 at 04:40:42PM +0000, Alan Hourihane wrote:
> >> >
On Tue, Feb 08, 2005 at 11:59:15AM -0500, David Dawes wrote:
> On Tue, Feb 08, 2005 at 04:40:42PM +0000, Alan Hourihane wrote:
> >On Tue, Feb 08, 2005 at 11:32:56AM -0500, David Dawes wrote:
> >> It looks like the DRM kernel source in xc/extras/drm is broken and
> >> inc
On Tue, Feb 08, 2005 at 11:32:56AM -0500, David Dawes wrote:
> It looks like the DRM kernel source in xc/extras/drm is broken and
> incomplete, especially for BSD platforms. The Linux version only
> appears to build for a narrow range of kernels, and this either
> needs to be fixed, or the minimum
On Mon, Jan 31, 2005 at 07:27:51PM -0500, David Dawes wrote:
> On Mon, Jan 31, 2005 at 09:20:06AM +0000, Alan Hourihane wrote:
> >On Sun, Jan 30, 2005 at 08:11:38PM -0500, David Dawes wrote:
> >> Has anyone tried DRI on an i810 with the current tree? I get a
> >>
On Sun, Jan 30, 2005 at 08:11:38PM -0500, David Dawes wrote:
> Has anyone tried DRI on an i810 with the current tree? I get a
> ring buffer lockup almost immediately after running glxgears. This
> is with the current i810 DRM module built and loaded against an
> otherwise stock 2.4.24 kernel.
I
On Mon, Jan 10, 2005 at 11:00:22PM -0500, David Dawes wrote:
> On Mon, Jan 10, 2005 at 08:43:18AM +, Matthias Scheler wrote:
> >On Sat, Jan 08, 2005 at 07:37:29PM -0500, David Dawes wrote:
> >> The schedule for the next XFree86 release -- 4.5.0 is as follows:
> >>
> >>26 January 2005
On Wed, Jun 30, 2004 at 10:28:06AM -0700, Torrey Lyons wrote:
> I've written up some documentation on the generic rootless layer in
> Xserver/miext/rootless. What is the appropriate place and format for
> this kind of documentation in the tree?
For now, I'd probably stick it into the same direct
On Tue, Jun 29, 2004 at 02:18:10AM +0200, Thomas Winischhofer wrote:
> David Dawes wrote:
> >On Mon, Jun 28, 2004 at 05:44:14PM +0100, Dr Andrew C Aitchison wrote:
> >
> >>On Mon, 28 Jun 2004, Andrew C Aitchison wrote:
> >>
> >>
> >>>CVS compile works for me since this change
> >>> revision 3.479
On Tue, Jun 22, 2004 at 10:53:59AM +0530, Suresh wrote:
>Hi,
>
>
>
>I am using Voyager CF card for exporting display to the VGA monitor my
>handheld runs Xfbdev. Can any one tell me how to configure.
The Voyager CF isn't supported by Xipaq. As for Xfbdev, it would require
a kernel d
Have you tried adding
Option "VBERestore" "false"
Alan.
On Mon, Apr 12, 2004 at 10:37:34AM +0800, Jeff Chua wrote:
> I've checked the CVS, and found that the i810 driver up to 4_3_99_9 works
> after resume, but anything after 4_3_99_9 has the same problem of
> displaying black screen after apm r
On Fri, Apr 09, 2004 at 05:44:31PM +0200, root wrote:
> I think there's a bug in the acceleration code of the s3 driver. When scrolling
> (with acceleration enabled), only parts of the screen that become newly visible
> really get visible, the screen doesn't scroll up. XaaNoScreenToScreenCopy opt
On Wed, Apr 07, 2004 at 01:06:55PM -0600, Mark Cuss wrote:
> Hello again
>
> I have an application running on this machine that decodes MPEG-2 into a
> window and then draws overlays on top of the video using a colorkey. This
> works on other hardware combinations (ie - an Intel 810, anything nVi
> - Original Message -
> From: "Alan Hourihane" <[EMAIL PROTECTED]>
> To: "Mark Cuss" <[EMAIL PROTECTED]>
> Cc: "X Developers List" <[EMAIL PROTECTED]>
> Sent: Wednesday, April 07, 2004 9:33 AM
> Subject: Re: Intel 82852 &a
On Wed, Apr 07, 2004 at 09:28:39AM -0600, Mark Cuss wrote:
> Hi All
>
> I have a laptop with an Intel 82852/855GM Integrated graphics chipset. The
> machine is running RedHat 9 with the new 4.4.0 X Server. I'd like to use
> the XVideo extension on the machine, but xvinfo reports that no adaptors
Mark,
What's the current status of the new xaa ??
Alan.
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel
I remember that a couple of extra tests failed with Xinerama enabled.
The ones I'm seeing are XCopyArea and XCopyPlane. Are these the ones
that are expected to fail - Mark V. ?
Alan.
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/li
On Sun, Mar 07, 2004 at 12:20:23PM -0500, Carl Nygard wrote:
>
> I've got a Thinkpad T40 running Fedora Core 1 (XFree86-4.3.0-42) and the
> VESA framebuffer (not sure that matters). When I run the attached
> simple program, I get problems with the fills when using Stipples. The
> whole object in
On Tue, Mar 02, 2004 at 11:43:34AM +0100, Thomas Winischhofer wrote:
> Alan Hourihane wrote:
> >>
> >>I prefer option 2 because of its fewer levels of SubSections.
> >>
> >>What's the replacement for the metamodes option/concept? Will this
> >>
On Tue, Mar 02, 2004 at 01:16:05AM +0100, Thomas Winischhofer wrote:
> Alan Hourihane wrote:
> >I'm looking to enhance the parser in XFree86 so that a lot of redundant
> >code in the current drivers that implement the 'mergedfb' mode can
> >be eliminated suc
On Mon, Mar 01, 2004 at 04:19:21PM -0800, Mark Vojkovich wrote:
> The current XAA has functions starting with "XAA" and header files
> starting with "xaa". To avoid namespace pollution, the second
> implementation of XAA will need a different namespace. It seems
> good to avoid calling it any
On Mon, Mar 01, 2004 at 04:19:21PM -0800, Mark Vojkovich wrote:
> The current XAA has functions starting with "XAA" and header files
> starting with "xaa". To avoid namespace pollution, the second
> implementation of XAA will need a different namespace. It seems
> good to avoid calling it any
On Mon, Mar 01, 2004 at 04:11:02PM -0800, Mark Vojkovich wrote:
> And please don't break binary compatibility with drivers who
> parse the current Monitor info in the ScrnInfoRec.
Absolutely, that is a main priority, as is allowing the new XFree86 server
to still parse older XF86Config files.
Ala
On Mon, Mar 01, 2004 at 02:57:50PM -0800, Alex Deucher wrote:
> --- Alan Hourihane <[EMAIL PROTECTED]> wrote:
> > I'm looking to enhance the parser in XFree86 so that a lot of
> > redundant
> > code in the current drivers that implement the 'mergedfb'
On Mon, Mar 01, 2004 at 10:10:40PM +, Alan Hourihane wrote:
> I'm looking to enhance the parser in XFree86 so that a lot of redundant
> code in the current drivers that implement the 'mergedfb' mode can
> be eliminated such that they don't have to do all the mo
I'm looking to enhance the parser in XFree86 so that a lot of redundant
code in the current drivers that implement the 'mergedfb' mode can
be eliminated such that they don't have to do all the monitor munging
in the driver.
So here's two variants of the modifications to the XF86Config I'm
thinking
On Tue, Feb 24, 2004 at 01:37:27PM +0100, Egbert Eich wrote:
> Christian,
>
> thank you for the investigation. It proves that we are not to blame.
> It remains to see what should be done about it. Disabling the offending
> function by default for all future doesn't seem to be a good idea as
> the
On Mon, Feb 23, 2004 at 07:29:32PM +0100, Christian Zietz wrote:
> Hi,
>
> Alan Hourihane schrieb:
>
> > Is there a string 'DELL' or similar in the BIOS that we can use the
> > function xf86ReadBIOS() to detect this buggy BIOS and skip using this
> > fun
On Mon, Feb 23, 2004 at 06:19:46PM +0100, Christian Zietz wrote:
> Hi,
>
> Egbert Eich schrieb:
>
> > I think it would be worthwhile to investigate the origin or the problem
> > and report it to Intel to fix it in the BIOS - in case they have broken
> > something. It looks like an endless loop to
On Fri, Feb 20, 2004 at 12:33:41PM +0100, Alain Poirier wrote:
> Le vendredi 20 Février 2004 01:33, Alan Hourihane a écrit :
> > Alain,
> >
> > Can you try the int10 emulator ?
> >
> > To do this, (re)move this file out of the way.
> >
> > /usr/X1
Alain,
Can you try the int10 emulator ?
To do this, (re)move this file out of the way.
/usr/X11R6/lib/modules/linux/libint10.a
Then XFree86 will use
/usr/X11R6/lib/modules/libint10.a
Which is the emulator. Does it still lockup with that BIOS call ?
Alan.
_
On Thu, Feb 19, 2004 at 11:17:03PM +0100, Alain POIRIER wrote:
> Hi,
>
> > > Christian Zietz writes:
> > > Hi,
> > >
> > > as developer of 855patch I get a lot of feedback from people using
> > > XFree86 on computers with i855GM graphics.
> > > It seems like new notebooks by Dell feature a new vi
On Fri, Feb 13, 2004 at 10:58:38AM +0800, Yukun Chen wrote:
> Hi All
>
> For some reasons, I have to compile XFree864.2 on SELS 8.2(64bit) with
> AMD64bit CPU. But when I run "make World>&World.log" on the specific dir, I just get
> the error
>
> message in my World.log file as follows:
On Tue, Feb 10, 2004 at 10:33:24PM -0500, David Dawes wrote:
> Just using atof() should work. Or better, add __glXAtof() to
> glx_ansic.h.
Your right David. I should allow time for testing next time :-)
committed.
Alan.
___
Devel mailing list
[EMAIL P
On Tue, Feb 10, 2004 at 06:20:25PM -0800, Torrey Lyons wrote:
> At 10:11 AM -0800 1/28/04, Alan Hourihane wrote:
> >Log message:
> > 778. Fix Multitexture problems with vertex arrays and indirect rendering
> >(Bugzilla #1092, DRI Project).
> > 777. Fix Sec
On Tue, Feb 10, 2004 at 02:34:54PM -0800, Torrey Lyons wrote:
> At 3:46 PM -0800 2/9/04, Alan Hourihane wrote:
> >CVSROOT: /home/x-cvs
> >Module name: xc
> >Changes by: [EMAIL PROTECTED] 04/02/09 15:46:31
> >
> >Log message:
> > 797. Fix G
On Thu, Feb 05, 2004 at 08:57:47PM +0100, David Gómez wrote:
> Hi all ;),
>
> I got an X crash with X 4.3.0, here is the error log.
>
> By the way, are there many bugfixes in the i830 driver for the upcoming
> 4.4.0 release? Maybe i'm asking for a problem already fixed in CVS...
You should try i
On Thu, Feb 05, 2004 at 11:21:32AM -0700, Terry R. Friedrichsen wrote:
> Building on FreeBSD/Alpha version 5.2 with gcc 3.3.3:
>
> In building the world from a Wednesday morning CVS update, g_render.c
> in xc/programs/Xserver/GL/glx failed to compile. The root problem
> was a missing right paren,
On Tue, Feb 03, 2004 at 12:38:16AM +1300, dave wrote:
>
> - Original Message -
> From: "Alan Hourihane" <[EMAIL PROTECTED]>
> To: "dave" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Monday, February 02, 2004 11:39 PM
&g
On Mon, Feb 02, 2004 at 11:35:23PM +1300, dave wrote:
>
> - Original Message -
> From: "Alan Hourihane" <[EMAIL PROTECTED]>
> To: "dave" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Monday, February 02, 2004 10:50 PM
&g
On Mon, Feb 02, 2004 at 06:34:40PM +1300, dave wrote:
> Hi I have just go my computers up and running and am ready to
>
> Start my X11 driver I have downloaded the latest dev-4.3.99.902
>
> The drivers directory name will be nvxf
>
> So can some one give a quick start help about how to enter my
On Tue, Jan 27, 2004 at 02:21:42PM -0500, David Dawes wrote:
> On Tue, Jan 27, 2004 at 06:45:10PM +0000, Alan Hourihane wrote:
> >On Tue, Jan 27, 2004 at 12:37:51PM -0500, David Dawes wrote:
> >> There are quite a few Radeon-related bugs still outstanding in
> >>
On Tue, Jan 27, 2004 at 12:37:51PM -0500, David Dawes wrote:
> There are quite a few Radeon-related bugs still outstanding in
> bugs.xfree86.org, including several related to DRI lockups.
>
> Has anyone followed them up?
David,
I suspect not with XFree86's DRI drivers still being based on Mesa 4
On Mon, Jan 12, 2004 at 03:39:22PM +0800, Yukun Chen wrote:
> Hi All
>
> I am a developer from XGI Technology which is a new company stem from graphic
> dpt. of Trident and graphic dpt. of Sis. Now we want to share our linux 2D driver
> with open
>
> source community. Then what should w
On Tue, Dec 23, 2003 at 02:02:20PM -0500, Thomas Dickey wrote:
> On Tue, 23 Dec 2003, Harold L Hunt II wrote:
>
> > The following CVS commit, made by Thomas Dickey, has no indication that
> > Thomas was either a) not involved at all in the patch or b) that Thomas
> > found Ralf Habacker's patch an
On Thu, Dec 18, 2003 at 09:56:01AM -0800, Keith Packard wrote:
> Around 14 o'clock on Dec 18, Alan Hourihane wrote:
>
> > Is this patch reasonable or too much (it does fix the problem) but I'm
> > wondering if the bounds are too strict for PutImage ?
>
> Pr
On Thu, Dec 18, 2003 at 10:19:47AM -0500, David Dawes wrote:
> I did get lots of spurious results with the early versions of the
> new xtest scripts I added to make testing easier. The latest version
> (4.0.1) seems to be pretty stable now though.
I needed this to get the run.sh script to work pr
On Thu, Dec 18, 2003 at 03:03:35PM +, Alan Hourihane wrote:
> On Wed, Dec 17, 2003 at 11:59:00PM -0500, David Dawes wrote:
> > I've been catching up on the 4.4 RC1 test/bug reports after being out
> > of action for the last few days. Judging from the reports coming in
On Wed, Dec 17, 2003 at 11:59:00PM -0500, David Dawes wrote:
> I've been catching up on the 4.4 RC1 test/bug reports after being out
> of action for the last few days. Judging from the reports coming in
> both here and in bugzilla, there's a good amount of testing happening,
> which is great. Som
Looking at ProcShmGetImage() there's a bunch of checking for out-of-bounds
coordinates, but ProcShmPutImage() lacks this checking.
Is this patch reasonable or too much (it does fix the problem) but I'm
wondering if the bounds are too strict for PutImage ?
Alan.
Index: shm.c
=
On Wed, Dec 17, 2003 at 03:08:03PM -0800, Mark Vojkovich wrote:
>I don't think it's as bad as you think. It looks to me like
> this comes about due to a difference in the Shm protocol. Going
> against convention, xShmPutImageReq has an unsigned value for the
> src X and Y location. All other
On Wed, Dec 17, 2003 at 03:08:03PM -0800, Mark Vojkovich wrote:
>I don't think it's as bad as you think. It looks to me like
> this comes about due to a difference in the Shm protocol. Going
> against convention, xShmPutImageReq has an unsigned value for the
> src X and Y location. All other
to the unsigned 15 bit coordinate
> system. Can somebody try that to see if it fixes the problem?
>
> Mark.
>
>
> On Wed, 17 Dec 2003, Alan Hourihane wrote:
>
> > Having looked at Bugzilla #978 it shows that it's very easy to crash
> >
Having looked at Bugzilla #978 it shows that it's very easy to crash
the Xserver when using out-of-bounds coordinates that get mixed up when
passing in int's that get converted to short's during the client->server
conversation.
Seeing as PutImage gets pushed through the CopyArea path, I'm sure
th
On Mon, Dec 08, 2003 at 03:17:20PM -0800, Kendall Bennett wrote:
> Sergey Babkin <[EMAIL PROTECTED]> wrote:
>
> > -- cut here ---
> > *** decode.c.0 Thu Dec 4 15:42:51 2003
> > --- decode.cThu Dec 4 17:15:29 2003
> > ***
> > *** 699,705
> > --- 6
Yes, it was committed by Egbert on 8th October.
Alan.
On Mon, Dec 08, 2003 at 08:49:40AM -0800, Alex Deucher wrote:
> I looked through the cvs commit archives and I never saw that the fix
> for 661 was committed. I don't have the hardware so I can't test.
>
> Alex
>
> --- David Dawes <[EMAIL P
6:09PM +, Raymond Jennings wrote:
> Could you fudge it so that the VESA driver just sets standard modes and
> passes custom modes and all other requests to the default driver? That way
> you wouldn't miss out on any acceleration. I was talking about only using
> VESA to set t
vely. I'm sure it affects more
users too.
You don't have to get the latest version though either, although it's
that's best.
Alan.
On Mon, Nov 24, 2003 at 09:33:04PM +, Raymond Jennings wrote:
> So if I got the latest version, and decided to change video modes, would
On Mon, Nov 24, 2003 at 09:19:01PM +, Raymond Jennings wrote:
> I was wondering if we could make some use of the VESA VGA extension, to set
> video modes at least. That would eliminate all of the video mode problems,
> such as bad offsets, out of sync, and scanline problems. The VESA standa
On Thu, Oct 30, 2003 at 10:59:41AM -0600, Billy Biggs wrote:
> Alan Hourihane ([EMAIL PROTECTED]):
>
> > I've actually already done it, but I'll probably leave it till after
> > XFree86 4.4.0.
>
> Regarding bug 830, does this mean my users can expect to some
2003 at 07:36:42AM -0800, Alex Deucher wrote:
> I'll take a look at fixing this in the radeon driver. What needs to be
> done to play nice with the DRI?
>
> Alex
>
> --- Alan Hourihane <[EMAIL PROTECTED]> wrote:
> > On Thu, Oct 30, 2003 at 07:47:06AM -0600
On Thu, Oct 30, 2003 at 07:47:06AM -0600, Billy Biggs wrote:
> Alan Hourihane ([EMAIL PROTECTED]):
>
> > Well, if someone else has a chip, or wants to update and test other
> > drivers (but be careful with DRI enabled drivers as it needs more work
> > in the driver
Andrew,
I've just committed a patch to the trident driver to enable it.
Best use that as the basis for the neomagic work.
Alan.
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel
On Thu, Oct 30, 2003 at 11:06:45AM +, Alan Hourihane wrote:
> On Thu, Oct 30, 2003 at 10:07:13AM +0000, Alan Hourihane wrote:
> > On Thu, Oct 30, 2003 at 08:09:05AM +, Andrew C Aitchison wrote:
> > > On Wed, 29 Oct 2003, Alan Hourihane wrote:
> > >
> >
On Thu, Oct 30, 2003 at 10:07:13AM +, Alan Hourihane wrote:
> On Thu, Oct 30, 2003 at 08:09:05AM +, Andrew C Aitchison wrote:
> > On Wed, 29 Oct 2003, Alan Hourihane wrote:
> >
> > > On Wed, Oct 29, 2003 at 12:26:45PM -0800, Alex Deucher wrote:
> > > &
On Thu, Oct 30, 2003 at 08:09:05AM +, Andrew C Aitchison wrote:
> On Wed, 29 Oct 2003, Alan Hourihane wrote:
>
> > On Wed, Oct 29, 2003 at 12:26:45PM -0800, Alex Deucher wrote:
> > > As I recall we had problems with allocating additional memory for Xv on
> >
On Wed, Oct 29, 2003 at 12:26:45PM -0800, Alex Deucher wrote:
> As I recall we had problems with allocating additional memory for Xv on
> neomagic chips (hence the overly_mem option). As I recall there was an
> issue with allocating memory beyond the limits of the blitter, similar
> to the problem
On Mon, Oct 27, 2003 at 11:35:20AM -0500, Harold L Hunt II wrote:
> 6) Alternatives are being evaluated for hosting Cygwin/XFree86 code in
> CVS. Hosts that can provide CVS commit access for at least five
> Cygwin/XFree86 developers will be given priority.
Harold,
I thought you already had the
On Mon, Oct 20, 2003 at 11:18:50AM -0400, Norman Walsh wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I'm trying to get XFree up and running on my Tecra 8200 (under Debian
> unstable). I've given up on 1400x1050 resolution and would now just be
> happy with reasonable performance at
On Wed, Oct 15, 2003 at 09:50:40AM -0700, Tim Roberts wrote:
> Some months ago, VIA released an XFree86 Savage driver in source form that
> included, among other things, a DRI driver and XvMC support.
>
> Has that code been integrated into the XFree86 source tree? Will it make
> XFree86 4.4? Or
On Wed, Sep 10, 2003 at 06:24:13PM +0200, Michel Dänzer wrote:
> On Wed, 2003-09-10 at 18:11, Alan Hourihane wrote:
> > On Wed, Sep 10, 2003 at 06:05:42PM +0200, Michel Dänzer wrote:
> > > On Wed, 2003-09-10 at 17:55, Alan Hourihane wrote:
> > > > On Wed, Sep 10, 20
On Wed, Sep 10, 2003 at 06:05:42PM +0200, Michel Dänzer wrote:
> On Wed, 2003-09-10 at 17:55, Alan Hourihane wrote:
> > On Wed, Sep 10, 2003 at 05:41:23PM +0200, Michel Dänzer wrote:
> > > On Wed, 2003-09-10 at 17:09, Jim Gettys wrote:
> > > >
> > >
On Wed, Sep 10, 2003 at 05:41:23PM +0200, Michel Dänzer wrote:
> On Wed, 2003-09-10 at 17:09, Jim Gettys wrote:
> >
> > While the X server has had the XSync extension for a long time,
> > the operating system "hooks" to allow X to synchronize with
> > external events (e.g. vertical sync, sample cl
Doesn't the 'dummy' video driver that's already in XFree86 do most of that
anyway ?
Alan.
On Thu, Aug 21, 2003 at 03:04:00PM +0100, Mark McLoughlin wrote:
> Hey,
> I've done some work on porting the vfb device to new device driver
> interface. See:
>
> http://www.skynet.ie/~mark/pub
On Sun, Aug 10, 2003 at 02:27:13PM +1000, Carsten Haitzler wrote:
> Would I be correct in the assumption that the only accelerated path for xrender
> is the identity transform (1:1 scale)? all other transforms are done in
> software? (my initial tests here with xfree86 4.3.0 & nvidia's latest drive
Sounds like your using an old cvsup binary with glibc-2.3. This is exactly
what I got.
You need to recompile cvsup for glibc-2.3.
I suspect as you work for RedHat, you've probably upgraded to RH9.
Alan.
On Fri, Aug 08, 2003 at 12:09:30PM -0400, John Dennis wrote:
> I had been using cvsup succes
On Fri, Jul 11, 2003 at 05:20:16PM -0700, Tim Roberts wrote:
> I've recently been made aware of the XFree86 Savage driver that VIA released
> and is now available on Alan Hourihane's web site. This driver is so much
> superior to the one I've been maintaining that I should be embarrassed.
>
> M
On Thu, Jul 10, 2003 at 08:40:27AM -0700, Alex Deucher wrote:
> I just saw this on VIA's website. It looks like they just took Alan's
> code and added some tv features (or perhaps just re-released his
> code?). I don't know if there are already in CVS or not, but for what
> it's worth here's the
On Thu, Jul 10, 2003 at 08:40:27AM -0700, Alex Deucher wrote:
> I just saw this on VIA's website. It looks like they just took Alan's
> code and added some tv features (or perhaps just re-released his
> code?). I don't know if there are already in CVS or not, but for what
> it's worth here's the
On Tue, Jul 08, 2003 at 10:25:40AM +0200, Egbert Eich wrote:
> Bugzilla #434 shows a x11perf regression test between 4.3.0 and a rather
> current CVS versions. The performance of some tests has gone down by
> >20% for a specific test, some other tests have suffered a performance
> penalty of >3%.
>
On Fri, Jul 04, 2003 at 10:54:22PM +0200, Matthieu Herrb wrote:
> Alan Hourihane wrote (in a message from Friday 4)
> > With the latest CVS 'fontstosfnt' doesn't build on FreeBSD on presumably
> > other OS's too, due to the lack of .
> >
> > A
With the latest CVS 'fontstosfnt' doesn't build on FreeBSD on presumably
other OS's too, due to the lack of .
A heads up for those maintaining it, and can you produce a fix ?
Alan.
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/list
On Wed, Jun 18, 2003 at 03:54:46PM -0400, Dominic Duval wrote:
> Hello,
>
> I'm currently trying to configure X for a frame buffer device which can
> _only_ be accessed in 16-bit. It's a long story, but accessing the frame
> buffer memory in 8 or 32 bits is just not possible with our current
> har
On Mon, Jun 02, 2003 at 04:30:11PM -0600, Mark Cuss wrote:
> Hello
>
> I'm not sure if this is an X problem or not - if not, please let me know...
>
> I have a Toshiba Satellite 2450 notebook on which I've recently installed RedHat 8.
> Everything works OK, except that sometimes in X when I typ
On Sun, Jun 01, 2003 at 07:20:57PM +0200, Juliusz Chroboczek wrote:
> Is it me, or are we really shipping 1200dpi bitmap fonts as part of
> XFree86?
>
> xc/programs/Xserver/XpConfig/C/print/models/SPSPARC2/fonts/Courier.pmf
These have always been there. It's part of the Xprint server.
Alan.
__
1 - 100 of 126 matches
Mail list logo
