Luc Verhaegen wrote:
On Sun, May 28, 2006 at 06:36:27PM +0200, Thomas Hellström wrote:
New semantics:
The new manager always aligns to 16 bytes, except when it is bypassed by
the SiS fb module.
This alarmed me; I don't want to see VIAs problem become a DRM wide
rule.
But it seems as if this alignment is enforced only through the device
specific code (xxx_mm.c), and that there really is nothing to worry
about.
Yes you're right. The core functions support any alignment so the
constraints are device specific.
Has me wondering though; Why does sis_mm.c enforce the same alignment?
Is this just a safe value? Why does this need to be overridden? Do some
engines on some sis hardware require wider alignment, while normal
alignment needs to be 16 bytes?
Although 16 bytes is a very common alignment requirement, also for some
SiS hardware, actually I just wanted to provide a smallest allocation
unit. However, in the SiS case, to make any use of it, the sisfb
allocator should enforce the same alignment.
/Thomas
Anyway, that's driver specific, not set in stone. Nice work,
Luc Verhaegen.
-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid7521&bid$8729&dat1642
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
