From: "Carlo E. Prelz" <fluido@fluido.as>
To: James Simmons <jsimmons@infradead.org>
Cc: Ben Collins <bcollins@debian.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Re: [FBDEV UPDATE] Newer patch.
Date: Fri, 31 Oct 2003 00:07:30 +0100 [thread overview]
Message-ID: <20031030230730.GA942@casa.fluido.as> (raw)
In-Reply-To: <Pine.LNX.4.44.0310301833140.4560-100000@phoenix.infradead.org>
Subject: [Linux-fbdev-devel] Re: [FBDEV UPDATE] Newer patch.
Date: gio, ott 30, 2003 at 06:38:46 +0000
Quoting James Simmons (jsimmons@infradead.org):
> I have fixed the problems you have reported. I have a newer patch. Note
> this is updated with the LCD support. I like to see if the patch works on
> sparc. I has updates from the latest 2.4.X kernels. Please give it a try.
>
> http://phoenix.infradead.org/~jsimmons/fbdev.diff.gz
>
> Let me know the results.
Thanks for integrating Ben's radeon stuff. But I have bad news.
I got a fresh 2.6.0test9 and patched it with your patch. First,
radeonfb_setup was missing from radeon_base.c, while it was declared
in fbmem.c. I applied the patch that was contributed to the list by
Javier Villavicencio a few days ago. Thus, I had a good compile. I
have video=radeonfb:1280x1024-32@75 set in my lilo.conf file.
At reboot, my LCD screen complained about bad frequencies: 50.9 kHz
horizontal, and 43.7 Hz vertical. Normal frequencies with the above
settings are 80kHz and 75Hz. Passing 1280x1024-32@60 instead of
1280x1024-32@75 did not change the generated frequencies, so it seems
that interpretation of the mode line is not OK.
I plugged in an old CRT monitor, and I could see a normal screen. But
when starting X (set up with Option "UseFBDev" "true"), the LCD
monitor became happy of the frequency that it received but was frozen
with a garbled screen. And the keyboard was dead. I logged in remotely
and found out that the X executable was hanging and could not be
killed. Reboot was needed.
I can run at 1280x1024-32@75 with 2.6.0test7 with the original patches
from Ben (actually, using the whole kernel tree that he suggested I
should use, gotten via rsync). And X works OK in FB mode with his
kernel. With proper OpenGL acceleration.
All this with a radeon 9200 card. More info upon request...
Carlo
--
* Se la Strada e la sua Virtu' non fossero state messe da parte,
* K * Carlo E. Prelz - fluido@fluido.as che bisogno ci sarebbe
* di parlare tanto di amore e di rettitudine? (Chuang-Tzu)
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
next prev parent reply other threads:[~2003-10-30 23:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-22 17:31 [FBDEV UPDATE] Newer patch James Simmons
2003-10-22 20:38 ` Carlo E. Prelz
2003-10-22 21:46 ` [Linux-fbdev-devel] " James Simmons
2003-10-22 20:50 ` jhf
2003-10-22 21:46 ` James Simmons
2003-10-23 10:00 ` Geert Uytterhoeven
2003-10-23 14:43 ` Ben Collins
2003-10-23 22:50 ` James Simmons
2003-10-23 23:45 ` Ben Collins
2003-10-30 18:38 ` James Simmons
2003-10-30 23:07 ` Carlo E. Prelz [this message]
2003-11-17 18:38 ` Ben Collins
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=20031030230730.GA942@casa.fluido.as \
--to=fluido@fluido.as \
--cc=bcollins@debian.org \
--cc=benh@kernel.crashing.org \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@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).