From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: Frans Pop <aragorn@tiscali.nl>, adaplas@pol.net
Cc: "David S. Miller" <davem@davemloft.net>,
debian-sparc@lists.debian.org, sparclinux@vger.kernel.org,
linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Re: [atyfb] No display on Sparc Ultra 10 with kernel 2.6.10-rc2 or later
Date: Fri, 18 Feb 2005 05:30:39 +0800 [thread overview]
Message-ID: <200502180530.41332.adaplas@hotpop.com> (raw)
In-Reply-To: <200502171516.14390.aragorn@tiscali.nl>
On Thursday 17 February 2005 22:16, Frans Pop wrote:
> On Thursday 17 February 2005 00:24, Antonino A. Daplas wrote:
> > > Try this patch and let me know.
> > >
> > > video=atyfb:comp_sync:<n>,vert_sync:<n>,hor_sync:<n>
> > >
> > > n = 0 (low), 1 (high)
>
> I've tested with the following combinations:
> - append="video=atyfb:comp_sync:1,1024x768@70"
> Works perfectly: csync is high and good display.
> - append="video=atyfb:comp_sync:1,hor_sync:1,vert_sync:0,1024x768@70"
> csync is high, but for some reason not hsync; display is good.
Okay, it seems that overriding the vsync and hsync settings is useless in
atyfb as it has its own algo to do that:
if(vdisplay < 400) {
h_sync_pol = 1;
v_sync_pol = 0;
} else if(vdisplay < 480) {
h_sync_pol = 0;
v_sync_pol = 1;
} else if(vdisplay < 768) {
h_sync_pol = 0;
v_sync_pol = 0;
} else {
h_sync_pol = 1;
v_sync_pol = 1;
}
I'll trim the patch for csync only.
> - append="video=atyfb:1024x768@70,comp_sync:1"
> Same results as first test.
>
> The sync settings were checked with 'fbset -i'.
>
> > BTW, the mode string should always be the last parameter, ie;
> >
> > video=atyfb:comp_sync:1,1024x768@70
>
> Hmmm. Wonder why you say that (considering the result of my last test).
My mistake then. Thanks for verifying.
>
> Should these new options also be documented in Documentation/fb/?
I'll add this and fix a few buglets when I push upstream.
Tony
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
prev parent reply other threads:[~2005-02-17 21:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200502140251.00645.aragorn@tiscali.nl>
[not found] ` <200502150059.12789.adaplas@hotpop.com>
[not found] ` <200502141855.29202.aragorn@tiscali.nl>
2005-02-14 23:40 ` [atyfb] No display on Sparc Ultra 10 with kernel 2.6.10-rc2 or later Antonino A. Daplas
2005-02-15 0:31 ` David S. Miller
2005-02-15 6:22 ` Frans Pop
2005-02-15 10:03 ` [Linux-fbdev-devel] " Geert Uytterhoeven
2005-02-15 12:10 ` Antonino A. Daplas
2005-02-15 16:49 ` David S. Miller
2005-02-16 2:27 ` Frans Pop
2005-02-16 3:20 ` David S. Miller
2005-02-16 11:30 ` Antonino A. Daplas
2005-02-16 2:27 ` Frans Pop
2005-02-16 11:27 ` Antonino A. Daplas
2005-02-16 15:51 ` David S. Miller
2005-02-16 22:10 ` Frans Pop
2005-02-16 23:02 ` Antonino A. Daplas
2005-02-16 23:18 ` [Linux-fbdev-devel] " Antonino A. Daplas
2005-02-16 23:24 ` Antonino A. Daplas
2005-02-17 14:16 ` Frans Pop
2005-02-17 21:30 ` Antonino A. Daplas [this message]
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=200502180530.41332.adaplas@hotpop.com \
--to=adaplas@hotpop.com \
--cc=adaplas@pol.net \
--cc=aragorn@tiscali.nl \
--cc=davem@davemloft.net \
--cc=debian-sparc@lists.debian.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=sparclinux@vger.kernel.org \
/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).