All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luigi Gangitano <luigi@debian.org>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: "Antonino A. Daplas" <adaplas@hotpop.com>,
	Alexander Kern <alex.kern@gmx.de>
Subject: Re: Re: [Fwd: AtyFB in 2.6.10, still not perfect]
Date: Tue, 22 Mar 2005 21:06:00 +0100	[thread overview]
Message-ID: <1111521961.6402.4.camel@willis> (raw)
In-Reply-To: <200503191615.32610.alex.kern@gmx.de>

[-- Attachment #1: Type: text/plain, Size: 814 bytes --]

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,

-- 
 Luigi Gangitano -- <luigi@debian.org> -- <gangitano@lugroma3.org>
 GPG: 1024D/924C0C26: 12F8 9C03 89D3 DB4A 9972  C24A F19B A618 924C 0C26

[-- Attachment #2: Questa parte del messaggio è firmata --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-03-22 20:06 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 [this message]
2005-03-23 21:35           ` Alexander Kern
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=1111521961.6402.4.camel@willis \
    --to=luigi@debian.org \
    --cc=adaplas@hotpop.com \
    --cc=alex.kern@gmx.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.