Re: [Chromium-dev] Self-documenting SPUs, configuration rework

[Keith W. <ke...@tu...>]

Brian Paul wrote:
> 
> Keith Whitwell wrote:
> >
> > I've attached a first cut at the sort of thing a self-documenting SPU might
> > look like.
> >
> > This is just handwaving at the moment, but there's not a lot to do to get it
> > working.
> >
> > There are two aspects to this code:  First, the spu can be queried for a list
> > of options it supports, which can then be fed to the config scripts to build
> > pretty dialog boxes.
> 
> I think you should go ahead and add the SPUOptions data structures to
> the SPUs and hook it into the SPU class (struct _SPUSTRUCT).  Then as
> I mentioned before, write a command-line utility program to report all
> the options for a named spu.  The utility would use crSPULoad() to do
> its thing.
> 
> Also, the utility should be able to return a list of all known SPUs.
> That might be done by scanning cr/lib/$(ARCH)/ for lib*spu.so and
> stripping off the 'lib' and 'spu.so' parts.

I'd prefer to take the names from argc/argv -- python can do the search easier
& faster.

The trouble with calling crSPULoad is that most SPU's seem to want to contact
the mothership from within there somewhere -- perhaps from
'the_spu->self(...)' at line 97.

Anyway I've imported a cutdown version of this into my utility, and that seems
to do fine.  I should have something to commit in half an hour or so.

Keith