From: Alexander Kern <alex.kern@gmx.de>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: Luigi Gangitano <luigi@debian.org>,
"Antonino A. Daplas" <adaplas@hotpop.com>
Subject: Re: Re: [Fwd: AtyFB in 2.6.10, still not perfect]
Date: Wed, 23 Mar 2005 22:35:31 +0100 [thread overview]
Message-ID: <200503232235.31597.alex.kern@gmx.de> (raw)
In-Reply-To: <1111521961.6402.4.camel@willis>
[-- Attachment #1: Type: text/plain, Size: 851 bytes --]
Am Dienstag, 22. März 2005 21:06 schrieb Luigi Gangitano:
> Il giorno sab, 19-03-2005 alle 16:15 +0100, Alexander Kern ha scritto:
> > Copyed from oldest mail...
> >
> > > (as known) with 2.6.10. Latest 2.6.10 source in
> > > debian adds the fix that
> > > was integrated in 2.6.11, from
> > >
> > >
> > > http://lists.debian.org/debian-sparc/2005/02/msg00063.html
> >
> > It's mean you run 2.6.10 + "always hsync on SPARC" patch ?
>
> Right. Same behaviour with 2.6.11, however.
>
> > And if you try any fixes from Tony, you see mclk 100 xclk 100 in your
> > dmesg, bur screen is steel garbage?
>
> Yes. dmesg reports the setting passed on cmdline and screen is still
> garbled. Setting xclk to 100 makes things worse.
>
> Regards,
Ok, try this patch...
or in combination with setting mclk and xclk to 100
Regards
Alex
[-- Attachment #2: atyfb_xl_gr_try.diff --]
[-- Type: text/x-diff, Size: 770 bytes --]
--- atyfb_base.c.orig 2004-12-24 22:35:23.000000000 +0100
+++ atyfb_base.c 2005-03-23 22:32:58.553823808 +0100
@@ -403,7 +403,7 @@
{ PCI_CHIP_MACH64GM, "3D RAGE XL (Mach64 GM, AGP)", 230, 83, 63, ATI_CHIP_264XL },
{ PCI_CHIP_MACH64GN, "3D RAGE XL (Mach64 GN, AGP)", 230, 83, 63, ATI_CHIP_264XL },
{ PCI_CHIP_MACH64GO, "3D RAGE XL (Mach64 GO, PCI-66/BGA)", 230, 83, 63, ATI_CHIP_264XL },
- { PCI_CHIP_MACH64GR, "3D RAGE XL (Mach64 GR, PCI-33MHz)", 230, 83, 63, ATI_CHIP_264XL },
+ { PCI_CHIP_MACH64GR, "3D RAGE XL (Mach64 GR, PCI-33MHz)", 230, 83, 63, ATI_CHIP_264XL | M64F_SDRAM_MAGIC_PLL },
{ PCI_CHIP_MACH64GL, "3D RAGE XL (Mach64 GL, PCI)", 230, 83, 63, ATI_CHIP_264XL },
{ PCI_CHIP_MACH64GS, "3D RAGE XL (Mach64 GS, PCI)", 230, 83, 63, ATI_CHIP_264XL },
next prev parent reply other threads:[~2005-03-23 21:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-15 10:26 [Fwd: AtyFB in 2.6.10, still not perfect] Antonino A. Daplas
2005-03-15 19:40 ` Luigi Gangitano
2005-03-15 20:39 ` Antonino A. Daplas
2005-03-15 23:20 ` Luigi Gangitano
2005-03-15 23:49 ` Antonino A. Daplas
2005-03-19 15:15 ` Alexander Kern
2005-03-22 20:06 ` Luigi Gangitano
2005-03-23 21:35 ` Alexander Kern [this message]
2005-03-24 16:06 ` Luigi Gangitano
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=200503232235.31597.alex.kern@gmx.de \
--to=alex.kern@gmx.de \
--cc=adaplas@hotpop.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=luigi@debian.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).