From: "Ville Syrjälä" <syrjala@sci.fi>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: paulus@samba.org, linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [PATCH] Disable mach64 accelerator if stride is not multiple of 64
Date: Sun, 21 Jun 2009 00:25:24 +0300 [thread overview]
Message-ID: <20090620212524.GC9980@sci.fi> (raw)
In-Reply-To: <Pine.LNX.4.64.0906171657010.23412@hs20-bc2-1.build.redhat.com>
On Wed, Jun 17, 2009 at 05:05:31PM -0400, Mikulas Patocka wrote:
> On Wed, 17 Jun 2009, Ville Syrjälä wrote:
>
> > I was under the impression that 64 byte aligned offset and pitch are only
> > required if block writes are used. But perhaps it is always required
> > with SGRAM/WRAM, or perhaps you have auto block writes enabled. Can you
> > check the memory type and the the value of the HW_DEBUG register?
>
> Memory is SGRAM M32L1632512A-8Q. See this:
> http://www.digchip.com/datasheets/parts/datasheet/581/M32L1632512A.php
>
> The status line is:
> atyfb: 3D RAGE PRO (Mach64 GP, PQFP, PCI) [0x4750 rev 0x7c]
> atyfb: 4M SGRAM (1:1), 14.31818 MHz XTAL, 230 MHz PLL, 100 Mhz MCLK, 100
> MHz XCLK
>
> The debug register is zero (printed with printk("ATI INIT ENGINE, DEBUG
> %08X", aty_ld_le32(HW_DEBUG, par)); at the end of aty_init_engine).
OK then it has auto block writes enabled.
> > > This patch disables accelerator if scanline is not multiple of 64 bytes.
> >
> > A better option would be to round the pitch up in check_var(). Also it
> > would be more proper to use fix.line_length as the pitch value instead
> > of var.xres_virtual. That way check_var() could leave var.xres_virtual
> > alone and just round fix.line_length to whatever is required.
> >
> > Actually now that I think about it I would prefer to round to 64 bytes
> > always when SGRAM/WRAM is found. The reason is that the mach64 DirectFB
> > driver always enables auto block writes on SGRAM boards and if atyfb
> > uses less alignment things will not work correctly. Perhaps atyfb should
> > enable auto block writes too.
>
> So patch it to align line length (I don't know fb well to pick the right
> place) and send me the patch and I'll test it.
I cooked up a patch and briefly tested it on my Dell Inspiron 7000
which has an LT Pro /w SGRAM. I will send it as part of a series now.
--
Ville Syrjälä
syrjala@sci.fi
http://www.sci.fi/~syrjala/
------------------------------------------------------------------------------
Are you an open source citizen? Join us for the Open Source Bridge conference!
Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250.
Need another reason to go? 24-hour hacker lounge. Register today!
http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org
next prev parent reply other threads:[~2009-06-20 21:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 10:00 [PATCH] Fix colors in mach64 accelerator Mikulas Patocka
2009-06-17 10:02 ` [PATCH] Disable mach64 accelerator if stride is not multiple of 64 Mikulas Patocka
2009-06-17 17:21 ` Ville Syrjälä
2009-06-17 21:05 ` Mikulas Patocka
2009-06-20 21:25 ` Ville Syrjälä [this message]
2009-06-17 17:24 ` [PATCH] Fix colors in mach64 accelerator Ville Syrjälä
2009-06-17 21:40 ` Krzysztof Helt
-- strict thread matches above, loose matches on Subject: below --
2009-06-18 10:17 [PATCH] Disable mach64 accelerator if stride is not multiple of 64 krzysztof.h1
2009-06-18 12:38 ` Mikulas Patocka
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=20090620212524.GC9980@sci.fi \
--to=syrjala@sci.fi \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=mpatocka@redhat.com \
--cc=paulus@samba.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 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.