Software zur Erkennung von "Spam" auf dem Rechner
darkcity.gna.ch
hat die eingegangene E-mail als mögliche "Spam"-Nachricht identifiziert.
Die ursprüngliche Nachricht wurde an diesen Bericht angehängt, so dass
Sie sie anschauen können (falls es doch eine legitime E-Mail ist) oder
ähnliche unerwünschte Nachrichten in Zukunft markieren können.
Bei Fragen zu diesem Vorgang wenden Sie sich bitte an
postmaster
Vorschau: On Wed, 2005-10-26 at 16:09 +0100, Andreas wrote: > >
There are so called "endian conversion mode" flags on all modern pci >
grapics cards which is set by the framebuffer driver to the >
appropriate depth. This however wont work for surfaces which use > other
depths, since the surface gets "fixed up" in the wrong by the > graphics
gard while copying from system ram to video ram. [...]
Inhaltsanalyse im Detail: (5.0 Punkte, 5.0 benötigt)
Pkte Regelname Beschreibung
---- ---------------------- --------------------------------------------------
2.0 RCVD_IN_SORBS_DUL RBL: SORBS: Senderechner nur temporär mit Internet
verbunden
[80.218.113.239 listed in dnsbl.sorbs.net]
3.1 RCVD_IN_XBL RBL: Transportiert via Rechner in XBL-Liste
(http://www.spamhaus.org/xbl/)
[80.218.113.239 listed in sbl-xbl.spamhaus.org]
1.7 RCVD_IN_NJABL_DUL RBL: NJABL: Senderechner nur temporär mit Internet
verbunden
[80.218.113.239 listed in combined.njabl.org]
-1.8 AWL AWL: From: address is in the auto white-list
--- Begin Message ---
On Wed, 2005-10-26 at 16:09 +0100, Andreas wrote:
>
> There are so called "endian conversion mode" flags on all modern pci
> grapics cards which is set by the framebuffer driver to the
> appropriate depth. This however wont work for surfaces which use
> other depths, since the surface gets "fixed up" in the wrong by the
> graphics gard while copying from system ram to video ram.
EXA (the new X.Org acceleration architecture) currently approaches this
problem something like this:
* There are driver hooks that get called before and after CPU
access to any pixmap stored in the framebuffer.
* For cards that allow setting different swapping for different
ranges of the framebuffer, these wrappers set up the ranges and
swapping for the pixmaps.
* Otherwise, if the pixmaps involved in the operation don't all
require the same swapping, the wrapper that gets called before
the access tells EXA to download the pixmaps into system RAM and
do the CPU access there. This requires the driver to provide a
way to download pixmaps that always works correctly of course.
Hope this helps,
--
Earthling Michel Dänzer | Debian (powerpc), X and DRI developer
Libre software enthusiast | http://svcs.affero.net/rm.php?r=daenzer
--- End Message ---
_______________________________________________
directfb-dev mailing list
[email protected]
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
