RE: [Chromium-dev] spu seeing server... howto..

[Karl R. <rk...@vr...>]

> Yeah, it would be called at startup.  In fact, maybe the right thing to do
> is to add another argument to the "self" function, and call it just the
> "things that you might need to know about to do your job" function.

a 'here's some useful info' function sounds good, and comandeering the
"self" function sounds like the path of least resistance.

should it be passed some struct of useful info, in case at some point in
the future other things are deemed spu-worthy and need to be passed in?

> > BTW, what kind of information are you wanting access to, Karl?  There
> > might be another way to do what you want that fits with the existing
> > infrastructure.

i'd like to know the tiling information for a given server, as well as the
total 'mural' size, so that the readback spu can properly re-assemble
tiled displays, by figuring out where they should eventually lie, and
calling RasterPos(). tiling info would also be useful if you want to
readback multiple noncontinuous tiles, ie if you wanted to hack together
some sort of fault tolerent or load balancing system [there are half a
dozen other problems associated with this example, but...]

karl

  [k a r l  r a s c h e]    the math department makes me feel normal
                                                   -- campus grafiti
   rk...@vr...