Re: X apparently not releases memory

[J. Imlay]

>
> Why not use depth 16?
>
> AFAIK depth 16 is a 2 bytes not much difference from 15 (almost 2 bytes)
> what makes it worth over depth 16?

In memory if you want to write bits that don't fit nice on a byte, you
have to,

y = 10101b; /* or however you specify 5 bits you want to go at the
begining of the next byte */
y << 3;

x = curent_destination_byte;
z = x & 0111b
x = z | y

You have to do this to do every single pixel write with 15bit color. With
16bit color all the bytes are even so it's just

dest = val;

But I might be completly wrong with this, as I'm not sure you can writing
anything other 32bits anyways anymore. And it might even be 128bits. I
havn't done much with asm on anything newer than 8086.

So my question is, Does the processor have to do the & | = bit on every
byte right so it's just optimized the point that it's a non issue? Or
from a speed standpoint is it still more optimal to use 8,16, or 32 bit
color because you can just assign the bytes.

Another possiblity is that the memory write call takes 100x longer than
the | and & because it has to use the bus for video (or even if it's in
cache it's still slower than registers) so that makes it a non issue.

Thanks,

Josie Imlay


>
> --
> Carlos Barros.
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
>
>

Re: have i to uncomment module xtt ?

[J. Imlay]

> Not by default it didn't:

ok  * feeling very very stupid at the moment *

I do seem to recall something about hitting that check box...



sorry about that (me == BIGIDIOT) => True

Re: have i to uncomment module xtt ?

[J. Imlay]

>  The bitmap, freetype, speedo, type1, and xtt modules are all font
>  rasterizers.  The freetype and xtt modules should not be enabled at the same
>^^
>  time, as they are incompatible.  The freetype module should be used for
>  ^^
>  Western languages and anti-aliased font support; the xtt module should be
>  used for East Asian character set support (specifically, for CID-keyed
>  fonts).
>
> /me yet again wonders why he bothers to write documentation that no one reads.

I have read lots of documentation lately, including the xfree86 docs for
this, and all they say is to use one or the other (which is obvious from
the symbol conflic error it throws) but not which one, or why there is two
of them. I never did figure out which one to use.

So thanks, now I do.

And actually the reason I even came accross this was last time I ran
apt-get upgrade on my friends machine, (debian unstable) it upgraded her
XFree86 and the configure scripts uncommented both and rather broke Xf86.
I probably should have filed a bug report but I don't really have any more
specific information.

Just letting you know that this is(was) something that happens.

Thanks,

Josie Imlay

> :(
>
> --
> G. Branden Robinson| Organized religion is a sham and a
> Debian GNU/Linux   | crutch for weak-minded people who
> [EMAIL PROTECTED] | need strength in numbers.
> http://people.debian.org/~branden/ | -- Jesse Ventura
>

Re: .Xdefaults seems broken

[J. Imlay]

> >$HOME/.Xresources
> >   contains X resources specific to the  invoking  user's  
> > environ-
> >   ment.   The  settings  are  loaded  with xrdb -merge.  Note 
> > that
> >   $HOME/.Xdefaults is a relic from X Version 10 (and X11R1)  
> > days,
> >   before  app-defaults files were implemented.  It has been 
> > depre-
> >   cated for over ten years at the time  of  this  writing.   
> > .Xre-
> >   sources should be used instead.
>
> Mmm, following this, i renamed my .Xdefaults- to .Xresources,
> and since then my xterm ignores those changes, so maybe there is
> something more going on here (but then, as you well know, i am mostly
> ignorant of how this really work/should work).

What I have noticed about this is that .Xresouces does indeed work for
controlling xterm and what not, but you have to restart X (or at least log
in again) in order for the changes to take effect, where as with
.Xdefault the changes took place imeadiatly. And I'm still slightly
confused as to why .Xdefaults seems to work all 5 of the other debian
boxse with almost the exact same configuration. Has something changed
recently that would have caused this?

Thanks,

Josie

 > > Friendly, > > Sven Luther >
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
>
>

.Xdefaults seems broken

[J. Imlay]

I am running a fresh install with 4.2 (but it was doing this with 4.1) and
when I start an xterm it completly ignores my .Xdefaults file. What I am
doing works at home just fine. Does anyone know why this would be
happening?

When i put these two lines in the .Xdefaults It still starts with a black
bg and a white fg. And I have tried other things but they don't work.
xterm*background: White
xterm*foreground: Black

The fact that I have a black bg and a white fg is not my concern, I want
it that way, but I want a larger font, and xterm is ignoring my
xterm*Font: -misc-fixed-medium-r-normal--15-140-75-75-c-90-iso10646-1
line as well.

If I am going about configuring xterm all wrong or you know of a better
why to do to this, please let me know.

Thanks,

Josie Imlay

Radeon VE -dualhead

[J. Imlay]

Hello,

I'm using a dell box with a radeon VE, it has 1 dvi out that goes into a
y with 2 vga outs connected to two monitors, I have setup my Xconfig to do
the dualhead and I have xinerama working, but only the main monitor is
ever on. The other monitor never turns on, but the desktop is definitly
extended onto it. xwininfo -root says the desktop is 3200x1200 and the
/var/log/XFree86.log has the output and proper mode liens for both
monitors and it detects everything about them both right. Showing the
stat's for the first monitor under the RADEON(0) lines and the second
under RADEON(1) lines.

What I have figured out so far from reading posts on xpert and google
lists, is that I think I might need to turn on the second DAC, but I have
no clue how to do this, what I got from xpert wasn't exactly
comprehensible to me.

And I found some mentioning of a patch in CVS for this but it didn't look
like a good patch because some one replied saying it wasn't necesary (I
think)

So does anyone have any advice or ideas? Would doing a make world on X CVS
possibly fix this?

Thanks in advance,

Josie Imlay -- (I'm not on this list anymore, so please keep me in the
cc:)

Radeon 8500 issues w/ 4.2-prev1

[J. Imlay]

I have tried several different setups with this, the 2D acceleration
driver that comes stock works except that xvideo puts a black layer on top
of the picture. (If I move the window fast, the movie will start to slide
out from under the black window on top of it.) I can fix this by first
playing something with xvidix (which requires root) and then after that
xvideo will work a couple of times. I think this is the X ati driver and
not the debs, but just stating that it doesn't all work for me here.

Then I downloaded the fglr200 drivers from ati and everything works
(including quake @ 1600x1200 nicely) except video at all. The only output
mode that works is X11. I realize this probably has nothing to do with
the X 4.2debs because the driver I am actually using is from ati. (other
problem is that I can't get it to go at 16bit color, only 24) Any
sugestions?

(The other was AccelX and bleh!)

Thanks,

Josie Imlay





-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Radeon 8500 issues w/ 4.2-prev1

[J. Imlay]

I have tried several different setups with this, the 2D acceleration
driver that comes stock works except that xvideo puts a black layer on top
of the picture. (If I move the window fast, the movie will start to slide
out from under the black window on top of it.) I can fix this by first
playing something with xvidix (which requires root) and then after that
xvideo will work a couple of times. I think this is the X ati driver and
not the debs, but just stating that it doesn't all work for me here.

Then I downloaded the fglr200 drivers from ati and everything works
(including quake @ 1600x1200 nicely) except video at all. The only output
mode that works is X11. I realize this probably has nothing to do with
the X 4.2debs because the driver I am actually using is from ati. (other
problem is that I can't get it to go at 16bit color, only 24) Any
sugestions?

(The other was AccelX and bleh!)

Thanks,

Josie Imlay





-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

unofficial 4.2 debs

[J. Imlay]

I've been using 4.2 for my radeon 8500 for a while and.. (alas no 3d but
anyways) the unoffical debs I have been using work great except that the xterm 
copy and
paste functionality is not. You select things with the mouse it never ends
up on the copy buffer and you middle click it doesn't paste. I don't know
if it's just my comp (it worked before I upgraded) or what. So I'm just
letting you know that if you do what ever was done to make these debs (I
am assuming it's a pretty standard compile of of X) you might have some
copy and paste issues with xterm.

Just something to look out for.

Hasta,

Josie Imlay




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

unofficial 4.2 debs

[J. Imlay]

I've been using 4.2 for my radeon 8500 for a while and.. (alas no 3d but
anyways) the unoffical debs I have been using work great except that the xterm copy and
paste functionality is not. You select things with the mouse it never ends
up on the copy buffer and you middle click it doesn't paste. I don't know
if it's just my comp (it worked before I upgraded) or what. So I'm just
letting you know that if you do what ever was done to make these debs (I
am assuming it's a pretty standard compile of of X) you might have some
copy and paste issues with xterm.

Just something to look out for.

Hasta,

Josie Imlay




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]