Chris Cheney wrote:
>
> I noticed that if you select /dev/gpmdata as your mouse device it still
> includes the detected mouse device (eg /dev/input/mice) this causes a
> problem usually if you are using gpm since gpm and X fight for the main
> device.
Not for /dev/input/mice, it can be opened and
Chris Cheney wrote:
>
> I noticed that if you select /dev/gpmdata as your mouse device it still
> includes the detected mouse device (eg /dev/input/mice) this causes a
> problem usually if you are using gpm since gpm and X fight for the main
> device.
Not for /dev/input/mice, it can be opened an
I noticed that if you select /dev/gpmdata as your mouse device it still
includes the detected mouse device (eg /dev/input/mice) this causes a
problem usually if you are using gpm since gpm and X fight for the main
device. Also it might be good to set the device type of gpmdata to ImPS/2
instead of
I noticed that if you select /dev/gpmdata as your mouse device it still
includes the detected mouse device (eg /dev/input/mice) this causes a
problem usually if you are using gpm since gpm and X fight for the main
device. Also it might be good to set the device type of gpmdata to ImPS/2
instead o
Mark Montague wrote:
>
> Michel Dänzer <[EMAIL PROTECTED]> writes:
>
> > Mark Montague wrote:
> >
> > > Anyway, it might be worth noting with the question that there may be a
> > > severe performance hit for some cards with using UseFBDev.
> >
> > Excuse me? It should have exactly zero impact on
Michel Dänzer <[EMAIL PROTECTED]> writes:
> Mark Montague wrote:
>
> > Anyway, it might be worth noting with the question that there may be a
> > severe performance hit for some cards with using UseFBDev.
>
> Excuse me? It should have exactly zero impact on performance.
You're right with 4.1 I
Mark Montague wrote:
>
> Michel Dänzer <[EMAIL PROTECTED]> writes:
>
> > Mark Montague wrote:
> >
> > > Anyway, it might be worth noting with the question that there may be a
> > > severe performance hit for some cards with using UseFBDev.
> >
> > Excuse me? It should have exactly zero impact on
Michel Dänzer <[EMAIL PROTECTED]> writes:
> Mark Montague wrote:
>
> > Anyway, it might be worth noting with the question that there may be a
> > severe performance hit for some cards with using UseFBDev.
>
> Excuse me? It should have exactly zero impact on performance.
You're right with 4.1 I
Mark Montague wrote:
> Anyway, it might be worth noting with the question that there may be a
> severe performance hit for some cards with using UseFBDev.
Excuse me? It should have exactly zero impact on performance.
--
Earthling Michel Dänzer (MrCooper)\ Debian GNU/Linux (powerpc) devel
Mark Montague wrote:
> Anyway, it might be worth noting with the question that there may be a
> severe performance hit for some cards with using UseFBDev.
Excuse me? It should have exactly zero impact on performance.
--
Earthling Michel Dänzer (MrCooper)\ Debian GNU/Linux (powerpc) deve
Here is what I use on my iMac DV, not sure if it's perfect, but it
works properly for me:
Section "Monitor"
Identifier "Monitor0"
HorizSync31.5 - 70.0
VertRefresh 40.0 - 150.0
ModeLine "1024x768" 78.5 1024 1033 1129 1312 768 769 772 800 +hsync
+vsync
Branden Robinson <[EMAIL PROTECTED]> writes:
> Do you want an xserver-xfree86 debconf question for "UseFBDev"? I only
> need to ask if [ -d /dev/fb ], correct?
Um, checking for /dev/fb only works for a devfs system-- is woody
committed to that? I thought it was optional still, although I haven't
On Fri, Jun 29, 2001 at 04:57:13AM +0200, Michel Dänzer wrote:
> > > Also, some kind of patch adding -fPIC for building static libraries will
> > > have to be applied, or a lot of shared libraries will break on powerpc.
[...]
> My patch there should do IMHO, but I'd like to get some confirmation fr
Branden Robinson wrote:
>
> On Fri, Jun 29, 2001 at 04:57:13AM +0200, Michel Dänzer wrote:
> > > > And why don't you apply the Dashed Bresenham fix as well?
> > >
> > > Because I forgot about it, and don't know where it is.
> >
> > Attached to this mail, for example. :)
>
> Okay, will add.
Thank
On Fri, Jun 29, 2001 at 04:57:13AM +0200, Michel Dänzer wrote:
> > > And why don't you apply the Dashed Bresenham fix as well?
> >
> > Because I forgot about it, and don't know where it is.
>
> Attached to this mail, for example. :)
Okay, will add.
> > Do you want an xserver-xfree86 debconf que
Branden Robinson wrote:
>
> On Fri, Jun 29, 2001 at 04:22:01AM +0200, Michel Dänzer wrote:
> > Branden Robinson wrote:
> > >
> > > I'd like feedback on these packages, please, to the debian-x list.
> >
> > DRI is for Direct Rendering Infrastructure, not Interface.
>
> Whoops. And usually I'm suc
Branden Robinson wrote:
>
> On Thu, Jun 28, 2001 at 03:25:44PM -0700, crombie wrote:
> > feedback for imac, 266mhz, 32mb ram for version 4.1.x
> > gotten via ftp.digex.com
>
> Please mail the list(s), not me privately.
>
> > will not install due to invalid vid modes.
>
> Technically, this isn't
On Thu, Jun 28, 2001 at 03:25:44PM -0700, crombie wrote:
> feedback for imac, 266mhz, 32mb ram for version 4.1.x
> gotten via ftp.digex.com
Please mail the list(s), not me privately.
> will not install due to invalid vid modes.
Technically, this isn't an installation issue, but a configuration i
On Fri, Jun 29, 2001 at 04:22:01AM +0200, Michel Dänzer wrote:
> Branden Robinson wrote:
> >
> > I'd like feedback on these packages, please, to the debian-x list.
>
> DRI is for Direct Rendering Infrastructure, not Interface.
Whoops. And usually I'm such a stickler for correct terminology. I'
Branden Robinson wrote:
>
> I'd like feedback on these packages, please, to the debian-x list.
DRI is for Direct Rendering Infrastructure, not Interface.
It seems you have applied my r128 Xv endianness fix, why don't you mention it
in the changelog? And why don't you apply the Dashed Bresenham
Here is what I use on my iMac DV, not sure if it's perfect, but it
works properly for me:
Section "Monitor"
Identifier "Monitor0"
HorizSync31.5 - 70.0
VertRefresh 40.0 - 150.0
ModeLine "1024x768" 78.5 1024 1033 1129 1312 768 769 772 800 +hsync
+vsync
Branden Robinson <[EMAIL PROTECTED]> writes:
> Do you want an xserver-xfree86 debconf question for "UseFBDev"? I only
> need to ask if [ -d /dev/fb ], correct?
Um, checking for /dev/fb only works for a devfs system-- is woody
committed to that? I thought it was optional still, although I haven'
On Fri, Jun 29, 2001 at 04:57:13AM +0200, Michel Dänzer wrote:
> > > Also, some kind of patch adding -fPIC for building static libraries will
> > > have to be applied, or a lot of shared libraries will break on powerpc.
[...]
> My patch there should do IMHO, but I'd like to get some confirmation f
Branden Robinson wrote:
>
> On Fri, Jun 29, 2001 at 04:57:13AM +0200, Michel Dänzer wrote:
> > > > And why don't you apply the Dashed Bresenham fix as well?
> > >
> > > Because I forgot about it, and don't know where it is.
> >
> > Attached to this mail, for example. :)
>
> Okay, will add.
Than
On Fri, Jun 29, 2001 at 04:57:13AM +0200, Michel Dänzer wrote:
> > > And why don't you apply the Dashed Bresenham fix as well?
> >
> > Because I forgot about it, and don't know where it is.
>
> Attached to this mail, for example. :)
Okay, will add.
> > Do you want an xserver-xfree86 debconf qu
Branden Robinson wrote:
>
> On Fri, Jun 29, 2001 at 04:22:01AM +0200, Michel Dänzer wrote:
> > Branden Robinson wrote:
> > >
> > > I'd like feedback on these packages, please, to the debian-x list.
> >
> > DRI is for Direct Rendering Infrastructure, not Interface.
>
> Whoops. And usually I'm su
Branden Robinson wrote:
>
> On Thu, Jun 28, 2001 at 03:25:44PM -0700, crombie wrote:
> > feedback for imac, 266mhz, 32mb ram for version 4.1.x
> > gotten via ftp.digex.com
>
> Please mail the list(s), not me privately.
>
> > will not install due to invalid vid modes.
>
> Technically, this isn'
On Thu, Jun 28, 2001 at 03:25:44PM -0700, crombie wrote:
> feedback for imac, 266mhz, 32mb ram for version 4.1.x
> gotten via ftp.digex.com
Please mail the list(s), not me privately.
> will not install due to invalid vid modes.
Technically, this isn't an installation issue, but a configuration
On Fri, Jun 29, 2001 at 04:22:01AM +0200, Michel Dänzer wrote:
> Branden Robinson wrote:
> >
> > I'd like feedback on these packages, please, to the debian-x list.
>
> DRI is for Direct Rendering Infrastructure, not Interface.
Whoops. And usually I'm such a stickler for correct terminology. I
>I haven't received any patches for any architectures other than these. I'm
>especially concerned about alpha (from which I at least have a report that
>it built okay) and arm (about which I have heard nothing at all). If I
>don't get any, the next release will be 4.1.0-1.
ARM didn't build when
Branden Robinson wrote:
>
> I'd like feedback on these packages, please, to the debian-x list.
DRI is for Direct Rendering Infrastructure, not Interface.
It seems you have applied my r128 Xv endianness fix, why don't you mention it
in the changelog? And why don't you apply the Dashed Bresenham
rspectively but it still fails.
if you need me to dreg up log files, lemme know.
=>-Original Message-
=>From: Branden Robinson [mailto:[EMAIL PROTECTED]
=>Sent: Thursday, June 28, 2001 2:56 PM
=>To: debian-x@lists.debian.org; [EMAIL PROTECTED]
=>Subject: XFree86 4.1.0-0pre1v2 ava
I'd like feedback on these packages, please, to the debian-x list.
I haven't received any patches for any architectures other than these. I'm
especially concerned about alpha (from which I at least have a report that
it built okay) and arm (about which I have heard nothing at all). If I
don't ge
>I haven't received any patches for any architectures other than these. I'm
>especially concerned about alpha (from which I at least have a report that
>it built okay) and arm (about which I have heard nothing at all). If I
>don't get any, the next release will be 4.1.0-1.
ARM didn't build when
rspectively but it still fails.
if you need me to dreg up log files, lemme know.
=>-Original Message-
=>From: Branden Robinson [mailto:[EMAIL PROTECTED]]
=>Sent: Thursday, June 28, 2001 2:56 PM
=>To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
=>Subject: XFree86 4.1.0-0pre1v2 available f
I'd like feedback on these packages, please, to the debian-x list.
I haven't received any patches for any architectures other than these. I'm
especially concerned about alpha (from which I at least have a report that
it built okay) and arm (about which I have heard nothing at all). If I
don't g
36 matches
Mail list logo
