linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Arendsen Hein <thomas@intevation.de>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: cyblafb in kernel 2.6.16: corrupted display   in Xfree86
Date: Thu, 23 Mar 2006 17:03:22 +0100	[thread overview]
Message-ID: <20060323160321.GB7464@intevation.de> (raw)
In-Reply-To: <4422B753.5080704@t-online.de>

* Knut Petersen <Knut_Petersen@t-online.de> [20060323 16:07]:
> Thomas Arendsen Hein schrieb:
> >>That is very slow. Use geometry 1152 864 2048 4096 8
> >
> >This only works with kernel 2.6.16, not with 2.6.15.6
>
> ACK

Wow, scrolling in the console is definitely _much_ faster with this:

time for "find /dev" on kernel 2.6.16:

       1152/864  2048/4096
 8bpp    18s       0.56s
16bpp    39s       0.65s

> >>Are there any problems if you use the standard resolutions, eg 1024x768 
> >>or 1280x1024?
> >
> >No and yes:
> >Everything works fine when using
> >/sbin/modprobe cyblafb bpp=16 mode=1280x1024 ref=85
> >but I get the same problems if I do:
> >/sbin/modprobe cyblafb && /usr/sbin/fbset -a 1280x1024-85
> 
> Please Try:
> 
> /sbin/modprobe cyblafb && /usr/sbin/fbset -a 1280x1024-85 -depth 16

works

> /sbin/modprobe cyblafb && /usr/sbin/fbset -g 1152 864 1152 864 8 -t 10000 
> 168 40 57 13 152 11

doesn't work

> /sbin/modprobe cyblafb && /usr/sbin/fbset -g 1152 864 1152 864 16 -t 10000 
> 168 40 57 13 152 11

works

> /sbin/modprobe cyblafb && /usr/sbin/fbset -g 1152 864 2048 4096 8 -t 10000 
> 168 40 57 13 152 11

doesn't work

> /sbin/modprobe cyblafb && /usr/sbin/fbset -g 1152 864 2048 2048 16 -t 10000 
> 168 40 57 13 152 11

works

With /sbin/modprobe cyblafb && /usr/sbin/fbset -a 1152x864-70 -depth 16
(changing fb.modes would probably help, too) everything is back to
normal for me.

I think the extra colors on console won't hurt, now that I know
about the 2048/4096 setting.

> Is there a special reason not to use the X* trident driver?

Yes, I had crashes when using more than one X display (e.g. one
local xdm and one "X -query other :1"), and switching between X and
console is _much_ faster this way.

Many thanks for the help (and for cyblafb in general),
Thomas

-- 
Email: thomas@intevation.de
http://intevation.de/~thomas/


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

  reply	other threads:[~2006-03-23 16:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-22 23:48 cyblafb in kernel 2.6.16: corrupted display in Xfree86 Thomas Arendsen Hein
2006-03-23  8:34 ` Knut Petersen
2006-03-23 12:52   ` Thomas Arendsen Hein
2006-03-23 14:57     ` Knut Petersen
2006-03-23 16:03       ` Thomas Arendsen Hein [this message]
2006-03-23 16:57         ` Knut Petersen
2006-03-23 18:39           ` Thomas Arendsen Hein
2006-03-23 18:50             ` Thomas Arendsen Hein
2006-03-23 23:37               ` Antonino A. Daplas
2006-03-23 22:46             ` Knut Petersen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060323160321.GB7464@intevation.de \
    --to=thomas@intevation.de \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).