On Wed, Nov 02, 2005 at 02:12:07PM +0000, Daniel Laird wrote: > Sorry forgot to give the context: > We are using directfb on an embedded device and we have muliple layers etc > which can all have their resolution set. > However the device can also output to various connectors. > (SCART/CVBS/YPBPR/HDMI) > As this connections are connected to other display devices we need to be > able to say we are outputing [EMAIL PROTECTED] or [EMAIL PROTECTED] > Having looked at DirectFB these are sort off implied by PAL/NTSC/SECAM > currently but for HD/HDMI this is not true. > We need to be able to set encoder to output at a given resolution, scan > type and frequency. > > I think the easiest way to do this is to add a frequency enum. And extend > the Signals types with the resolution combinations for example
Doing this with enums makes it very inflexible. IMO the resolutions and scan frequencies should be specified via a struct of somekind. Maybe a full blown video timing structure like the (currently internal) VideoMode structure. Then it would be a matter of calling some method to enumerate the supported modes. I'm not sure what the best way to handle input vs. output resolutions. Do we need two sets of modes? I think we should leave the TV stanrdards to only indicate chroma encoding. That means they really only concern CVBS and Y/C signals. We'd just need to add a "few" of them to cover everything. PAL-B/G... PAL-N/NC Is there a difference between N and NC? Is it CN or NC? PAL-M PAL-60 Something else? NTSC-M Maybe NTSC-J? And 4.43 MHz variants? Something else? SECAM? What SECAM variantts are there? -- Ville Syrjälä [EMAIL PROTECTED] http://www.sci.fi/~syrjala/ _______________________________________________ directfb-dev mailing list directfb-dev@directfb.org http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
