frameworkd.conf needs more comments

[arne.anka]

here's what i just sent to the s-u mailinglist regarding the commenst in the example frameworkd.conf:

• # persistence format, one of "pickle", "yaml" -- what is persisted and what are the pros and cons for both?
• [odeviced.audio] disable = 1 -- what is odeviced.audio for and what difference does it make to dis- or enable it?
• [odeviced.input] disable = 1 -- not quite clear, why the default is disabled
• [odeviced.kernel26] -- what does it do?
• [odeviced.powercontrol_ibm] disable = 1; [odeviced.powercontrol_neo] disable = 1 -- what are those for and why are they (neo being for freerunner probably?) disabled?
• [ogsmd] -- why disabled by default? ti_calypso_dsp_mode -- what exactly do the options mean? i've looked for a while for description what these rather (to me) cryptic descriptions "short/long echo cancellation" and values for noise reduction actually mean (echo cancellation and noise reduction i do understand, but what with long/short and those db values?), neither google nor freesmartphone.org yielded anything. and how do i use, say, short-aec and nr:6db together?
• [ousaged] # choose whether resources should be disabled at startup, at shutdown, always (default), or never. sync_resources_with_lifecycle = always -- what does that mean? resources should be disabled always? but then, how would the be used?
• [opimd] -- i don't really understand what the different key/value pairs stand for
• fsousaged is, as said before, not mentioned at all

my research at fso.org usually leads to "look into the code" or something to that effect -- but i don't want to search code just to understand, what the different options are for, what is the sensible configuration and how to use new features (opimd frinst). and though i'm following all mails at smartphones-userland at least, i apparently can't keep up with the development (the somehow solved bleutooth issue frinst escaped me). like you wrote already, a lot of that information should be contained in a REAME included in the package and/or there should be some kind of wiki page -- if someone has the idea to implement something, he has to explain it anyway, why not right then write down and add configuration options and stuff later on?

[arne.anka]

that trac seems not really to understand simple line breaks ...

• # persistence format, one of "pickle", "yaml" -- what is persisted and what are the pros and cons for both?

• [odeviced.audio] disable = 1 -- what is odeviced.audio for and what difference does it make to dis- or enable it?

• [odeviced.input] disable = 1 -- not quite clear, why the default is disabled

• [odeviced.kernel26] -- what does it do?

• [odeviced.powercontrol_ibm] disable = 1; [odeviced.powercontrol_neo] disable = 1 -- what are those for and why are they (neo being for freerunner probably?) disabled?

• [ogsmd] -- why disabled by default? ti_calypso_dsp_mode -- what exactly do the options mean? i've looked for a while for description what these rather (to me) cryptic descriptions "short/long echo cancellation" and values for noise reduction actually mean (echo cancellation and noise reduction i do understand, but what with long/short and those db values?), neither google nor freesmartphone.org yielded anything. and how do i use, say, short-aec and nr:6db together?

• [ousaged] # choose whether resources should be disabled at startup, at shutdown, always (default), or never. sync_resources_with_lifecycle = always -- what does that mean? resources should be disabled always? but then, how would the be used?

• [opimd] -- i don't really understand what the different key/value pairs stand for

• fsousaged is, as said before, not mentioned at all

my research at fso.org usually leads to "look into the code" or something to that effect -- but i don't want to search code just to understand, what the different options are for, what is the sensible configuration and how to use new features (opimd frinst). and though i'm following all mails at smartphones-userland at least, i apparently can't keep up with the development (the somehow solved bleutooth issue frinst escaped me).

like you wrote already, a lot of that information should be contained in a REAME included in the package and/or there should be some kind of wiki page -- if someone has the idea to implement something, he has to explain it anyway, why not right then write down and add configuration options and stuff later on?

[sim]

 decoration Changed 1 year ago by admin

 bathtub Changed 1 year ago by admin

 solar system Changed 1 year ago by admin

 stair parts Changed 1 year ago by admin

 solar supply Changed 1 year ago by admin