Fwd: Re: Libata PATA status - CMD64X on sparc

2007-07-04 Thread Frans Pop
07 18:31 From: Frans Pop <...> To: Alan Cox <...> On Wednesday 04 July 2007 14:15, you wrote: > The main thing to know is simply "does it work". Generally speaking > you'll get either total failure or success. Initially I compiled the driver into the kernel and b

Re: [atyfb] No display on Sparc Ultra 10 with kernel 2.6.10-rc2 or later

2005-02-17 Thread Frans Pop
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) I've tested with the following combinations: - append="video=atyfb:comp_sync:1,[EMAIL PROTECTED]" Works perfectly: c

Re: [atyfb] No display on Sparc Ultra 10 with kernel 2.6.10-rc2 or later

2005-02-16 Thread Frans Pop
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 for atyfb. > > Please do. > > BTW, for Sparc we may wish to inherit the CSYNC setting from

Re: [atyfb] No display on Sparc Ultra 10 with kernel 2.6.10-rc2 or later

2005-02-15 Thread Frans Pop
this be fixed or should the conclusion be that resolutions other than [EMAIL PROTECTED] are just not supported? Cheers, Frans Pop pgpxyi2iuDtAZ.pgp Description: PGP signature

Re: [atyfb] No display on Sparc Ultra 10 with kernel 2.6.10-rc2 or later

2005-02-15 Thread Frans Pop
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 > atyfb_setup_sparc(). For the 2.6.8 kernel, this line is in > atyfb_init(). Tested that and output is identi

Re: [atyfb] No display on Sparc Ultra 10 with kernel 2.6.10-rc2 or later

2005-02-14 Thread Frans Pop
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. From 2.6.8 kernel (working framebuffer): mode "1152x900-66" # D

Re: [atyfb] No display on Sparc Ultra 10 with kernel 2.6.10-rc2 or later

2005-02-14 Thread Frans Pop
st to proceed? Can you help? Cheers, Frans Pop For comparison, here are the relevant lines from kern.log when booting with a Debian 2.6.8 kernel: atyfb: 3D RAGE (GT) [0x4754 rev 0x9a] 2M SGRAM, 14.31818 MHz XTAL, 200 MHz PLL, 67 Mhz MCLK fb0: ATY Mach64 frame buffer device on PCI Console:

Re: [atyfb] No display on Sparc Ultra 10 with kernel 2.6.10-rc2 or later

2005-02-14 Thread Frans Pop
On Monday 14 February 2005 12:32, Ben Collins wrote: > There's the problem right there. This is all wrong for sparc. Should be > something like 1024x768, and atleast 70Hz refresh. Hmm. Not sure if that's the whole problem. I tried booting with video=atyfb:[EMAIL PROTECTED] (which I know is OK for

[atyfb] No display on Sparc Ultra 10 with kernel 2.6.10-rc2 or later

2005-02-13 Thread Frans Pop
o debugging, provided you can give me some instructions). Kind regards, Frans Pop [1] I compiled 2.6.10-rc1 with added changeset 1.1938.212.5 to fix build error. lspci info: :01:02.0 VGA compatible controller: ATI Technologies Inc 3D Rage I/II 215GT [Mach64 GT] (rev 9a) Snip from kern.log a