On Thu, 8 Jan 2004, David Dawes wrote:
> >> Is needed here for Solaris? I didn't find it necessary for
> >> the Solaris builds I've tried.
> >It provides a prototype for keyboard-cfg.c's and monitor-cfg.c's use of
> >bzero(). An alternative would be to change them to memset()'s.
> Code that u
Hello Egbert;
Egbert Eich wrote:
Hello Lee,
thank you for the patches!
Lee Olsen writes:
> I have completed my tests with my supply of trailing edge hardware, and
> my hercules driver plays
> well with X440. There are two attachments, one is a tar file of the
> hercules driver source and t
On Sun, Apr 04, 2004 at 02:48:54PM -0700, Mark Vojkovich wrote:
> Lets say you have a DFP with a fixed resolution and therefore
>can't run modes with an HDisplay or VDisplay beyond that. What's
>the most efficient way to validate those modes? I see that
>xf86ValidateModes will check pScrn->maxH
Lets say you have a DFP with a fixed resolution and therefore
can't run modes with an HDisplay or VDisplay beyond that. What's
the most efficient way to validate those modes? I see that
xf86ValidateModes will check pScrn->maxHValue and pScrn->maxVValue
for HTotal and VTotal and it supports max
On Sun, Apr 04, 2004 at 12:03:34AM +0200, Egbert Eich wrote:
>David Dawes writes:
> >
> > My point is that this is just one example of a class of problem
> > that is not unique to the vesa driver. Therefore solving it within
> > the vesa driver, while useful, does not solve the underlying problem
Hello Lee,
thank you for the patches!
Lee Olsen writes:
> I have completed my tests with my supply of trailing edge hardware, and
> my hercules driver plays
> well with X440. There are two attachments, one is a tar file of the
> hercules driver source and the other
> is unified diffs in
David Dawes writes:
>
> My point is that this is just one example of a class of problem
> that is not unique to the vesa driver. Therefore solving it within
> the vesa driver, while useful, does not solve the underlying problem.
> Also, this class of problem is not limited to "vintage" hardw
--- Thomas Hellstrom <[EMAIL PROTECTED]> wrote:
> Hi!
>
> Code for bringing the VIA 2d driver up to date with the drm module
> currently in dri.sourceforge.net cvs has been submitted under
> bugzilla 1327
>
> /Thomas
>
Thomas,
If you'd like to keep an up-to-date 2D driver in DRI cvs that
Hi!
Code for bringing the VIA 2d driver up to date with the drm module
currently in dri.sourceforge.net cvs has been submitted under bugzilla 1327
/Thomas
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel
