On Thursday 17 February 2005 22:16, Frans Pop wrote:
> On Thursday 17 February 2005 00:24, Antonino A. Daplas wrote:
> > > Try this patch and let me know.
> > >
> > > video=atyfb:comp_sync:,vert_sync:,hor_sync:
> > >
> > > n = 0 (low), 1 (high)
On Thursday 17 February 2005 07:02, Antonino A. Daplas wrote:
> On Thursday 17 February 2005 06:10, Frans Pop wrote:
> > On Wednesday 16 February 2005 16:51, David S. Miller wrote:
> > > On Wed, 16 Feb 2005 19:27:57 +0800 Antonino A. Daplas wrote:
> > > > Nope, t
On Thursday 17 February 2005 07:02, Antonino A. Daplas wrote:
> On Thursday 17 February 2005 06:10, Frans Pop wrote:
> > On Wednesday 16 February 2005 16:51, David S. Miller wrote:
> > > On Wed, 16 Feb 2005 19:27:57 +0800 Antonino A. Daplas wrote:
> > > > Nope, t
On Thursday 17 February 2005 06:10, Frans Pop wrote:
> On Wednesday 16 February 2005 16:51, David S. Miller wrote:
> > On Wed, 16 Feb 2005 19:27:57 +0800 Antonino A. Daplas wrote:
> > > Nope, those are proposed options. If nobody disagrees, I can easily
> > > add this f
On Wednesday 16 February 2005 11:20, David S. Miller wrote:
> On Wed, 16 Feb 2005 03:27:51 +0100
>
> Frans Pop <[EMAIL PROTECTED]> wrote:
> > Excellent!
> > Tested the patch with 2.6.11-rc3-bk2 and AFAICT it completely restores
> > the old behavior. I guess that solves the regression since 2.6.10-r
On Wednesday 16 February 2005 10:27, Frans Pop wrote:
> 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
> > aty
On Tuesday 15 February 2005 14:22, Frans Pop wrote:
> Hi Tony,
>
> I've tried your suggestions and the one about using fbset resulted in a
> breakthrough. 'fbset -depth' gave no results, but comparing the output of
> 'fbset -i' from a working kernel and a new one gave me something to try.
>
Okay.
On Tuesday 15 February 2005 01:55, Frans Pop wrote:
> Hello Tony,
>
> Thanks for your reaction.
>
> On Monday 14 February 2005 17:59, Antonino A. Daplas wrote:
> > The above timings are screwed. This is 1024x768 at 85Hz INTERLACED.
> > The fb_find_mode() function p
On Monday 14 February 2005 23:34, Frans Pop wrote:
> On Monday 14 February 2005 12:32, Ben Collins wrote:
> atyfb: Set Visible Mode to 1024x768-8
> atyfb: Virtual resolution 1024x2016, pixclock_in_ps 22349 (calculated
> 22349) atyfb: Dot clock: 44 MHz
> atyfb: Horizontal sync: 35
