These fields can be used to describe the kind of encoder you are using. You are correct in seeing that currently, DirectFB is not using these fields. So, it is primarily intended as a 'hint' or information towards the application.
You are also correct in noting that dfbinfo is acting unexpected. I think it makes sense to change if (descs[i].type == encoder_type[n].type) to if (descs[i].type & encoder_type[n].type) let me know if this works for you, so I can include it in the archive. Greets Niels Strelchun, Timothy wrote: > When running dfbinfo today on the DFB drivers that we are developing for the > Intel(R) Media Processor CE 3100, I noticed that of the encoders we are > supporting currently that only one of the them had a type string shown on the > encoder type line. > > I investigated and found that the printing routine didn't handle multiple > DSET_* flags being ORed together and stored in the > DFBScreenEncoderDescription::type field (we are ORing DSET_TV and > DSET_DIGITAL together currently for component output/connection and HDMI > output/connection to indicated that both SD, ED and HD is supported). I also > found now usage of DSET_DIGITAL in any existing drivers included in the core > packages. > > So, what is the intended usage of this type field? > > Thanks, > Timothy > > -- > > Timothy Strelchun > CE Software Engineering > Digital Home Group > Intel Corporation > > The views expressed above are my own and not those of Intel > _______________________________________________ > directfb-dev mailing list > directfb-dev@directfb.org > http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev > > -- .------------------------------------------. | DirectFB - Hardware accelerated graphics | | http://www.directfb.org/ | "------------------------------------------" _______________________________________________ directfb-dev mailing list directfb-dev@directfb.org http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
