help
Lestat V
dreameration at gmail.com
Wed Oct 26 02:06:37 PDT 2005
On 10/26/05, xorg-request at lists.freedesktop.org
<xorg-request at lists.freedesktop.org> wrote:
> Send xorg mailing list submissions to
> xorg at lists.freedesktop.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.freedesktop.org/mailman/listinfo/xorg
> or, via email, send a message with subject or body 'help' to
> xorg-request at lists.freedesktop.org
>
> You can reach the person managing the list at
> xorg-owner at lists.freedesktop.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of xorg digest..."
>
>
> Today's Topics:
>
> 1. fontconfig and freetype (Munira Ahmed)
> 2. Re: fontconfig and freetype (Daniel Stone)
> 3. Re: fontconfig and freetype (Munira Ahmed)
> 4. Re: CVS Update: xc (branch: trunk) (Luc Verhaegen)
> 5. Re: CVS Update: xc (branch: trunk) (Thomas Hellstr?m)
> 6. Re: usb mouse (Marcus Sch?fer)
> 7. Re: usb mouse (Marcus Sch?fer)
> 8. Re: fontconfig and freetype (Richard Stellingwerff)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 26 Oct 2005 14:14:13 +0800
> From: Munira Ahmed <munira.ahmed at gmail.com>
> Subject: fontconfig and freetype
> To: xorg at lists.freedesktop.org
> Message-ID:
> <d4783cda0510252314x799e62f7maee0fb05cee340f0 at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> What is the interdepdency of freetype and fontconfig?
>
> I am getting following errors
>
> fcfreetype.c:76:2: warning: #warning "No FT_Get_BDF_Property: Please install
> freetype 2.1.4 or later"
> fcfreetype.c: In function `FcGetPixelSize':
> fcfreetype.c:971: error: structure has no member named `y_ppem'
> fcfreetype.c: In function `FcFontCapabilities':
> fcfreetype.c:2828: warning: implicit declaration of function
> `FT_Load_Sfnt_Table'
> make[2]: *** [fcfreetype.lo] Error 1
> make[2]: Leaving directory `/home/munira/motokit/fontconfig-2.3.91/src'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/home/munira/motokit/fontconfig-2.3.91'
> make: *** [all] Error 2
>
> Can anybody please help me identify the prob
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: http://lists.freedesktop.org/archives/xorg/attachments/20051026/1ea84d3f/attachment-0001.html
>
> ------------------------------
>
> Message: 2
> Date: Wed, 26 Oct 2005 16:28:18 +1000
> From: Daniel Stone <daniel at freedesktop.org>
> Subject: Re: fontconfig and freetype
> To: Munira Ahmed <munira.ahmed at gmail.com>
> Cc: xorg at lists.freedesktop.org
> Message-ID: <20051026062817.GC6601 at fooishbar.org>
> Content-Type: text/plain; charset="us-ascii"
>
> On Wed, Oct 26, 2005 at 02:14:13PM +0800, Munira Ahmed wrote:
> > What is the interdepdency of freetype and fontconfig?
> >
> > I am getting following errors
> >
> > fcfreetype.c:76:2: warning: #warning "No FT_Get_BDF_Property: Please install
> ^^^^^^^^^^^^^^
> > freetype 2.1.4 or later"
> ^^^^^^^^^^^^^^^^^^^^^^^
> > fcfreetype.c: In function `FcGetPixelSize':
> > fcfreetype.c:971: error: structure has no member named `y_ppem'
> > fcfreetype.c: In function `FcFontCapabilities':
> > fcfreetype.c:2828: warning: implicit declaration of function
> > `FT_Load_Sfnt_Table'
> > make[2]: *** [fcfreetype.lo] Error 1
> > make[2]: Leaving directory `/home/munira/motokit/fontconfig-2.3.91/src'
> > make[1]: *** [all-recursive] Error 1
> > make[1]: Leaving directory `/home/munira/motokit/fontconfig-2.3.91'
> > make: *** [all] Error 2
> >
> > Can anybody please help me identify the prob
>
> As the message says ...
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: not available
> Type: application/pgp-signature
> Size: 189 bytes
> Desc: Digital signature
> Url : http://lists.freedesktop.org/archives/xorg/attachments/20051026/fefc944b/attachment-0001.pgp
>
> ------------------------------
>
> Message: 3
> Date: Wed, 26 Oct 2005 14:39:04 +0800
> From: Munira Ahmed <munira.ahmed at gmail.com>
> Subject: Re: fontconfig and freetype
> To: xorg at lists.freedesktop.org
> Message-ID:
> <d4783cda0510252339i7d4dbfc8i4ad86382cb56cbe3 at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> oh i forgot to mention i an using 2.1.4 and yet get this error
>
> On 10/26/05, Munira Ahmed <munira.ahmed at gmail.com> wrote:
> >
> > What is the interdepdency of freetype and fontconfig?
> >
> > I am getting following errors
> >
> > fcfreetype.c:76:2: warning: #warning "No FT_Get_BDF_Property: Please
> > install freetype 2.1.4 or later"
> > fcfreetype.c: In function `FcGetPixelSize':
> > fcfreetype.c:971: error: structure has no member named `y_ppem'
> > fcfreetype.c: In function `FcFontCapabilities':
> > fcfreetype.c:2828: warning: implicit declaration of function
> > `FT_Load_Sfnt_Table'
> > make[2]: *** [fcfreetype.lo] Error 1
> > make[2]: Leaving directory `/home/munira/motokit/fontconfig-2.3.91/src'
> > make[1]: *** [all-recursive] Error 1
> > make[1]: Leaving directory `/home/munira/motokit/fontconfig-2.3.91'
> > make: *** [all] Error 2
> >
> > Can anybody please help me identify the prob
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: http://lists.freedesktop.org/archives/xorg/attachments/20051026/f446d2bb/attachment.htm
>
> ------------------------------
>
> Message: 4
> Date: Wed, 26 Oct 2005 09:31:17 +0200
> From: Luc Verhaegen <libv at skynet.be>
> Subject: Re: CVS Update: xc (branch: trunk)
> To: Discuss issues related to the xorg tree
> <xorg at lists.freedesktop.org>
> Message-ID: <20051026073117.GA23710 at skynet.be>
> Content-Type: text/plain; charset=iso-8859-1
>
> On Wed, Oct 26, 2005 at 12:25:50AM +0200, Thomas Hellström wrote:
> >
> > With the current code, The colorkey is only painted when the overlay is
> > updated, not every frame. Previously it was painted only when the
> > cliprects changed, so it is not a big CPU-eater. What I actually am seeing
> > is that xine sometimes misses the title screen when autopainting is
> > enabled.
> >
> > Even more confusing is the fact that XvPutimage is called with the old set
> > of cliprects when a change in the number of cliprects has triggered an
> > expose event in the player.
> >
> > However, while the above made things better I just saw this happening
> > again, so this is probably a bug in xine-ui, clearing the output window
> > after the colorkey has been autopainted.
> >
> > I'll revert the commit.
> >
> > /Thomas
> >
> I wasn't saying that what you did was wrong, i was just curious as to
> why this happened.
>
> Urgh, yes, this code still checks the RegionsEqual twice... I spent most
> of the summer wondering what those people at VIA were thinking when they
> wrote any of the Xv code. I seem to be suppressing the worst of the bad
> memories.
>
> In that light your choice doesn't seem that negative, as there's already
> one RegionsEqual call less.
>
> X.org already has REGION_EQUAL btw.
>
> This does lead to something else though, namely, why is all this
> colorkey handling down in the DDX? XV_AUTOPAINT and XV_COLORKEY are
> afaik standard. All handling could be in the DIX, with the XV_COLORKEY
> only passed on for the overlay to adjust to. Does the colorkey painting
> need to happen that closely intertwined with other overlay engine stuff?
> Surely with an efficient PutImage, that needn't be the case. It would
> avoid going into ReputImage at all in some cases.
>
> Painting the colorkey right after PutImage might even reduce the effect
> of first-run-garbage. Like on the CLE266A, where the HQV needs to be
> flipped twice for something useful to be presented to the overlay
> engine. It might provide for a smoother transition at overlay start. And
> it does make the DDX code simpler and shorter.
>
> It would break my alpha plane. Any other drivers doing funky stuff with
> the colorkey rects? Maybe some devices need special handling of a
> missing colorkey?
>
> Luc Verhaegen.
>
>
> ------------------------------
>
> Message: 5
> Date: Wed, 26 Oct 2005 10:05:33 +0200 (CEST)
> From: Thomas Hellstr?m <unichrome at shipmail.org>
> Subject: Re: CVS Update: xc (branch: trunk)
> To: "Discuss issues related to the xorg tree"
> <xorg at lists.freedesktop.org>
> Message-ID:
> <27105.192.138.116.230.1130313933.squirrel at 192.138.116.230>
> Content-Type: text/plain;charset=iso-8859-1
>
> > On Wed, Oct 26, 2005 at 12:25:50AM +0200, Thomas Hellström wrote:
>
> >
> > In that light your choice doesn't seem that negative, as there's already
> > one RegionsEqual call less.
> >
>
> Yes, but on the other hand, since the repaint helper takes the cliprects
> as arguments there should be no need to repaint the colorkey when
> cliprects hav not changed. Actually, what seems to be happening on a
> window change is
>
> 1) Putimage is called with new window location / dimensions and old
> cliprects.
> 2) Reputimage is called with new window location and old cliprects.
> 3) Reputimage is called with new cliprects.
>
> It is correct, but seems a bit inefficient.
>
>
> > X.org already has REGION_EQUAL btw.
> >
> > This does lead to something else though, namely, why is all this
> > colorkey handling down in the DDX? XV_AUTOPAINT and XV_COLORKEY are
> > afaik standard. All handling could be in the DIX, with the XV_COLORKEY
> > only passed on for the overlay to adjust to. Does the colorkey painting
> > need to happen that closely intertwined with other overlay engine stuff?
> > Surely with an efficient PutImage, that needn't be the case. It would
> > avoid going into ReputImage at all in some cases.
> >
> > Painting the colorkey right after PutImage might even reduce the effect
> > of first-run-garbage. Like on the CLE266A, where the HQV needs to be
> > flipped twice for something useful to be presented to the overlay
> > engine. It might provide for a smoother transition at overlay start. And
> > it does make the DDX code simpler and shorter.
> >
> > It would break my alpha plane. Any other drivers doing funky stuff with
> > the colorkey rects? Maybe some devices need special handling of a
> > missing colorkey?
> >
>
> Xv can be implemented without overlays. Either using 3D textures (which is
> possible also without DRI), or in the case of the Unichrome PRO A, using
> one HQV for downscaling and color transformation, the other for upscaling
> directly to the frame buffer. There must be a way for the DDX to turn off
> colorkey handling.
>
> >
> > Luc Verhaegen.
>
> /Thomas
>
>
>
> > _______________________________________________
> > xorg mailing list
> > xorg at lists.freedesktop.org
> > http://lists.freedesktop.org/mailman/listinfo/xorg
> >
>
>
>
>
> ------------------------------
>
> Message: 6
> Date: Wed, 26 Oct 2005 10:12:41 +0200
> From: Marcus Sch?fer <ms at suse.de>
> Subject: Re: usb mouse
> To: Discuss issues related to the xorg tree
> <xorg at lists.freedesktop.org>
> Cc: xorg at freedesktop.org
> Message-ID: <20051026081241.GA16588 at suse.de>
> Content-Type: text/plain; charset=iso-8859-15
>
> Hi,
>
> > Would some kind soul please tell me how x.org works with usb mice? I've one
> > (MS USB mouse) that is working fine but xorg.conf shows that it is using
> > the IMPS/2 protocol. As it is a USB mouse, why x.org is using a PS/2 protocol
> > and it is still working? This is in Fedora core 3 (2.6 kernel).
>
> This is because of the kernel input interface. All mice except the serial
> ones are handled by the kernel. The kernel translate the information from
> all connected mice into a explorerPS/2 protocol and send that information
> out to the multiplexer device /dev/input/mice. The raw information from
> the mouse can be accessed by /dev/input/event[X] but I'm pretty sure you
> are using /dev/input/mice or a link to it in your InputDevice section
> of xorg.conf.
>
> The protocols imps/2 and ps/2 are compatible to explorerPS/2. As far
> as I know they are different only in the supported number of buttons.
> That's the reason why it is working for you that way.
>
> Regards
> Marcus
> --
> Public Key available
> -------------------------------------------------------
> Marcus Schäfer (Res. & Dev.) SUSE LINUX Products GmbH
> Tel: 0911-740 53 0 Maxfeldstrasse 5
> FAX: 0911-740 53 479 D-90409 Nürnberg
> http://www.suse.de Germany
> -------------------------------------------------------
>
>
> ------------------------------
>
> Message: 7
> Date: Wed, 26 Oct 2005 10:12:41 +0200
> From: Marcus Sch?fer <ms at suse.de>
> Subject: Re: usb mouse
> To: Discuss issues related to the xorg tree
> <xorg at lists.freedesktop.org>
> Cc: xorg at freedesktop.org
> Message-ID: <20051026081241.GA16588 at suse.de>
> Content-Type: text/plain; charset=iso-8859-15
>
> Hi,
>
> > Would some kind soul please tell me how x.org works with usb mice? I've one
> > (MS USB mouse) that is working fine but xorg.conf shows that it is using
> > the IMPS/2 protocol. As it is a USB mouse, why x.org is using a PS/2 protocol
> > and it is still working? This is in Fedora core 3 (2.6 kernel).
>
> This is because of the kernel input interface. All mice except the serial
> ones are handled by the kernel. The kernel translate the information from
> all connected mice into a explorerPS/2 protocol and send that information
> out to the multiplexer device /dev/input/mice. The raw information from
> the mouse can be accessed by /dev/input/event[X] but I'm pretty sure you
> are using /dev/input/mice or a link to it in your InputDevice section
> of xorg.conf.
>
> The protocols imps/2 and ps/2 are compatible to explorerPS/2. As far
> as I know they are different only in the supported number of buttons.
> That's the reason why it is working for you that way.
>
> Regards
> Marcus
> --
> Public Key available
> -------------------------------------------------------
> Marcus Schäfer (Res. & Dev.) SUSE LINUX Products GmbH
> Tel: 0911-740 53 0 Maxfeldstrasse 5
> FAX: 0911-740 53 479 D-90409 Nürnberg
> http://www.suse.de Germany
> -------------------------------------------------------
>
>
> ------------------------------
>
> Message: 8
> Date: Wed, 26 Oct 2005 10:43:26 +0200
> From: Richard Stellingwerff <remenic at gmail.com>
> Subject: Re: fontconfig and freetype
> To: Discuss issues related to the xorg tree
> <xorg at lists.freedesktop.org>
> Message-ID:
> <3aef9cce0510260143i62afb103w10d6f5fc3490386e at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> On 10/26/05, Munira Ahmed <munira.ahmed at gmail.com> wrote:
> > oh i forgot to mention i an using 2.1.4 and yet get this error
> >
> >
> > On 10/26/05, Munira Ahmed <munira.ahmed at gmail.com > wrote:
> > > What is the interdepdency of freetype and fontconfig?
> > >
> > > I am getting following errors
> > >
> > > fcfreetype.c:76:2: warning: #warning "No FT_Get_BDF_Property: Please
> > install freetype 2.1.4 or later"
> > > fcfreetype.c: In function `FcGetPixelSize':
> > > fcfreetype.c:971: error: structure has no member named `y_ppem'
> > > fcfreetype.c: In function `FcFontCapabilities':
> > > fcfreetype.c:2828: warning: implicit declaration of function
> > `FT_Load_Sfnt_Table'
> > > make[2]: *** [fcfreetype.lo] Error 1
> > > make[2]: Leaving directory
> > `/home/munira/motokit/fontconfig-2.3.91/src'
> > > make[1]: *** [all-recursive] Error 1
> > > make[1]: Leaving directory
> > `/home/munira/motokit/fontconfig-2.3.91'
> > > make: *** [all] Error 2
> > >
> > > Can anybody please help me identify the prob
> > >
>
> Did you forget to install the -dev package (containing the headers) of
> freetype 2.1.4?
>
> Kind regards,
> Richard Stellingwerff.
>
>
> ------------------------------
>
> _______________________________________________
> xorg mailing list
> xorg at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/xorg
>
> End of xorg Digest, Vol 3, Issue 65
> ***********************************
>
More information about the xorg
mailing list