From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: linux-fbdev-devel@lists.sourceforge.net,
Andrew Walrond <andrew@walrond.org>
Subject: Re: Rivafb won't work with DVI connector
Date: Tue, 23 Nov 2004 06:13:02 +0800 [thread overview]
Message-ID: <200411230613.02227.adaplas@hotpop.com> (raw)
In-Reply-To: <200411220943.57077.andrew@walrond.org>
[-- Attachment #1: Type: text/plain, Size: 1571 bytes --]
On Monday 22 November 2004 17:43, Andrew Walrond wrote:
> On Monday 22 Nov 2004 09:23, Andrew Walrond wrote:
> > I'll try to boot on dvi without and module parameters and report back
> > shortly.
>
> Ok, some progress. Booting without any module parameters on dvi connector
> gets me what is probably a 1024x768 display on my 1600x1200 tft screen.
> However, the console text is shifted right a bit less than half a screen
> width such that the right hand of the display appears wrapped on the left.
> There also seem to be two cursors, seperated by about two character widths.
> (Note these are not artifacts of the screen, which handles 1024x768 just
> fine under normal circumstances, either with a large border, or scaled to
> fit the whole screen)
>
> Dmesg:
>
> nvidiafb: nVidia device/chipset 10DE0250
> nvidiafb: nVidia Corporation NV25 [GeForce4 Ti 4600]
> ...can't find one
> ...can't find one
> nvidiafb: CRTC 1 is currently programmed for DFP
> nvidiafb: Using DFP on CRTC 1
> Panel size is 1024 x 768
> nvidiafb: MTRR set to ON
> Console: switching to colour frame buffer device 80x30
> nvidiafb: PCI nVidia NV25 framebuffer (128MB @ 0xE0000000)
>
> But hell, at least I am seeing some stuff through the dvi !
That sounds like progress :-)
Try this patch (reverse the previous one first)
- update code against the latest CVS version of Xorg
- added VESA blanking support
- added backlight support for powermacs
- added hardware cursor support using option 'hwcur'.
- clean-up of i2c code
Let me know, again, of the results. Thanks.
Tony
[-- Attachment #2: nvidiafb2.diff.gz --]
[-- Type: application/x-gzip, Size: 32894 bytes --]
next prev parent reply other threads:[~2004-11-22 22:13 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-19 11:37 Rivafb won't work with DVI connector Andrew Walrond
2004-11-19 22:08 ` Antonino A. Daplas
2004-11-20 15:52 ` Andrew Walrond
2004-11-22 0:11 ` Antonino A. Daplas
2004-11-22 9:23 ` Andrew Walrond
2004-11-22 9:43 ` Andrew Walrond
2004-11-22 22:13 ` Antonino A. Daplas [this message]
2004-11-22 23:47 ` Andrew Walrond
2004-11-22 23:54 ` Andrew Walrond
2004-11-23 1:50 ` Antonino A. Daplas
2004-11-23 12:32 ` Andrew Walrond
2004-11-23 14:28 ` Antonino A. Daplas
2004-11-23 15:09 ` Andrew Walrond
2004-11-23 15:18 ` Antonino A. Daplas
2004-11-23 16:08 ` Andrew Walrond
2004-11-23 17:07 ` Antonino A. Daplas
2004-11-23 18:01 ` Andrew Walrond
2004-11-23 18:26 ` Antonino A. Daplas
2004-11-23 19:00 ` Andrew Walrond
2004-11-23 19:07 ` Andrew Walrond
2004-11-23 19:23 ` Andrew Walrond
2004-11-23 19:59 ` Geert Uytterhoeven
2004-11-23 20:53 ` Andrew Walrond
2004-11-23 22:44 ` Antonino A. Daplas
2004-11-23 23:59 ` Andrew Walrond
2004-11-24 22:38 ` Andrew Walrond
2004-11-23 20:21 ` Chad Daelhousen
2004-11-24 23:01 ` Andrew Walrond
-- strict thread matches above, loose matches on Subject: below --
2004-11-25 0:07 Antonino A. Daplas
2004-11-25 15:27 ` Andrew Walrond
2004-11-25 21:16 ` Antonino A. Daplas
2004-11-26 14:09 ` Antonino A. Daplas
2004-11-27 12:40 ` Andrew Walrond
2004-11-27 18:29 ` Michel Dänzer
2004-11-27 22:35 ` Andrew Walrond
2004-11-27 22:43 ` 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=200411230613.02227.adaplas@hotpop.com \
--to=adaplas@hotpop.com \
--cc=andrew@walrond.org \
--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).