Roland Scheidegger schrieb:
> Hi,
> 
> I'm planning to merge gallium-noblocks branch to master soon. This api
> change may affect your driver, statetracker, whatever. I _should_ have
> fixed up all in tree stuff using it, but that's not a guarantee it will
> still run correctly (nv50 driver was strange for instance), and
What's strange with nv50 ?
There's this one "if (!pt->nblocksx[level]) {" in nv50_transfer.c that
was an unnecessary leftover because I hadn't seen miptree_blanket forgot
the initialize these and pushed a bit too early, thankfully this is now
gone automatically.

I just need the y blocks everywhere instead of just y because things
like offset = stride * y is simply wrong if you have *actual*
multi-pixel blocks (pitch as in nblocksx * width).
I hope no one will try to transfer just parts of a block (makes not much
sense for DXT imo though).

Well, as far as I can see nv50 should still work correctly, thanks for
adapting it.
> certainly if you have out of tree things they will break.
> The changes themselves should be fairly simple, you can read more about
> them in the git log file.
> 
> Roland
> 
> ------------------------------------------------------------------------------
> Join us December 9, 2009 for the Red Hat Virtual Experience,
> a free event focused on virtualization and cloud computing. 
> Attend in-depth sessions from your desk. Your couch. Anywhere.
> http://p.sf.net/sfu/redhat-sfdev2dev
> _______________________________________________
> Mesa3d-dev mailing list
> Mesa3d-dev@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mesa3d-dev


------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing. 
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
Mesa3d-dev mailing list
Mesa3d-dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mesa3d-dev

Reply via email to