--- emmanuel ALLAUD <[EMAIL PROTECTED]> a écrit : >
Hi,
> I read your mails on xfree-devel about your wiki
> page.
> I actually had also setup one via the xwin site. The
> link is : http://xwin.org:9673/xwin/XJANITOR
> There are a lot of stuff about compiling XFree and
> also about debugging X
Hi,
I read your mails on xfree-devel about your wiki page.
I actually had also setup one via the xwin site. The
link is : http://xwin.org:9673/xwin/XJANITOR
There are a lot of stuff about compiling XFree and
also about debugging X (using xscope, valgrind for the
mem leaks and other oddities...)
On Tue, Sep 09, 2003 at 03:59:07PM +0200, Egbert Eich wrote:
>Thomas Winischhofer writes:
> >
> > So, why is 1024x600 sorted out on this machine then? (I ask because SiS
> > BIOSes sometimes list wrong modes when probing, and refer to wrong
> > internal modes numbers. I had hoped that Intel folk
Thomas Winischhofer wrote:
Alessandro Temil wrote:
Egbert Eich wrote:
> > David
> Here you are, i attached both i810 and vesa driver XFree86.0.log.
> (by the way, i'm new of this mailing list, if it doesn't allow
messages > with attachments i'll repost them inlined asap.)
> > This moring i
Thomas Winischhofer writes:
>
> So, why is 1024x600 sorted out on this machine then? (I ask because SiS
> BIOSes sometimes list wrong modes when probing, and refer to wrong
> internal modes numbers. I had hoped that Intel folks just forgot to
> change their probe function for this very mac
Alessandro Temil <[EMAIL PROTECTED]> wrote:
> > - Rewrite the i810 driver so it bypasses the BIOS like the Windows
> > driver does. I'm not aware whether Intel would provide the required
> > documentation to the the open source community.
>
> This was the thing i'm inquiring on. Intel seemed to
Alessandro Temil wrote:
Egbert Eich wrote:
> > David
> Here you are, i attached both i810 and vesa driver XFree86.0.log.
> (by the way, i'm new of this mailing list, if it doesn't allow
messages > with attachments i'll repost them inlined asap.)
> > This moring i wrote to intel asking for t
Egbert Eich wrote:
Thomas Winischhofer writes:
>
> It is possible that the BIOS actually knows the mode, but has no VESA
> number for it. I have seen this at least on SiS hardware: SiS BIOSes
> maintain two mode number lists, one with internal mode numbers, one for
> VESA mode numbers. As
Egbert Eich wrote:
> > David
> Here you are, i attached both i810 and vesa driver XFree86.0.log.
> (by the way, i'm new of this mailing list, if it doesn't allow messages
> with attachments i'll repost them inlined asap.)
>
> This moring i wrote to intel asking for the specifications, i ho
Alessandro Temil writes:
> >>Hoewever, I am absolutely astonished that the graphics BIOS on a 1400x1050
> >>panel does not know how to set a 1400x1050 mode. That means, for example,
> >>that the kernel console driver could never set a mode that fills the panel.
> >>
> >>Does the i810 driver
Thomas Winischhofer writes:
>
> It is possible that the BIOS actually knows the mode, but has no VESA
> number for it. I have seen this at least on SiS hardware: SiS BIOSes
> maintain two mode number lists, one with internal mode numbers, one for
> VESA mode numbers. As the i810 BIOS, it h
Tim Roberts writes:
> On Fri, 05 Sep 2003 20:04:19 +0200, Alessandro Temil wrote:
>
> >Christian Zietz wrote:
> >>
> >> The problem is: The current i810 driver does not only read the available
> >> resolutions from the BIOS but also uses the BIOS to set the video mode.
> >> So if the BIOS
Alessandro Temil wrote:
Thomas Winischhofer wrote:
Alessandro Temil wrote:
David Dawes wrote:
On Fri, Sep 05, 2003 at 11:25:35AM -0700, Tim Roberts wrote:
On Fri, 05 Sep 2003 20:04:19 +0200, Alessandro Temil wrote:
Christian Zietz wrote:
The problem is: The current i810 driver does not only
Thomas Winischhofer wrote:
Alessandro Temil wrote:
David Dawes wrote:
On Fri, Sep 05, 2003 at 11:25:35AM -0700, Tim Roberts wrote:
On Fri, 05 Sep 2003 20:04:19 +0200, Alessandro Temil wrote:
Christian Zietz wrote:
The problem is: The current i810 driver does not only read the
available
resol
Alessandro Temil wrote:
David Dawes wrote:
On Fri, Sep 05, 2003 at 11:25:35AM -0700, Tim Roberts wrote:
On Fri, 05 Sep 2003 20:04:19 +0200, Alessandro Temil wrote:
Christian Zietz wrote:
The problem is: The current i810 driver does not only read the
available
resolutions from the BIOS but als
On Fri, Sep 05, 2003 at 11:25:35AM -0700, Tim Roberts wrote:
>On Fri, 05 Sep 2003 20:04:19 +0200, Alessandro Temil wrote:
>
>>Christian Zietz wrote:
>>>
>>> The problem is: The current i810 driver does not only read the available
>>> resolutions from the BIOS but also uses the BIOS to set the vide
On Fri, 05 Sep 2003 20:04:19 +0200, Alessandro Temil wrote:
>Christian Zietz wrote:
>>
>> The problem is: The current i810 driver does not only read the available
>> resolutions from the BIOS but also uses the BIOS to set the video mode.
>> So if the BIOS doesn't know of 1400x1050, it won't set i
Christian Zietz wrote:
Hi,
Alessandro Temil schrieb:
I'm a linux Xfree86 user, and my laptop has an LCD screen with
1400x1050 native resolution. the internal video chipset is an intel
855GM. After some hours of trying i figured out there's no way of
getting that resolution under XFree86, due
Hi,
Alessandro Temil schrieb:
> I'm a linux Xfree86 user, and my laptop has an LCD screen with
> 1400x1050 native resolution. the internal video chipset is an intel
> 855GM. After some hours of trying i figured out there's no way of
> getting that resolution under XFree86, due to the fac
Hi everybody
I'm a linux Xfree86 user, and my laptop has an LCD screen with
1400x1050 native resolution. the internal video chipset is an intel
855GM. After some hours of trying i figured out there's no way of
getting that resolution under XFree86, due to the fact that the current
i810 driver
20 matches
Mail list logo
