linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: Frans Pop <aragorn@tiscali.nl>, adaplas@pol.net
Cc: debian-sparc@lists.debian.org, sparclinux@vger.kernel.org,
	Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: [atyfb] No display on Sparc Ultra 10 with kernel 2.6.10-rc2 or later
Date: Tue, 15 Feb 2005 20:10:21 +0800	[thread overview]
Message-ID: <200502152010.22880.adaplas@hotpop.com> (raw)
In-Reply-To: <200502150722.24770.aragorn@tiscali.nl>

On Tuesday 15 February 2005 14:22, Frans Pop wrote:
> Hi Tony,
>
> I've tried your suggestions and the one about using fbset resulted in a
> breakthrough. 'fbset -depth' gave no results, but comparing the output of
> 'fbset -i' from a working kernel and a new one gave me something to try.
>

Okay.  It seems that in the working kernel, the default mode, 1152x900, was
taken from the prom (since there is no 1152x900 in the mode database) if you
did not specify any boot mode option.

In the non-working version, without the boot mode option, the default_var
was used (which is only 640x480) or taken from the mode database if you
specified a boot mode.  Unfortunately, none of the entries in the mode
database nor the default var has the composite sync set to high, which
causes your display to go out of sync.  If I'm going to guess, the 2.6.10
version failed to get the default mode from the prom.

Can you verify if this is the case?  Insert a bunch of printk's in and around this
line "if (node == pcp->prom_node) {" in atyfb_setup_sparc().  For the 2.6.8
kernel, this line is in atyfb_init().

As a workaround, a boot option can be added for csync, hsync and vsync. 

Tony




  parent reply	other threads:[~2005-02-15 12:10 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 [this message]
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

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=200502152010.22880.adaplas@hotpop.com \
    --to=adaplas@hotpop.com \
    --cc=adaplas@pol.net \
    --cc=aragorn@tiscali.nl \
    --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).