From: Frans Pop <aragorn@tiscali.nl>
To: 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: Wed, 16 Feb 2005 03:27:38 +0100 [thread overview]
Message-ID: <200502160327.47586.aragorn@tiscali.nl> (raw)
In-Reply-To: <200502152010.22880.adaplas@hotpop.com>
[-- Attachment #1: Type: text/plain, Size: 997 bytes --]
On Tuesday 15 February 2005 13:10, Antonino A. Daplas wrote:
> 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().
Tested that and output is identical for both. That condition you cite is
true for both kernels and the resolutions are retrieved from prom:
atyfb (fjp): crtc.vxres 1152
atyfb (fjp): crtc.vyres 900
> As a workaround, a boot option can be added for csync, hsync and vsync.
Hmm. I looked for the syntax for that, but can't find it.
I tried
video=atyfb:1024x768@70,csync:1
and
video=atyfb:1024x768@70,csync:high
but both failed miserably.
(I have checked that csync is sufficient to activate the monitor.)
What I get is boot messages 'vclk out of range' and 'not enough video RAM'
and I end up with 640x480-60 with both hsync and _v_sync set high, but
not csync (and a monitor in suspend of course).
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-02-16 2:27 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 [this message]
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=200502160327.47586.aragorn@tiscali.nl \
--to=aragorn@tiscali.nl \
--cc=adaplas@pol.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).