約 5,663,451 件
https://w.atwiki.jp/boare/pages/90.html
Release Note Release Date 5 Apr, 2009 Notes Cadencii requires ".NET Framework Runtime(version 2.0 or later)" and "Visual C++ Library DLLs". Installers of these rumtimes are available from the links below. .NET Framework Runtime Download .NET Framework 3.5 SP1 Visual C++ Library DLL Microsoft Visual C++ 2008 Redistributable Package (x86) Cadencii can be launched with the latest version of mono. This enable you to use Cadencii with many platforms supported by mono. (Note Several functions using VOCALOID2 VSTi are not available in this case.) Mono is available from the link mono download Download Cadencii version 1.4.0 (416KB) CadenciiSDK version 1.3 (387KB) How to get source codes Source code repositories are now separated to 2 parts. Repository for the components listed below are on SVN LipSync repository of SourceForge.JP. Boare.Lib.AppUtil Boare.Lib.Media Boare.Lib.Vsq bocoree Also, Repository for the list below are on SVN Cadencii repository of SourceForege.JP. Cadencii vstidrv3 GenerateKeySound Please follow the instruction below for checking out the SourceForge.JP's CVS repository. If you're required to enter the password, just hit enter key. cvs -d pserver anonymous@cvs.sourceforge.jp /cvsroot/lipsync login cvs -z3 -d pserver anonymous@cvs.sourceforge.jp /cvsroot/lipsync co -r CADENCII_1_4_0 Boare.Lib.AppUtil cvs -z3 -d pserver anonymous@cvs.sourceforge.jp /cvsroot/lipsync co -r CADENCII_1_4_0 [[Boare.Lib.Media]] cvs -z3 -d pserver anonymous@cvs.sourceforge.jp /cvsroot/lipsync co -r CADENCII_1_4_0 [[Boare.Lib.Vsq]] cvs -z3 -d pserver anonymous@cvs.sourceforge.jp /cvsroot/lipsync co -r CADENCII_1_4_0 bocoree Source codes on SourceForge.JP's SVN repository can be checked out as follows. svn checkout -r 61 http //svn.sourceforge.jp/svnroot/cadencii/branches/1.4 ./ These cvs / svn command is for checiking out "THIS" version of Cadencii. In order to get the latest source codes, please remove "-r" options from these commands.
https://w.atwiki.jp/usb_audio/pages/37.html
原文：Audio Device Document 1.0(PDF) USB Device Class Definition for Audio Devices Release 1.0 March 18, 1998 41 The bNrInPins field contains the number of Input Pins (p) of the Mixer Unit. This evidently equals the number of audio channel clusters that enter the Mixer Unit. The connectivity of the Input Pins is described via the baSourceID() array, containing p elements. The index i into the array is one-based and directly related to the Input Pin numbers. BaSourceID(i) contains the ID of the Unit or Terminal to which Input Pin i is connected. The cluster descriptors, describing the logical channels entering the Mixer Unit are not repeated here. It is up to the Host software to trace the connections ‘upstream’ to locate the cluster descriptors pertaining to the audio channel clusters. As mentioned before, every input channel can virtually be mixed into all of the output channels. If n is thetotal number of logical input channels, contained in all the audio channel clusters that are entering the Mixer Unit ここに式 and m is the number of logical output channels, then there are n x m mixing Controls in the Mixer Unit, some of which may not be programmable. cite(Note) Both n and m must be limited to 254. Because a Mixer Unit can redefine the spatial locations of the logical output channels, contained in its output cluster, there is a need for a Mixer output cluster descriptor. The bNrChannels, wChannelConfig and iChannelNames characterize the cluster that leaves the Mixer Unit over the single Output Pin (‘downstream’ connection). For a detailed description of the cluster descriptor, see Section 3.7.2.3, “Audio Channel Cluster Format.” The Mixer Unit Descriptor reports which Controls are programmable in the bmControls bitmap field. This bitmap must be interpreted as a two-dimensional bit array that has a row for each logical input channel and a column for each logical output channel. If a bit at position [u, v] is set, this means that the Mixer Unit contains a programmable mixing Control that connects input channel u to output channel v. If bit [u, v] is clear, this indicates that the connection between input channel u and output channel v is non-programmable. Its fixed value can be retrieved through the appropriate request. The valid range for u is from one to n. The valid range for v is from one to m. The bmControls field stores the bit array row after row where the MSb of the first byte corresponds to the connection between input channel 1 and output channel 1. If (n x m) is not an integer multiple of 8, the bit array is padded with zeros until an integer number of bytes is occupied. The number of bytes used to store the bit array, N, can be calculated as follows IF ((n x m) MOD 8) 0 THEN N = ((n x m) DIV 8) + 1 ELSE N = ((n x m) DIV 8) An index to a string descriptor is provided to further describe the Mixer Unit. The following table details the structure of the Mixer Unit descriptor. Table 4-5 Mixer Unit Descriptor Offset Field Size Value Description 0 bLength 1 Number Size of this descriptor, in bytes 10+p+N 1 bDescriptorType 1 Constant CS_INTERFACE descriptor type. 2 bDescriptorSubtype 1 Constant MIXER_UNIT descriptor subtype. USB Device Class Definition for Audio Devices Release 1.0 March 18, 1998 42 Offset Field Size Value Description 3 bUnitID 1 Number Constant uniquely identifying the Unit within the audio function. This value is used in all requests to address this Unit. 4 bNrInPins 1 Number Number of Input Pins of this Unit p 5 baSourceID(1) 1 Number ID of the Unit or Terminal to which the first Input Pin of this Mixer Unit is connected. … … … … … 5+(p-1) baSourceID (p) 1 Number ID of the Unit or Terminal to which the last Input Pin of this Mixer Unit is connected. 5+p bNrChannels 1 Number Number of logical output channels in the Mixer’s output audio channel cluster. 6+p wChannelConfig 2 Bitmap Describes the spatial location of the logical channels. 8+p iChannelNames 1 Index Index of a string descriptor, describing the name of the first logical channel. 9+p bmControls N Number Bit map indicating which mixing Controls are programmable. 9+p+N iMixer 1 Index Index of a string descriptor, describing the Mixer Unit. 4.3.2.4 Selector Unit Descriptor The Selector Unit is uniquely identified by the value in the bUnitID field of the Selector Unit descriptor (SUD). No other Unit or Terminal within the same alternate setting of the AudioControl interface may have the same ID. This value must be passed in the UnitID field of each request that is directed to the Selector Unit. The bNrInPins field contains the number of Input Pins (p) of the Selector Unit. The connectivity of the Input Pins is described via the baSourceID() array that contains p elements. The index i into the array is one-based and directly related to the Input Pin numbers. BaSourceID(i) contains the ID of the Unit or Terminal to which Input Pin i is connected. The cluster descriptors, describing the logical channels that enter the Selector Unit are not repeated here. In order for a Selector Unit to be legally connected, all of the audio channel clusters that enter the Selector Unit must have the same number of channels. However, the spatial locations of these channels may vary from cluster to cluster. Therefore, the Host software should trace all Input Pins to find their ‘upstream’ connection to locate the cluster descriptors for all the Input Pins that enter the Selector Unit. This further implies that the cluster descriptor, associated with the Output Pin of the Selector Unit can change dynamically, depending on the currently selected position of the Selector Unit. An index to a string descriptor is provided to further describe the Selector Unit. The following table details the structure of the Selector Unit descriptor. USB Device Class Definition for Audio Devices Release 1.0 March 18, 1998 43 Table 4-6 Selector Unit Descriptor Offset Field Size Value Description 0 bLength 1 Number Size of this descriptor, in bytes 6+p 1 bDescriptorType 1 Constant CS_INTERFACE descriptor type. 2 bDescriptorSubtype 1 Constant SELECTOR_UNIT descriptor subtype. 3 bUnitID 1 Number Constant uniquely identifying the Unit within the audio function. This value is used in all requests to address this Unit. 4 bNrInPins 1 Number Number of Input Pins of this Unit p 5 baSourceID(1) 1 Number ID of the Unit or Terminal to which the first Input Pin of this Selector Unit is connected. … … … … … 5+(p-1) baSourceID (p) 1 Number ID of the Unit or Terminal to which the last Input Pin of this Selector Unit is connected. 5+p iSelector 1 Index Index of a string descriptor, describing the Selector Unit. 4.3.2.5 Feature Unit Descriptor The Feature Unit is uniquely identified by the value in the bUnitID field of the Feature Unit descriptor (FUD). No other Unit or Terminal within the same alternate setting of the AudioControl interface may have the same ID. This value must be passed in the UnitID field of each request that is directed to the Feature Unit. The bSourceID field is used to describe the connectivity for this Feature Unit. It contains the ID of the Unit or Terminal to which this Feature Unit is connected via its Input Pin. The cluster descriptor, describing the logical channels entering the Feature Unit is not repeated here. It is up to the Host software to trace the connection ‘upstream’ to locate the cluster descriptor pertaining to this audio channel cluster. The bmaControls() array is an array of bit-maps, each indicating the availability of certain audio Controls for a specific logical channel or for the master channel 0. For future expandability, the number of bytes occupied by each element (n) of the bmaControls() array is indicated in the bControlSize field. The number of logical channels in the cluster is denoted by ch. An index to a string descriptor is provided to further describe the Feature Unit. The layout of the Feature Unit descriptor is detailed in the following table. Table 4-7 Feature Unit Descriptor Offset Field Size Value Description 0 bLength 1 Number Size of this descriptor, in bytes 7+(ch+1)*n USB Device Class Definition for Audio Devices Release 1.0 March 18, 1998 44 Offset Field Size Value Description 1 bDescriptorType 1 Constant CS_INTERFACE descriptor type. 2 bDescriptorSubtype 1 Constant FEATURE_UNIT descriptor subtype. 3 bUnitID 1 Number Constant uniquely identifying the Unit within the audio function. This value is used in all requests to address this Unit. 4 bSourceID 1 Constant ID of the Unit or Terminal to which this Feature Unit is connected. 5 bControlSize 1 Number Size in bytes of an element of the bmaControls() array n 6 bmaControls(0) n Bitmap A bit set to 1 indicates that the mentioned Control is supported for master channel 0 D0 MuteD1 VolumeD2 BassD3 MidD4 TrebleD5 Graphic EqualizerD6 Automatic GainD7 DelayD8 Bass BoostD9 LoudnessD10..(n*8-1) Reserved 6+n bmaControls(1) n Bitmap A bit set to 1 indicates that the mentioned Control is supported for logical channel 1. … … … … … 6+(ch*n) bmaControls(ch) n Bitmap A bit set to 1 indicates that the mentioned Control is supported for logical channel ch. 6+(ch+1)*n iFeature 1 Index Index of a string descriptor, describing this Feature Unit. 4.3.2.6 Processing Unit Descriptor The Processing Unit is uniquely identified by the value in the bUnitID field of the Processing Unit descriptor (PUD). No other Unit or Terminal within the same alternate setting of the AudioControl interface may have the same ID. This value must be passed in the UnitID field of each request that is directed to the Processing Unit. The wProcessType field contains a value that fully identifies the Processing Unit. For a list of all supported Processing Unit Types, see Section A.7, “Processing Unit Process Types.” The bNrInPins field contains the number of Input Pins (p) of the Processing Unit. The connectivity of the Input Pins is described via the baSourceID() array that contains p elements. The index i into the array is one-based and directly related to the Input Pin numbers. BaSourceID(i) contains the ID of the Unit or USB Device Class Definition for Audio Devices Release 1.0 March 18, 1998 45 Terminal to which Input Pin i is connected. The cluster descriptors, describing the logical channels entering the Processing Unit are not repeated here. It is up to the Host software to trace the connections ‘upstream’ to locate the cluster descriptors pertaining to the audio channel clusters. Because a Processing Unit can freely redefine the spatial locations of the logical output channels, contained in its output cluster, there is a need for an output cluster descriptor. The bNrChannels, wChannelConfig, and iChannelNames fields characterize the cluster that leaves the Processing Unit over the single Output Pin (‘downstream’ connection). For a detailed description of the cluster descriptor, see Section 3.7.2.3, “Audio Channel Cluster Format.” The bmControls field is a bitmap, indicating the availability of certain audio Controls in the Processing Unit. For future expandability, the number of bytes occupied by the bmControls field is indicated in the bControlSize field. In general, all Controls are optional. However, some Processing Types may define certain Controls as mandatory. In such a case, the appropriate bit in the bmControls field must be set to one. The meaning of the bits in the bmControls field is qualified by the wProcessType field. However, bit D0 always represents the Enable Processing Control for all Processing Unit Types. The Enable Processing Control is used to bypass the entire functionality of the Processing Unit. Default behavior is assumed when set to off. In case of a single Input Pin, logical channels entering the Unit are passed unaltered for those channels that are also present in the output cluster. Logical channels not available in the output cluster are absorbed by the Processing Unit. Logical channels present in the output cluster but unavailable in the input cluster are muted. In case of multiple Input Pins, corresponding logical input channels are equally mixed together before being passed to the output. If the Enable Processing Control is present in a Processing Unit, bit D0 must be set to one. Otherwise, it is set to zero, indicating that the Processing Unit cannot be bypassed. An index to a string descriptor is provided to further describe the Processing Unit. The previous fields are common to all Processing Units. However, depending on the value in the wProcessType field, a process-specific part is added to the descriptor. The following paragraphs describe these process-specific parts. The following table outlines the common part of the Processing Unit descriptor. Table 4-8 Common Part of the Processing Unit Descriptor Offset Field Size Value Description 0 bLength 1 Number Size of this descriptor, in bytes 13+p+n+x 1 bDescriptorType 1 Constant CS_INTERFACE descriptor type. 2 bDescriptorSubtype 1 Constant PROCESSING_UNIT descriptor subtype. 3 bUnitID 1 Number Constant uniquely identifying the Unit within the audio function. This value is used in all requests to address this Unit. 4 wProcessType 2 Constant Constant identifying the type of processing this Unit is performing. 6 bNrInPins 1 Number Number of Input Pins of this Unit p 1 - 6 - 11 - 16 - 21 - 26 - 31 - 36 - 41 - 46 - 51 - 56 - 61 - 66 - 71 - 76 - 81 - 86 - 91 - 96 - 101 - 106 - 111 - 116 - 121 - 126 ここを編集
https://w.atwiki.jp/zegapain/pages/505.html
REUNION -ZEGAPAIN ARCHIVE PROJECT- 【種別】関連商品/受注生産 設定資料集 【著者】高島 雄哉 【予約期間】2024年8月30日（金）12時（正午）～2025年1⽉5⽇（日）23 59まで 【発売日】2025/02下旬 ￥12,100円(税込) 【発売元】バンダイナムコフィルムワークス REUNION -ZEGAPAIN ARCHIVE PROJECT- 『ZEGAPAIN PROJECT REUNION』の集大成となるドラマCD付き設定集「REUNION -ZEGAPAIN ARCHIVE PROJECT-」が登場！ 本書籍は、『ZEGAPAIN PROJECT REUNION』の集大成となる設定集で、A4サイズ・300ページ以上の冊子で構成。 冊子を収納する三方背BOXには、『ZEGAPAIN』シリーズより、メカニックデザイン・やまだ たかひろ氏による「ゼーガペイン アルティール」の新規描き下ろしイラストを使用。 「ゼーガペイン アルティール」は一部ホロの箔押しを使用した美麗なデザイン。 冊子の表紙・裏表紙には、『ZEGAPAIN』より、キャラクター作画監督・大貫健一氏による新規描き下ろしイラストを使用。表紙は「キョウ＆リョーコ」、裏表紙は「キョウ＆シズノ」。 冊子には、『ZEGAPAIN』、『ZEGAPAIN ADP』、『ZEGAPAIN STA』よりキャラクター・メカニックの設定画や、美術設定、過去の版権イラストなどを収録。各作品の解説ページや、OP・EDなどの絵コンテを一部掲載した読み応えのある構成。 さらに、「ソゴル・キョウ」役の浅沼晋太郎氏と、「カミナギ・リョーコ」役の花澤香菜氏、「ミサキ・シズノ」役の川澄綾子氏によるキャストインタビューと、監督・下田正美氏、シリーズ構成・関島眞頼氏、脚本・高山カツヒコ氏によるスタッフ鼎談が掲載。 また、監督・下田正美氏監修のもと、脚本・高山カツヒコ氏による、新規録り下ろしドラマCDも付属。 【A-on STORE 限定特典】 冊子表紙イラスト「キョウ＆リョーコ」のミニ色紙(横121㎜×縦136㎜) 【サンライズストア(プレミアムバンダイ内) 限定特典】 冊子裏表紙イラスト「キョウ＆シズノ」のミニ色紙(横121㎜×縦136㎜)。 【関連URL】 A-on STORE https //a-onstore.jp/item/item-1000232398/ サンライズストア(プレミアムバンダイ内) https //p-bandai.jp/item/item-1000216225/ コメント 名前 コメント
https://w.atwiki.jp/busphoto/pages/426.html
社番 ひ127 メーカー 三菱ふそう 車名 エアロスター 型式 QKG-MP35FM 車体 MFBM 年式 2012.6 ステップ ワンステップ 転入年月 - 改番年月 - 前所属 - 前社番 - 登録番号 湘南200 か 1656 登録変更年月 - バックカメラ ○ かなch. × ラッピング - 備考
https://w.atwiki.jp/mahabharatapotal/pages/1609.html
第12-126章．第12-127章．第12-128章． 第12-127章． ビーシュマは言った、『その時、リシたちの中で最も優れた者、すなわち再生したリシャバが、すべてのリシたちの中に座って、少し微笑み、次のように言った： 王の中の虎よ、以前、神聖な場所を旅していた時、主よ、私は奈良とナーラーヤナの美しい亡命地に到着しました。神聖なガンガーが湧き出る）大空の湖もあります。 王よ、賢者アスワシーラスはいつもそこで永遠のヴェーダを読んでいる。その湖で沐浴をし、祖先と犬たちに水を捧げ、私は隠居所に入った。その隠れ家の中では、奈良菩薩とナーラーヤナ菩薩がいつも真の喜びの中で時を過ごしている。 その場所からそう遠くないところに、私は住まいを構えるために別の隠れ家に向かった。そこに座っていると、ボロ布と皮を身にまとった、非常に背が高く痩せ衰えたリシが私の方に近づいてくるのが見えた。懺悔の富を持つ彼はタヌと名乗った。強靭な腕の持ち主よ、他の男と比べると、彼の身長は8倍もあるように見えた。王家の賢者よ、その無駄のなさについては、私はこのようなものを見たことがないと言える。王よ、彼の体は小指のように細かった。首も腕も脚も髪も、すべてが並外れていた。彼の頭は彼の体に比例し、彼の車と目もまた同じであった。その話し方、動作は非常に弱々しかった。その非常にやせ細ったブラフマナを見て、私は非常に元気がなくなり、怖くなった。彼の足に敬礼し、手を合わせて彼の前に立った。私の名前と家系を告げ、私の父の名も告げ、人の中の雄牛よ、私は彼に示された席にゆっくりと腰を下ろした。それから、君主よ、あの徳の最も高い者、すなわちタヌは、その庇護院に住むリシたちの中で、正義と利益に関する話題について説き始めた。その時、蓮の花びらのような目をした一人の王が、軍勢と侍女たちを引き連れて、大八車に乗ってその場所にやって来た。その王の名はヴィラドゥムナ。ハンサムな顔立ちで、偉大な名声を持っていた。息子の名はブリディユムナ。その子が行方不明になり、主君は非常に元気がなく、行方不明の子を追って森の中を放浪しているうちに、そこにやって来た。息子をここで見つけよう！」「息子をここで見つけよう！」。こうして希望に引きずられながら、王はそのころ、その森をさまよった。やせ衰えたリシに向かって彼は言った、「間違いなく、私のあの非常に徳の高い息子は、私が探し出すのは非常に困難です。残念なことに、彼は私の一人息子でした。彼は行方不明で、どこにもいません！見つけることはできないが、彼を見つけるという私の望みは非常に大きい。その望み（それは常に裏切られ続けている）に満たされて、私は本当に死に瀕しているのです」。王のこの言葉を聞いて 王のこの言葉を聞いて、ムニの最たる者、すなわち聖なるタヌは、しばらくの間、頭を垂れて観想の中に埋もれていた。瞑想に埋もれた彼を見て、王は非常に元気がなくなった。天空のリシよ、何が克服できないのか、何が希望よりも偉大なのか。聖なる者よ、もし不謹慎でなければ、私に教えてください』。 ムニは言った、『聖なる偉大なリシがあなたの息子に侮辱されました。彼は自分の愚かな理解力に動かされ、不運によってそれを行ったのです。リシはあなたの息子に金の壺と野菜の樹皮を求めた。汝の息子は侮蔑的に行者を喜ばせようとしなかった。あなたの息子にこのように扱われ、大賢者は失望した。こうして、王は、世界中から崇拝されているその行者を礼拝した。高潔な魂を持つヴィラドゥムナは、汝のように疲労困憊してそこに座っていた。偉大なリシは、そのお返しに、森の住人が守る儀式に従って、王の足を洗う水と、アルギャを構成する通常の材料を差し出した。それから、王の中の虎よ、すべてのリシがそこに座り、大熊座の星々が北極星を取り囲むように、人の中の雄牛を取り囲んだ。そして彼らは敗れざる王に、その亡命先に到着した原因を尋ねた」。 第12-126章．第12-127章．第12-128章．
https://w.atwiki.jp/feedback1970/pages/44.html
memo 処理の流れ 382 int main(int argc, const char * const argv[]) 383 { 384 char c; 385 int configtestonly = 0; 386 const char *confname = SERVER_CONFIG_FILE; 387 const char *def_server_root = HTTPD_ROOT; 388 const char *temp_error_log = NULL; 389 process_rec *process; 390 server_rec *server_conf; 391 apr_pool_t *pglobal; 392 apr_pool_t *pconf; 393 apr_pool_t *plog; /* Pool of log streams, reset _after_ each read of conf */ 394 apr_pool_t *ptemp; /* Pool for temporary config stuff, reset often */ 395 apr_pool_t *pcommands; /* Pool for -D, -C and -c switches */ 396 apr_getopt_t *opt; 397 apr_status_t rv; 398 module **mod; 399 const char *optarg; 400 APR_OPTIONAL_FN_TYPE(ap_signal_server) *signal_server; 401 402 AP_MONCONTROL(0); /* turn off profiling of startup */ 403 404 process = init_process( argc, argv); 405 pglobal = process- pool; 406 pconf = process- pconf; 407 ap_server_argv0 = process- short_name; 408 409 #if APR_CHARSET_EBCDIC 410 if (ap_init_ebcdic(pglobal) != APR_SUCCESS) { 411 destroy_and_exit_process(process, 1); 412 } 413 #endif 414 415 apr_pool_create( pcommands, pglobal); 416 apr_pool_tag(pcommands, "pcommands"); 417 ap_server_pre_read_config = apr_array_make(pcommands, 1, sizeof(char *)); 418 ap_server_post_read_config = apr_array_make(pcommands, 1, sizeof(char *)); 419 ap_server_config_defines = apr_array_make(pcommands, 1, sizeof(char *)); 420 421 ap_setup_prelinked_modules(process); 422 423 ap_run_rewrite_args(process); 424 425 /* Maintain AP_SERVER_BASEARGS list in http_main.h to allow the MPM 426 * to safely pass on our args from its rewrite_args() handler. 427 */ オプション処理 428 apr_getopt_init( opt, pcommands, process- argc, process- argv); 429 430 while ((rv = apr_getopt(opt, AP_SERVER_BASEARGS, c, optarg)) 431 == APR_SUCCESS) { 432 char **new; 433 434 switch (c) { 435 case c 436 new = (char **)apr_array_push(ap_server_post_read_config); 437 *new = apr_pstrdup(pcommands, optarg); 438 break; 439 440 case C 441 new = (char **)apr_array_push(ap_server_pre_read_config); 442 *new = apr_pstrdup(pcommands, optarg); 443 break; 444 445 case d 446 def_server_root = optarg; 447 break; 448 449 case D 450 new = (char **)apr_array_push(ap_server_config_defines); 451 *new = apr_pstrdup(pcommands, optarg); 452 break; 453 454 case e 455 if (strcasecmp(optarg, "emerg") == 0) { 456 ap_default_loglevel = APLOG_EMERG; 457 } 458 else if (strcasecmp(optarg, "alert") == 0) { 459 ap_default_loglevel = APLOG_ALERT; 460 } 461 else if (strcasecmp(optarg, "crit") == 0) { 462 ap_default_loglevel = APLOG_CRIT; 463 } 464 else if (strncasecmp(optarg, "err", 3) == 0) { 465 ap_default_loglevel = APLOG_ERR; 466 } 467 else if (strncasecmp(optarg, "warn", 4) == 0) { 468 ap_default_loglevel = APLOG_WARNING; 469 } 470 else if (strcasecmp(optarg, "notice") == 0) { 471 ap_default_loglevel = APLOG_NOTICE; 472 } 473 else if (strcasecmp(optarg, "info") == 0) { 474 ap_default_loglevel = APLOG_INFO; 475 } 476 else if (strcasecmp(optarg, "debug") == 0) { 477 ap_default_loglevel = APLOG_DEBUG; 478 } 479 else { 480 usage(process); 481 } 482 break; 483 484 case E 485 temp_error_log = apr_pstrdup(process- pool, optarg); 486 break; 487 488 case X 489 new = (char **)apr_array_push(ap_server_config_defines); 490 *new = "DEBUG"; 491 break; 492 493 case f 494 confname = optarg; 495 break; 496 497 case v 498 printf("Server version %s\n", ap_get_server_version()); 499 printf("Server built %s\n", ap_get_server_built()); 500 destroy_and_exit_process(process, 0); 501 502 case V 503 show_compile_settings(); 504 destroy_and_exit_process(process, 0); 505 506 case l 507 ap_show_modules(); 508 destroy_and_exit_process(process, 0); 509 510 case L 511 ap_show_directives(); 512 destroy_and_exit_process(process, 0); 513 514 case t 515 configtestonly = 1; 516 break; 517 518 case S 519 configtestonly = 1; 520 new = (char **)apr_array_push(ap_server_config_defines); 521 *new = "DUMP_VHOSTS"; 522 break; 523 524 case h 525 case ? 526 usage(process); 527 } 528 } 529 530 /* bad cmdline option? then we die */ 531 if (rv != APR_EOF || opt- ind opt- argc) { 532 usage(process); 533 } 535 apr_pool_create( plog, pglobal); 536 apr_pool_tag(plog, "plog"); 537 apr_pool_create( ptemp, pconf); 538 apr_pool_tag(ptemp, "ptemp"); 539 540 /* Note that we preflight the config file once 541 * before reading it _again_ in the main loop. 542 * This allows things, log files configuration 543 * for example, to settle down. 544 */ 545 546 ap_server_root = def_server_root; 547 if (temp_error_log) { 548 ap_replace_stderr_log(process- pool, temp_error_log); 549 } 550 server_conf = ap_read_config(process, ptemp, confname, ap_conftree); 551 if (ap_run_pre_config(pconf, plog, ptemp) != OK) { 552 ap_log_error(APLOG_MARK, APLOG_STARTUP |APLOG_ERR, 0, 553 NULL, "Pre-configuration failed"); 554 destroy_and_exit_process(process, 1); 555 } 556 557 ap_process_config_tree(server_conf, ap_conftree, process- pconf, ptemp); 558 ap_fixup_virtual_hosts(pconf, server_conf); 559 ap_fini_vhost_config(pconf, server_conf); 560 apr_hook_sort_all(); 561 if (configtestonly) { 562 ap_log_error(APLOG_MARK, APLOG_STARTUP, 0, NULL, "Syntax OK"); 563 destroy_and_exit_process(process, 0); 564 } 565 566 signal_server = APR_RETRIEVE_OPTIONAL_FN(ap_signal_server); 567 if (signal_server) { 568 int exit_status; 569 570 if (signal_server( exit_status, pconf) != 0) { 571 destroy_and_exit_process(process, exit_status); 572 } 573 } 574 575 apr_pool_clear(plog); 576 577 if ( ap_run_open_logs(pconf, plog, ptemp, server_conf) != OK) { 578 ap_log_error(APLOG_MARK, APLOG_STARTUP |APLOG_ERR, 579 0, NULL, "Unable to open logs"); 580 destroy_and_exit_process(process, 1); 581 } 582 583 if ( ap_run_post_config(pconf, plog, ptemp, server_conf) != OK) { 584 ap_log_error(APLOG_MARK, APLOG_STARTUP |APLOG_ERR, 0, 585 NULL, "Configuration Failed"); 586 destroy_and_exit_process(process, 1); 587 } 588 589 apr_pool_destroy(ptemp); 590 591 for (;;) { 592 apr_hook_deregister_all(); 593 apr_pool_clear(pconf); 594 595 for (mod = ap_prelinked_modules; *mod != NULL; mod++) { 596 ap_register_hooks(*mod, pconf); 597 } 598 599 /* This is a hack until we finish the code so that it only reads 600 * the config file once and just operates on the tree already in 601 * memory. rbb 602 */ 603 ap_conftree = NULL; 604 apr_pool_create( ptemp, pconf); 605 apr_pool_tag(ptemp, "ptemp"); 606 ap_server_root = def_server_root; 607 server_conf = ap_read_config(process, ptemp, confname, ap_conftree); 608 if (ap_run_pre_config(pconf, plog, ptemp) != OK) { 609 ap_log_error(APLOG_MARK, APLOG_STARTUP |APLOG_ERR, 610 0, NULL, "Pre-configuration failed"); 611 destroy_and_exit_process(process, 1); 612 } 613 614 ap_process_config_tree(server_conf, ap_conftree, process- pconf, ptemp); 615 ap_fixup_virtual_hosts(pconf, server_conf); 616 ap_fini_vhost_config(pconf, server_conf); 617 apr_hook_sort_all(); 618 apr_pool_clear(plog); 619 if (ap_run_open_logs(pconf, plog, ptemp, server_conf) != OK) { 620 ap_log_error(APLOG_MARK, APLOG_STARTUP |APLOG_ERR, 621 0, NULL, "Unable to open logs"); 622 destroy_and_exit_process(process, 1); 623 } 624 625 if (ap_run_post_config(pconf, plog, ptemp, server_conf) != OK) { 626 ap_log_error(APLOG_MARK, APLOG_STARTUP |APLOG_ERR, 627 0, NULL, "Configuration Failed"); 628 destroy_and_exit_process(process, 1); 629 } 630 631 apr_pool_destroy(ptemp); 632 apr_pool_lock(pconf, 1); 633 634 ap_run_optional_fn_retrieve(); 635 636 if (ap_mpm_run(pconf, plog, server_conf)) 637 break; 638 639 apr_pool_lock(pconf, 0); 640 } 641 642 apr_pool_lock(pconf, 0); 643 destroy_and_exit_process(process, 0); 644 645 return 0; /* Termination ok */ 646 } 647 648 /* force Expat to be linked into the server executable */ 649 #if defined(USE_EXPAT) !defined(SHARED_CORE_BOOTSTRAP) 650 #include "xmlparse.h" 651 const XML_LChar *suck_in_expat(void); 652 const XML_LChar *suck_in_expat(void) 653 { 654 return XML_ErrorString(XML_ERROR_NONE); 655 } 656 #endif /* USE_EXPAT */ 657 658 #ifndef SHARED_CORE_BOOTSTRAP 659 /* 660 * Force apr_password_validate() into the image so that modules like 661 * mod_auth can use it even if they re dynamically loaded. 662 */ 663 void suck_in_apr_password_validate(void); 664 void suck_in_apr_password_validate(void) 665 { 666 apr_password_validate("a", "b"); 667 } 668 #endif 669 670 #ifdef AP_USING_AUTOCONF 671 /* This ugly little hack pulls any function referenced in exports.c into 672 * the web server. exports.c is generated during the build, and it 673 * has all of the APR functions specified by the apr/apr.exports and 674 * apr-util/aprutil.exports files. 675 */ 676 const void *suck_in_APR(void); 677 const void *suck_in_APR(void) 678 { 679 extern const void *ap_ugly_hack; 680 681 return ap_ugly_hack; 682 } 683 #endif source 1 /* Licensed to the Apache Software Foundation (ASF) under one or more 2 * contributor license agreements. See the NOTICE file distributed with 3 * this work for additional information regarding copyright ownership. 4 * The ASF licenses this file to You under the Apache License, Version 2.0 5 * (the "License"); you may not use this file except in compliance with 6 * the License. You may obtain a copy of the License at 7 * 8 * http //www.apache.org/licenses/LICENSE-2.0 9 * 10 * Unless required by applicable law or agreed to in writing, software 11 * distributed under the License is distributed on an "AS IS" BASIS, 12 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 13 * See the License for the specific language governing permissions and 14 * limitations under the License. 15 */ 16 17 #include "apr.h" 18 #include "apr_strings.h" 19 #include "apr_getopt.h" 20 #include "apr_general.h" 21 #include "apr_lib.h" 22 #include "apr_md5.h" 23 #include "apr_time.h" 24 #include "apr_version.h" 25 #include "apu_version.h" 26 27 #define APR_WANT_STDIO 28 #define APR_WANT_STRFUNC 29 #include "apr_want.h" 30 31 #define CORE_PRIVATE 32 #include "ap_config.h" 33 #include "httpd.h" 34 #include "http_main.h" 35 #include "http_log.h" 36 #include "http_config.h" 37 #include "http_vhost.h" 38 #include "apr_uri.h" 39 #include "util_ebcdic.h" 40 #include "ap_mpm.h" 41 #include "mpm_common.h" 42 43 /* WARNING Win32 binds http_main.c dynamically to the server. Please place 44 * extern functions and global data in another appropriate module. 45 * 46 * Most significant main() global data can be found in http_config.c 47 */ 48 49 /* XXX - We should be able to grab the per-MPM settings here too */ 50 static void show_compile_settings(void) 51 { 52 printf("Server version %s\n", ap_get_server_version()); 53 printf("Server built %s\n", ap_get_server_built()); 54 printf("Server s Module Magic Number %u %u\n", 55 MODULE_MAGIC_NUMBER_MAJOR, MODULE_MAGIC_NUMBER_MINOR); 56 printf("Server loaded APR %s, APR-UTIL %s\n", 57 apr_version_string(), apu_version_string()); 58 printf("Compiled using APR %s, APR-UTIL %s\n", 59 APR_VERSION_STRING, APU_VERSION_STRING); 60 /* sizeof(foo) is long on some platforms so we might as well 61 * make it long everywhere to keep the printf format 62 * consistent 63 */ 64 printf("Architecture %ld-bit\n", 8 * (long)sizeof(void *)); 65 printf("Server compiled with....\n"); 66 #ifdef BIG_SECURITY_HOLE 67 printf(" -D BIG_SECURITY_HOLE\n"); 68 #endif 69 70 #ifdef SECURITY_HOLE_PASS_AUTHORIZATION 71 printf(" -D SECURITY_HOLE_PASS_AUTHORIZATION\n"); 72 #endif 73 74 #ifdef APACHE_MPM_DIR 75 printf(" -D APACHE_MPM_DIR=\"%s\"\n", APACHE_MPM_DIR); 76 #endif 77 78 #ifdef HAVE_SHMGET 78 #ifdef HAVE_SHMGET 79 printf(" -D HAVE_SHMGET\n"); 80 #endif 81 82 #if APR_FILE_BASED_SHM 83 printf(" -D APR_FILE_BASED_SHM\n"); 84 #endif 85 86 #if APR_HAS_SENDFILE 87 printf(" -D APR_HAS_SENDFILE\n"); 88 #endif 89 90 #if APR_HAS_MMAP 91 printf(" -D APR_HAS_MMAP\n"); 92 #endif 93 94 #ifdef NO_WRITEV 95 printf(" -D NO_WRITEV\n"); 96 #endif 97 98 #ifdef NO_LINGCLOSE 99 printf(" -D NO_LINGCLOSE\n"); 100 #endif 101 102 #if APR_HAVE_IPV6 103 printf(" -D APR_HAVE_IPV6 (IPv4-mapped addresses "); 104 #ifdef AP_ENABLE_V4_MAPPED 105 printf("enabled)\n"); 106 #else 107 printf("disabled)\n"); 108 #endif 109 #endif 110 111 #if APR_USE_FLOCK_SERIALIZE 112 printf(" -D APR_USE_FLOCK_SERIALIZE\n"); 113 #endif 114 115 #if APR_USE_SYSVSEM_SERIALIZE 116 printf(" -D APR_USE_SYSVSEM_SERIALIZE\n"); 117 #endif 118 119 #if APR_USE_POSIXSEM_SERIALIZE 120 printf(" -D APR_USE_POSIXSEM_SERIALIZE\n"); 121 #endif 122 123 #if APR_USE_FCNTL_SERIALIZE 124 printf(" -D APR_USE_FCNTL_SERIALIZE\n"); 125 #endif 126 127 #if APR_USE_PROC_PTHREAD_SERIALIZE 128 printf(" -D APR_USE_PROC_PTHREAD_SERIALIZE\n"); 129 #endif 130 131 #if APR_USE_PTHREAD_SERIALIZE 132 printf(" -D APR_USE_PTHREAD_SERIALIZE\n"); 133 #endif 134 135 #if APR_PROCESS_LOCK_IS_GLOBAL 136 printf(" -D APR_PROCESS_LOCK_IS_GLOBAL\n"); 137 #endif 138 139 #ifdef SINGLE_LISTEN_UNSERIALIZED_ACCEPT 140 printf(" -D SINGLE_LISTEN_UNSERIALIZED_ACCEPT\n"); 141 #endif 142 143 #if APR_HAS_OTHER_CHILD 144 printf(" -D APR_HAS_OTHER_CHILD\n"); 145 #endif 146 147 #ifdef AP_HAVE_RELIABLE_PIPED_LOGS 148 printf(" -D AP_HAVE_RELIABLE_PIPED_LOGS\n"); 149 #endif 150 151 #ifdef BUFFERED_LOGS 152 printf(" -D BUFFERED_LOGS\n"); 153 #ifdef PIPE_BUF 154 printf(" -D PIPE_BUF=%ld\n",(long)PIPE_BUF); 155 #endif 156 #endif 157 158 #if APR_CHARSET_EBCDIC 159 printf(" -D APR_CHARSET_EBCDIC\n"); 160 #endif 161 162 #ifdef APACHE_XLATE 163 printf(" -D APACHE_XLATE\n"); 164 #endif 165 166 #ifdef NEED_HASHBANG_EMUL 167 printf(" -D NEED_HASHBANG_EMUL\n"); 168 #endif 169 170 #ifdef SHARED_CORE 171 printf(" -D SHARED_CORE\n"); 172 #endif 173 174 /* This list displays the compiled in default paths */ 175 #ifdef HTTPD_ROOT 176 printf(" -D HTTPD_ROOT=\"" HTTPD_ROOT "\"\n"); 177 #endif 178 179 #ifdef SUEXEC_BIN 180 printf(" -D SUEXEC_BIN=\"" SUEXEC_BIN "\"\n"); 181 #endif 182 183 #if defined(SHARED_CORE) defined(SHARED_CORE_DIR) 184 printf(" -D SHARED_CORE_DIR=\"" SHARED_CORE_DIR "\"\n"); 185 #endif 186 187 #ifdef DEFAULT_PIDLOG 188 printf(" -D DEFAULT_PIDLOG=\"" DEFAULT_PIDLOG "\"\n"); 189 #endif 190 191 #ifdef DEFAULT_SCOREBOARD 192 printf(" -D DEFAULT_SCOREBOARD=\"" DEFAULT_SCOREBOARD "\"\n"); 193 #endif 194 195 #ifdef DEFAULT_LOCKFILE 196 printf(" -D DEFAULT_LOCKFILE=\"" DEFAULT_LOCKFILE "\"\n"); 197 #endif 198 199 #ifdef DEFAULT_ERRORLOG 200 printf(" -D DEFAULT_ERRORLOG=\"" DEFAULT_ERRORLOG "\"\n"); 201 #endif 202 203 #ifdef AP_TYPES_CONFIG_FILE 204 printf(" -D AP_TYPES_CONFIG_FILE=\"" AP_TYPES_CONFIG_FILE "\"\n"); 205 #endif 206 207 #ifdef SERVER_CONFIG_FILE 208 printf(" -D SERVER_CONFIG_FILE=\"" SERVER_CONFIG_FILE "\"\n"); 209 #endif 210 } 211 212 static void destroy_and_exit_process(process_rec *process, 213 int process_exit_value) 214 { 215 apr_pool_destroy(process- pool); /* and destroy all descendent pools */ 216 apr_terminate(); 217 exit(process_exit_value); 218 } 219 220 static process_rec *init_process(int *argc, const char * const * *argv) 221 { 222 process_rec *process; 223 apr_pool_t *cntx; 224 apr_status_t stat; 225 const char *failed = "apr_app_initialize()"; 226 227 stat = apr_app_initialize(argc, argv, NULL); 228 if (stat == APR_SUCCESS) { 229 failed = "apr_pool_create()"; 230 stat = apr_pool_create( cntx, NULL); 231 } 232 233 if (stat != APR_SUCCESS) { 234 /* For all intents and purposes, this is impossibly unlikely, 235 * but APR doesn t exist yet, we can t use it for reporting 236 * these earliest two failures; 237 */ 238 char ctimebuff[APR_CTIME_LEN]; 239 apr_ctime(ctimebuff, apr_time_now()); 240 fprintf(stderr, "[%s] [crit] (%d) %s %s failed " 241 "to initial context, exiting\n", 242 ctimebuff, stat, (*argv)[0], failed); 243 apr_terminate(); 244 exit(1); 245 } 246 247 apr_pool_tag(cntx, "process"); 248 ap_open_stderr_log(cntx); 249 250 /* Now we have initialized apr and our logger, no more 251 * exceptional error reporting required for the lifetime 252 * of this server process. 253 */ 254 255 process = apr_palloc(cntx, sizeof(process_rec)); 256 process- pool = cntx; 257 258 apr_pool_create( process- pconf, process- pool); 259 apr_pool_tag(process- pconf, "pconf"); 260 process- argc = *argc; 261 process- argv = *argv; 262 process- short_name = apr_filepath_name_get((*argv)[0]); 263 return process; 264 } 265 266 static void usage(process_rec *process) 267 { 268 const char *bin = process- argv[0]; 269 char pad[MAX_STRING_LEN]; 270 unsigned i; 271 272 for (i = 0; i strlen(bin); i++) { 273 pad[i] = ; 274 } 275 276 pad[i] = \0 ; 277 278 #ifdef SHARED_CORE 279 ap_log_error(APLOG_MARK, APLOG_STARTUP, 0, NULL , 280 "Usage %s [-R directory] [-D name] [-d directory] [-f file]", 281 bin); 282 #else 283 ap_log_error(APLOG_MARK, APLOG_STARTUP, 0, NULL, 284 "Usage %s [-D name] [-d directory] [-f file]", bin); 285 #endif 286 287 ap_log_error(APLOG_MARK, APLOG_STARTUP, 0, NULL, 288 " %s [-C \"directive\"] [-c \"directive\"]", pad); 289 290 #ifdef WIN32 291 ap_log_error(APLOG_MARK, APLOG_STARTUP, 0, NULL, 292 " %s [-w] [-k start|restart|stop|shutdown]", pad); 293 ap_log_error(APLOG_MARK, APLOG_STARTUP, 0, NULL, 294 " %s [-k install|config|uninstall] [-n service_name]", 295 pad); 296 #endif 297 #ifdef AP_MPM_WANT_SIGNAL_SERVER 298 ap_log_error(APLOG_MARK, APLOG_STARTUP, 0, NULL, 299 " %s [-k start|restart|graceful|stop]", 300 pad); 301 #endif 302 ap_log_error(APLOG_MARK, APLOG_STARTUP, 0, NULL, 303 " %s [-v] [-V] [-h] [-l] [-L] [-t] [-S]", pad); 304 ap_log_error(APLOG_MARK, APLOG_STARTUP, 0, NULL, 305 "Options "); 306 307 #ifdef SHARED_CORE 308 ap_log_error(APLOG_MARK, APLOG_STARTUP, 0, NULL, 309 " -R directory specify an alternate location for " 310 "shared object files"); 311 #endif 312 313 ap_log_error(APLOG_MARK, APLOG_STARTUP, 0, NULL, 314 " -D name define a name for use in " 315 " IfDefine name directives"); 316 ap_log_error(APLOG_MARK, APLOG_STARTUP, 0, NULL, 317 " -d directory specify an alternate initial " 318 "ServerRoot"); 319 ap_log_error(APLOG_MARK, APLOG_STARTUP, 0, NULL, 320 " -f file specify an alternate ServerConfigFile"); 321 ap_log_error(APLOG_MARK, APLOG_STARTUP, 0, NULL, 322 " -C \"directive\" process directive before reading " 323 "config files"); 324 ap_log_error(APLOG_MARK, APLOG_STARTUP, 0, NULL, 325 " -c \"directive\" process directive after reading " 326 "config files"); 327 328 #ifdef NETWARE 329 ap_log_error(APLOG_MARK, APLOG_STARTUP, 0, NULL, 330 " -n name set screen name"); 331 #endif 332 #ifdef WIN32 333 ap_log_error(APLOG_MARK, APLOG_STARTUP, 0, NULL, 334 " -n name set service name and use its " 335 "ServerConfigFile"); 336 ap_log_error(APLOG_MARK, APLOG_STARTUP, 0, NULL, 337 " -k start tell Apache to start"); 338 ap_log_error(APLOG_MARK, APLOG_STARTUP, 0, NULL, 339 " -k restart tell running Apache to do a graceful " 340 "restart"); 341 ap_log_error(APLOG_MARK, APLOG_STARTUP, 0, NULL, 342 " -k stop|shutdown tell running Apache to shutdown"); 343 ap_log_error(APLOG_MARK, APLOG_STARTUP, 0, NULL, 344 " -k install install an Apache service"); 345 ap_log_error(APLOG_MARK, APLOG_STARTUP, 0, NULL, 346 " -k config change startup Options of an Apache " 347 "service"); 348 ap_log_error(APLOG_MARK, APLOG_STARTUP, 0, NULL, 349 " -k uninstall uninstall an Apache service"); 350 ap_log_error(APLOG_MARK, APLOG_STARTUP, 0, NULL, 351 " -w hold open the console window on error"); 352 #endif 353 354 ap_log_error(APLOG_MARK, APLOG_STARTUP, 0, NULL, 355 " -e level show startup errors of level " 356 "(see LogLevel)"); 357 ap_log_error(APLOG_MARK, APLOG_STARTUP, 0, NULL, 358 " -E file log startup errors to file"); 359 ap_log_error(APLOG_MARK, APLOG_STARTUP, 0, NULL, 360 " -v show version number"); 361 ap_log_error(APLOG_MARK, APLOG_STARTUP, 0, NULL, 362 " -V show compile settings"); 363 ap_log_error(APLOG_MARK, APLOG_STARTUP, 0, NULL, 364 " -h list available command line options " 365 "(this page)"); 366 ap_log_error(APLOG_MARK, APLOG_STARTUP, 0, NULL, 367 " -l list compiled in modules"); 368 ap_log_error(APLOG_MARK, APLOG_STARTUP, 0, NULL, 369 " -L list available configuration " 370 "directives"); 371 ap_log_error(APLOG_MARK, APLOG_STARTUP, 0, NULL, 372 " -t -D DUMP_VHOSTS show parsed settings (currently only " 373 "vhost settings)"); 374 ap_log_error(APLOG_MARK, APLOG_STARTUP, 0, NULL, 375 " -S a synonym for -t -D DUMP_VHOSTS"); 376 ap_log_error(APLOG_MARK, APLOG_STARTUP, 0, NULL, 377 " -t run syntax check for config files"); 378 379 destroy_and_exit_process(process, 1); 380 } 381 382 int main(int argc, const char * const argv[]) 383 { 384 char c; 385 int configtestonly = 0; 386 const char *confname = SERVER_CONFIG_FILE; 387 const char *def_server_root = HTTPD_ROOT; 388 const char *temp_error_log = NULL; 389 process_rec *process; 390 server_rec *server_conf; 391 apr_pool_t *pglobal; 392 apr_pool_t *pconf; 393 apr_pool_t *plog; /* Pool of log streams, reset _after_ each read of conf */ 394 apr_pool_t *ptemp; /* Pool for temporary config stuff, reset often */ 395 apr_pool_t *pcommands; /* Pool for -D, -C and -c switches */ 396 apr_getopt_t *opt; 397 apr_status_t rv; 398 module **mod; 399 const char *optarg; 400 APR_OPTIONAL_FN_TYPE(ap_signal_server) *signal_server; 401 402 AP_MONCONTROL(0); /* turn off profiling of startup */ 403 404 process = init_process( argc, argv); 405 pglobal = process- pool; 406 pconf = process- pconf; 407 ap_server_argv0 = process- short_name; 408 409 #if APR_CHARSET_EBCDIC 410 if (ap_init_ebcdic(pglobal) != APR_SUCCESS) { 411 destroy_and_exit_process(process, 1); 412 } 413 #endif 414 415 apr_pool_create( pcommands, pglobal); 416 apr_pool_tag(pcommands, "pcommands"); 417 ap_server_pre_read_config = apr_array_make(pcommands, 1, sizeof(char *)); 418 ap_server_post_read_config = apr_array_make(pcommands, 1, sizeof(char *)); 419 ap_server_config_defines = apr_array_make(pcommands, 1, sizeof(char *)); 420 421 ap_setup_prelinked_modules(process); 422 423 ap_run_rewrite_args(process); 424 425 /* Maintain AP_SERVER_BASEARGS list in http_main.h to allow the MPM 426 * to safely pass on our args from its rewrite_args() handler. 427 */ 428 apr_getopt_init( opt, pcommands, process- argc, process- argv); 429 430 while ((rv = apr_getopt(opt, AP_SERVER_BASEARGS, c, optarg)) 431 == APR_SUCCESS) { 432 char **new; 433 434 switch (c) { 435 case c 436 new = (char **)apr_array_push(ap_server_post_read_config); 437 *new = apr_pstrdup(pcommands, optarg); 438 break; 439 440 case C 441 new = (char **)apr_array_push(ap_server_pre_read_config); 442 *new = apr_pstrdup(pcommands, optarg); 443 break; 444 445 case d 446 def_server_root = optarg; 447 break; 448 449 case D 450 new = (char **)apr_array_push(ap_server_config_defines); 451 *new = apr_pstrdup(pcommands, optarg); 452 break; 453 454 case e 455 if (strcasecmp(optarg, "emerg") == 0) { 456 ap_default_loglevel = APLOG_EMERG; 457 } 458 else if (strcasecmp(optarg, "alert") == 0) { 459 ap_default_loglevel = APLOG_ALERT; 460 } 461 else if (strcasecmp(optarg, "crit") == 0) { 462 ap_default_loglevel = APLOG_CRIT; 463 } 464 else if (strncasecmp(optarg, "err", 3) == 0) { 465 ap_default_loglevel = APLOG_ERR; 466 } 467 else if (strncasecmp(optarg, "warn", 4) == 0) { 468 ap_default_loglevel = APLOG_WARNING; 469 } 470 else if (strcasecmp(optarg, "notice") == 0) { 471 ap_default_loglevel = APLOG_NOTICE; 472 } 473 else if (strcasecmp(optarg, "info") == 0) { 474 ap_default_loglevel = APLOG_INFO; 475 } 476 else if (strcasecmp(optarg, "debug") == 0) { 477 ap_default_loglevel = APLOG_DEBUG; 478 } 479 else { 480 usage(process); 481 } 482 break; 483 484 case E 485 temp_error_log = apr_pstrdup(process- pool, optarg); 486 break; 487 488 case X 489 new = (char **)apr_array_push(ap_server_config_defines); 490 *new = "DEBUG"; 491 break; 492 493 case f 494 confname = optarg; 495 break; 496 497 case v 498 printf("Server version %s\n", ap_get_server_version()); 499 printf("Server built %s\n", ap_get_server_built()); 500 destroy_and_exit_process(process, 0); 501 502 case V 503 show_compile_settings(); 504 destroy_and_exit_process(process, 0); 505 506 case l 507 ap_show_modules(); 508 destroy_and_exit_process(process, 0); 509 510 case L 511 ap_show_directives(); 512 destroy_and_exit_process(process, 0); 513 514 case t 515 configtestonly = 1; 516 break; 517 518 case S 519 configtestonly = 1; 520 new = (char **)apr_array_push(ap_server_config_defines); 521 *new = "DUMP_VHOSTS"; 522 break; 523 524 case h 525 case ? 526 usage(process); 527 } 528 } 529 530 /* bad cmdline option? then we die */ 531 if (rv != APR_EOF || opt- ind opt- argc) { 532 usage(process); 533 } 534 535 apr_pool_create( plog, pglobal); 536 apr_pool_tag(plog, "plog"); 537 apr_pool_create( ptemp, pconf); 538 apr_pool_tag(ptemp, "ptemp"); 539 540 /* Note that we preflight the config file once 541 * before reading it _again_ in the main loop. 542 * This allows things, log files configuration 543 * for example, to settle down. 544 */ 545 546 ap_server_root = def_server_root; 547 if (temp_error_log) { 548 ap_replace_stderr_log(process- pool, temp_error_log); 549 } 550 server_conf = ap_read_config(process, ptemp, confname, ap_conftree); 551 if (ap_run_pre_config(pconf, plog, ptemp) != OK) { 552 ap_log_error(APLOG_MARK, APLOG_STARTUP |APLOG_ERR, 0, 553 NULL, "Pre-configuration failed"); 554 destroy_and_exit_process(process, 1); 555 } 556 557 ap_process_config_tree(server_conf, ap_conftree, process- pconf, ptemp); 558 ap_fixup_virtual_hosts(pconf, server_conf); 559 ap_fini_vhost_config(pconf, server_conf); 560 apr_hook_sort_all(); 561 if (configtestonly) { 562 ap_log_error(APLOG_MARK, APLOG_STARTUP, 0, NULL, "Syntax OK"); 563 destroy_and_exit_process(process, 0); 564 } 565 566 signal_server = APR_RETRIEVE_OPTIONAL_FN(ap_signal_server); 567 if (signal_server) { 568 int exit_status; 569 570 if (signal_server( exit_status, pconf) != 0) { 571 destroy_and_exit_process(process, exit_status); 572 } 573 } 574 575 apr_pool_clear(plog); 576 577 if ( ap_run_open_logs(pconf, plog, ptemp, server_conf) != OK) { 578 ap_log_error(APLOG_MARK, APLOG_STARTUP |APLOG_ERR, 579 0, NULL, "Unable to open logs"); 580 destroy_and_exit_process(process, 1); 581 } 582 583 if ( ap_run_post_config(pconf, plog, ptemp, server_conf) != OK) { 584 ap_log_error(APLOG_MARK, APLOG_STARTUP |APLOG_ERR, 0, 585 NULL, "Configuration Failed"); 586 destroy_and_exit_process(process, 1); 587 } 588 589 apr_pool_destroy(ptemp); 590 591 for (;;) { 592 apr_hook_deregister_all(); 593 apr_pool_clear(pconf); 594 595 for (mod = ap_prelinked_modules; *mod != NULL; mod++) { 596 ap_register_hooks(*mod, pconf); 597 } 598 599 /* This is a hack until we finish the code so that it only reads 600 * the config file once and just operates on the tree already in 601 * memory. rbb 602 */ 603 ap_conftree = NULL; 604 apr_pool_create( ptemp, pconf); 605 apr_pool_tag(ptemp, "ptemp"); 606 ap_server_root = def_server_root; 607 server_conf = ap_read_config(process, ptemp, confname, ap_conftree); 608 if (ap_run_pre_config(pconf, plog, ptemp) != OK) { 609 ap_log_error(APLOG_MARK, APLOG_STARTUP |APLOG_ERR, 610 0, NULL, "Pre-configuration failed"); 611 destroy_and_exit_process(process, 1); 612 } 613 614 ap_process_config_tree(server_conf, ap_conftree, process- pconf, ptemp); 615 ap_fixup_virtual_hosts(pconf, server_conf); 616 ap_fini_vhost_config(pconf, server_conf); 617 apr_hook_sort_all(); 618 apr_pool_clear(plog); 619 if (ap_run_open_logs(pconf, plog, ptemp, server_conf) != OK) { 620 ap_log_error(APLOG_MARK, APLOG_STARTUP |APLOG_ERR, 621 0, NULL, "Unable to open logs"); 622 destroy_and_exit_process(process, 1); 623 } 624 625 if (ap_run_post_config(pconf, plog, ptemp, server_conf) != OK) { 626 ap_log_error(APLOG_MARK, APLOG_STARTUP |APLOG_ERR, 627 0, NULL, "Configuration Failed"); 628 destroy_and_exit_process(process, 1); 629 } 630 631 apr_pool_destroy(ptemp); 632 apr_pool_lock(pconf, 1); 633 634 ap_run_optional_fn_retrieve(); 635 636 if (ap_mpm_run(pconf, plog, server_conf)) 637 break; 638 639 apr_pool_lock(pconf, 0); 640 } 641 642 apr_pool_lock(pconf, 0); 643 destroy_and_exit_process(process, 0); 644 645 return 0; /* Termination ok */ 646 } 647 648 /* force Expat to be linked into the server executable */ 649 #if defined(USE_EXPAT) !defined(SHARED_CORE_BOOTSTRAP) 650 #include "xmlparse.h" 651 const XML_LChar *suck_in_expat(void); 652 const XML_LChar *suck_in_expat(void) 653 { 654 return XML_ErrorString(XML_ERROR_NONE); 655 } 656 #endif /* USE_EXPAT */ 657 658 #ifndef SHARED_CORE_BOOTSTRAP 659 /* 660 * Force apr_password_validate() into the image so that modules like 661 * mod_auth can use it even if they re dynamically loaded. 662 */ 663 void suck_in_apr_password_validate(void); 664 void suck_in_apr_password_validate(void) 665 { 666 apr_password_validate("a", "b"); 667 } 668 #endif 669 670 #ifdef AP_USING_AUTOCONF 671 /* This ugly little hack pulls any function referenced in exports.c into 672 * the web server. exports.c is generated during the build, and it 673 * has all of the APR functions specified by the apr/apr.exports and 674 * apr-util/aprutil.exports files. 675 */ 676 const void *suck_in_APR(void); 677 const void *suck_in_APR(void) 678 { 679 extern const void *ap_ugly_hack; 680 681 return ap_ugly_hack; 682 } 683 #endif
https://w.atwiki.jp/cohstatsjp/pages/221.html
Infantry Mortar Commandos Contents 1 Tactics 2 History 3 Built From 3.1 Glider HQ 4 Squad Abilities 4.1 Concealing Smoke 5 Squad Weapons 5.1 3in Mortar 5.2 Sten SMG Mortar Commandos Squad Size 6 Capture Rate 1 Sup Threshold 0.35 Health 390 Sight 35 Pin Threshold 0.8 Cost 510 Detection 7/0 Recovery Rate 0.012 Hotkey M Population 6 Time 36 Retreat Modifier 0.5 Target Type infantry_soldier Upkeep 9.0144 Reinforce Cost 0.4119 Critical Type infantry Squad Slots Reinforce Time 1.5 Tactics Commando Mortars can only be created in a glider HQ. Commando Mortars operate in the same way to American and German mortars. History The Airlanding troops of the British Airborne were tasked with assaulting German positions prior to the D-Day landings. They landed their gliders in Coup de Main assaults on enemy positions, surprising the German defenders in risky attacks. They were all volunteers, and well-trained for their dangerous job, and continued to act as elite ground infantry once the airborne operations were over. The MK.II ML 3 mortar was the standard mortar of the infantry battalions. It s performance was similar to the American M1 81mm and the German 8cm GrW34. The Commandos in Company of Heroes are actually Airlanding troops from an Airborne Division, or SAS (Special Air Service) Commandos. Their distinctive red berets indicate they re airborne troops, or SAS troops, as Commandos wore green berets. Commandos came from several branches (Royal Army Commandos, Royal Marine Commandos, and Royal Navy Commandos) and none were involved in glider operations. Built From Glider HQ [Expand][Hide] Cost 100 Activation targeted Duration _ Target tp_position Recharge 75 Hotkey Effects Request a Glider Headquarters capable of producing Mortar Commandos, PIAT Commandos, and Heavy Machine Gun Commmandos. ESee Ability Glider HQ for details. Squad Abilities Concealing Smoke [Expand][Hide] Cost Activation timed Duration 14 Target tp_any Recharge 30 Hotkey S Effects Break any suppression or pinning effects on the squad and envelope the Commandos in concealing smoke. ESee Ability Concealing Smoke for details. Squad Weapons 3in Mortar [Expand][Hide] Weapon 3in Mortar See Weapon 3in Mortar for details. Sten SMG [Expand][Hide] Weapon Sten SMG See Weapon Sten SMG for details. Retrieved from http //coh-stats.com/Infantry Mortar_Commandos
https://w.atwiki.jp/dslua/pages/15.html
MicroLuaDS 3.0のReadme.txtのGoogle翻訳と適当な修正を加えたものです。 Micro Lua DS 3.0 By Risike Official website www.microlua.risike.com Dev platform http //microlua.googlecode.com Micro Lua DS 3.0 By Risike 公式のウェブサイト：http //www.microlua.risike.com devのプラットフォーム：http //microlua.googlecode.com 注：FireFoxにより、公式のウェブサイトに接続しようとすると「攻撃サイトとして報告されています！」「この Web ページ (www.microlua.risike.com) は攻撃サイトであると報告されており、セキュリティ設定に従いブロックされました。」と表示されます。警告を無視して入ったことがないので内容は不明。 HOW TO INSTALL? －－－－－－－－－－ Put the lua directory at the root of your SD card. You can put your own scripts in /lua/scripts, it's the best way. Put microlua.nds, microlua.sc.nds or microlua.ds.gba where you want on you SD card. インストール方法？ －－－－－－－－－－ マジコンのSDカードのルートにluaディレクトリに配置します。あなたの独自のスクリプトは/lua/scriptsに置くのが良い。 microlua.nds、 microlua.sc.ndsそしてmicrolua.ds.gbaをSDカードに配置します。 RELEASE NOTE －－－－－－－－－－ 3.0 リリースノート －－－－－－－－－－ 3.0： After the 3.0 prerelease, compiling with libfat20080530 made relative paths usable (thanks to Quent42340). 3.0プレリリース後、libfat20080530 でコンパイル相対パスをした （Quent42340に感謝）使用可能。 Fixed bugs － Double-click issue. － Jpg loading issue. You can now load .jpg and .jpeg files without problem. － Image loading optimisation. You can load and destroy images, font and maps indefinitely. － No more "Oops unhandled error". － The Canvas ATTR_Y2 bug. － The "non-permanent" scaling problem. － The Stylus.newPress problem. － Big speed increase during Lua file loading, so that Micro Lua and your scripts are loaded faster. 修正されたバグ： － ダブルクリックの問題。 － またはJPGの読み込みの問題。jpgとjpeg のファイルを問題なく読み込むことができます。 － 画像の読み込みの最適化。あなたは読み込むことができます、画像、フォント、マップを破壊する 無期限。 － これ以上の"おっと"エラーが処理されない。 － Canvas ATTR_Y2バグを修正。 － "non-permanent"スケーリングの問題。 － Stylus.newPressの問題。 ルアファイルの読み込み中 - ビッグ速度の増加なので、マイクロLuaで、そのお スクリプトが速く読み込まれます。 New features － Added Wifi support. － Added DateTime support. － Added Rumble support. － Added Motion support. － Sound syntax changed. － You can now play several mods in the same time. － SFX support (you can now play wave files). － Added a new render() function, no need to use startDrawing() and stopDrawing(), but you can still use them. － Added a MICROLUA_VERSION global variable. － You can now customize the shell in the shell.ini file. － Stylus support in the shell. － No more position limit for direct drawing and printing. － Added a new getStringWidth function which return the width (in pixel) of a string, using a custom font. 新機能： － 無線LAN（Wifi）のサポートを追加しました。 － DateTimeがサポートされました。 － Rumbleのサポートを追加しました。 － モーションのサポートを追加しました。 － サウンドの構文が変更されました。 － これは、同じ時間内にいくつかの改造を再生することができます。 － SFXサポート（あなたが今波ファイルを再生することができます）。 － （）とstartDrawingを使用する必要はありません新しいレンダリング（）関数を追加 （）stopDrawingが、まだそれらを使用することができます。 － グローバル変数MICROLUA_VERSIONを追加しました。 － あなたが今shell.iniファイルでシェルをカスタマイズできます。 シェルで - スタイラスをサポートします。 － 直接描画および印刷用にこれ以上の位置の制限。 － ）の戻り値のピクセルの幅（新しいgetStringWidth機能を追加 文字列は、カスタムフォントを使用します。 Removed － Keyboard library removed but you can download it on the official website in open source. So you can modify it. 削除： － キーボードのライブラリは、しかし、あなたは、公式ウェブサイトからダウンロードすることができます オープンソース。だからあなたはそれを変更することができます。 2.0 beta － Displaying is about 3X FASTER! － Some syntax changes (see "syntax changes.txt"). － Adding a Canvas system. You can now create a Canvas, adding some objects inside like lines, rectangles, images...etc. Then call Canvas.draw function to draw all items. This method is aboute 30X FASTER than displaying of Micro Lua 1.0!!! On no$gba you can display 1600 images without loss of FPS. － Adding an INI file management system. You can now read and write ini files. － Adding ScrollMaps. They are maps we can scroll pixel by pixel. It's faster than normal Maps (faster than 1.0 too) but you can only display them in fullscreen. － A getTile function for maps. － Some bugs fixes. － Better errors management. 2.0ベータ版： － 表示について3倍高速です！ － いくつかの文法的な変更は、（""）の構文changes.txtを参照してください。 － キャンバスのシステムを追加します。あなたは現在、いくつかのオブジェクトを追加するキャンバスを作成することができます のような行の内部、四角形、画像...など次にCanvas.draw関数を呼び出す すべての項目を描画する。このメソッドは、表示よりもaboute 30倍高速です マイクロルア1.0！ない$の場合はFPSを失うことなく1600の画像を表示することができますGBAは。 － INIファイルの管理システムを追加します。これで読むことができるとiniファイルを作成します。 － 追加ScrollMaps。私たちはピクセルごとにスクロールすることができます地図です。それは高速だ より速く1.0も）しかし、あなたはこの中でのみそれらを表示することができます通常のマップ（より フルスクリーン。 － マップのgetTile関数です。 － いくつかのバグが修正。 － より良いエラー管理。 1.0.1 beta This version fixes the bug with Exceptions. Now when an error occurs, it is displayed on the lower screen. 1.0.1ベータ版： このバージョンは、例外のバグを修正します。これで、エラーが発生すると、それは 下の画面に表示されます。 1.0 beta First public release. 1.0ベータ版： 最初の公開リリース。
https://w.atwiki.jp/usb_audio/pages/58.html
原文：Audio Devices Rev. 2.0 Spec and Adopters Agreement(ZIP) USB Device Class Definition for Audio Devices Release 2.0 May 31, 2006 16 2 Management Overview The USB is very well suited for transport of audio ranging from low fidelity voice connections to high quality, multi-channel audio streams. The USB has become a ubiquitous connector on modern PC’s and is well-understood by most consumers today. As such, it has become the connector of choice for many peripherals and is indeed the simplest and most pervasive digital audio connector available today. With the advent of the High Speed USB, consumers can count on this medium to meet all of their audio needs today and into the future. Many applications from communications, to entertainment, to music recording and playback, can take advantage of audio features of the USB. In principle, a versatile bus specification like the USB provides many ways to propagate and/or control digital audio. For the industry, however, it is very important that audio transport mechanisms be well defined and standardized on the USB. Only in this way can interoperability be guaranteed among the many possible audio devices on the USB. Standardized audio transport mechanisms also help to keep software drivers as generic as possible. The Audio Device Class described in this document satisfies those requirements. It is written and revised by experts in the audio field. Other device classes that address audio in some way should refer to this document for their audio interface specification. An essential issue in audio is synchronization of the data streams. Indeed, the smallest artifacts are easily detected by the human ear. Therefore, a robust synchronization scheme on isochronous transfers has been developed and incorporated in the USB Specification. The Audio Device Class definition adheres to this synchronization scheme to transport audio data reliably over the bus. This document contains all necessary information for a designer to build a USB-compliant device that incorporates audio functionality. It specifies the standard and class-specific descriptors that must be present in each USB audio function. It further explains the use of class-specific requests that allow for full audio function control. A number of predefined data formats are listed and fully documented. Each format defines a standard way of transporting audio over the USB. Provisions have been made so that vendor-specific audio formats and compression schemes can be handled. Many of the changes introduced in Version 2.0 of the USB Specification for Audio Devices take advantage of the new features provided in the USB 2.0 Specification. With the additional bandwidth made available, high speed USB operation allows the transport of multiple channels of high bit rate audio. This expands the range of solutions provided by USB audio devices but also challenges the way in which they operate. In addition to supporting the additional bandwidth, the specification supports new codec types for consumer audio applications, provides numerous clarifications of the original specification and extensions to support various changes in the core specification. The changes are not generally backwards compatible to 1.0 because that would too severely limit this new class of devices. 2.1 Overview of Key Differences between ADC v1.0 and v2.0 The following list is not an exhaustive list of all changes that have been introduced. For complete information, refer to the full specification. Pay special attention to Sections 1 through 6! • Complete support for high speed operation - no longer are audio class devices limited to full speed operation. • The notion of physical and logical Audio channel clusters. • The number of predefined spatial locations has increased. In addition, a virtual spatial location called Raw Data was introduced. • Use of the interface association descriptor - The standard Interface Association mechanism is used to describe an Audio Interface Collection. The former class specific mechanism was deprecated. • Descriptor updates fixed offsets associated with many descriptors and enlarged three byte fields into four bytes. • Extensive support for interrupts to inform the host about dynamic changes that occur on the different addressable Entities (Clock Entities, Terminals, Units, interfaces and endpoints) inside the audio function. • More clarification text on the audio function. USB Device Class Definition for Audio Devices Release 2.0 May 31, 2006 17 • Audio Control Changes. – Control attribute changes. – Mixer Unit control request (set/get pairs changed). – Many updates in the control descriptions. • Added support for clock domains, clock description and clock control. • Added additional Audio Controls inside a Feature Unit (Input, Gain, Input Gain Pad …) • Added bit pairs in descriptors to indicate presence and programmability of every Control • Prohibited the use of Alternate Setting switching to change sampling frequencies. Instead, Clock Entities are introduced that can be manipulated (through the AudioControl interface) to select operating sampling frequencies. • Split off the examples in a separate document. • Allowed binding between physical buttons on the audio function and the corresponding Audio Control. Prescribed how this is done. • Added an Effect Unit to group algorithms that work on logical channels separately but require multiple parameters to manipulate the effect (as opposed to basic (single parameter) manipulation, performed in a Feature Unit). • Introduced Parametric Equalizer Section Effect Unit. • Rearranged Reverb, Modulation Delay and Dynamic Compressor PUs under the new Effect Unit. • Added the concept of audio function Category. The Category indicates the primary use of the audio function as envisioned by the manufacturer. • Added the Sampling Rate Converter Unit. • Added a means to express Latency of individual building blocks within the audio function. • Added Encoder support. USB Device Class Definition for Audio Devices 3 Functional Characteristics 3.1 Introduction In many cases, audio functionality does not exist as a standalone device. It is one capability that, together with other functions, constitutes a “composite” device. A perfect example of this is a DVD-ROM player, which can incorporate video, audio, data storage, and transport control. The audio function is thus located at the interface level in the device class hierarchy. It consists of a number of interfaces grouping related pipes that together implement the interface to the audio function. An audio function is considered to be a ‘closed box’ that has very distinct and well defined interfaces to the outside world. Audio functions are addressed through their audio interfaces. Each audio function must have a single AudioControl interface and can have zero or more AudioStreaming and zero or more MIDIStreaming interfaces. The AudioControl (AC) interface is used to access the Audio Controls of the function whereas the AudioStreaming (AS) interfaces are used to transport audio streams into and out of the function. The MIDIStreaming (MS) interfaces can be used to transport MIDI data streams into and out of the audio function. The collection of the single AudioControl interface and the AudioStreaming and MIDIStreaming interfaces that belong to the same audio function is called the Audio Interface Collection (AIC). A device can have multiple Audio Interface Collections active at the same time. These Collections are used to control multiple independent audio functions located in the same composite device. An Audio Interface Collection is described through the standard USB Interface Association mechanism that expresses interface binding via the Interface Association Descriptor (IAD). Note All MIDI-related information is grouped in a separate document, Universal Serial Bus Device Class Definition for MIDI Devices that is considered part of this specification. The remainder of this document will therefore not mention MIDIStreaming interfaces and their specifics anymore. The following figure illustrates the concept Audio FunctionAudio-StreamingInterfaceINUSBAudio-StreamingInterfaceINAudio-StreamingInterfaceINAudio-StreamingInterfaceOUTAudio-StreamingInterfaceOUTAudio-StreamingInterfaceOUTAudioControl InterfaceAudio InterfaceCollectionAlternate Settings Figure 3-1 Audio Function Global View 18 Release 2.0 May 31, 2006 USB Device Class Definition for Audio Devices Release 2.0 May 31, 2006 19 All functionality pertaining to controlling parameters that directly influence audio perception (like volume) are located inside the central rectangle and are exclusively controlled through the AudioControl interface. Streaming aspects of the communication to or from the audio function are handled through separate AudioStreaming interfaces. The AudioStreaming interface is primarily used for transporting audio data between the audio function and the outside world. However, all control data that is related specifically to the streaming behavior is also conveyed through the AudioStreaming interface. In particular, all control data that is used to influence the decoder or encoder process that potentially resides between the actual streaming endpoint and the audio function (e.g. conversion from AC-3 encoded stream to 5.1 physical audio channels) is conveyed through the AudioStreaming interface. Note that in some cases an AudioStreaming interface is only used to perform controlling functions while no actual data is transported over the interface. A physical S/PDIF connection to the audio function is a typical example. Although the actual audio data is coming in from the outside world (not through the USB), it might be necessary to control some aspects of the S/PDIF connection. In that case, the S/PDIF connection is represented by an AudioStreaming interface so that it becomes addressable through USB. Also note that the connection between the AudioStreaming interfaces and the audio function is not ‘solid’. The reason for this is that when seen from the inside of the audio function, each audio stream entering or leaving the audio function is represented by a special object, called a Terminal (see further). The Terminal concept abstracts the actual AudioStreaming interface inside the audio function and provides a logical view on the connection rather than a physical view. This abstraction allows audio channels within the audio function to be treated as ‘logical’ audio channels that do not have physical characteristics associated with them anymore (analog vs. digital, format, sampling rate, bit resolution, etc.). 3.2 Audio Interface Collection (AIC) On USB, an audio function is completely defined by its interfaces. An audio function has one AudioControl interface and zero d into an Audio Interface e The Audio Function class and Subclasses can be further qualified by the Function Protocol code. The ion sion of this specification so that enumeration stantiated. or more AudioStreaming interfaces, groupe Collection. The standard USB Interface Association mechanism is used to describe the Audio Interface Collection i.e. to bind those interfaces together. Interface Association is expressed via the standard USB Interface Association Descriptor (IAD). Every Interface Association Descriptor has a FunctionClass, FunctionSubClass and FunctionProtocol field that together identify the function that is represented by thAssociation. The following paragraphs define these fields for the Audio Device Class. 3.3 Audio Function Class An Interface Association has a Function Class code assigned to it. This specification requires that the Function Class code be the same as the Audio Interface Class code. The Audio Function class code is assigned by this specification. For details, see Appendix A.1, “Audio Function Class Code”. 3.4 Audio Function Subclass The Audio Function class is divided into Function Subclasses. At this moment, the Function SubClass codeis not used and must be set to FUNCTION_SUBCLASS_UNDEFINED. The assigned codes can be found in A.2, “Audio Function Subclass Codes” of this specification. All other Subclass codes are unused and reserved by this specification for future use. 3.5 Audio Function Protocol Funct Protocol code is used to reflect the current versoftware can decide which driver versions need to be in The assigned Protocol codes can be found in Appendix A.3, “Audio Function Protocol Codes” of this specification. All other Protocol codes are unused and reserved by this specification for future use. USB Device Class Definition for Audio Devices Release 2.0 May 31, 2006 20 h USB belong to this class. t, f this class, the only requirement is that it exposes one in aming interfaces for consuming or ss code is assigned by the USB. For details, see Appendix A.4, “Audio Interface Class Code”. re part of a certain Interface • AudioStreaming Interface Subclass ion. the current version of this specification. . ion Category indicates the primary intended use for the audio function. The following . ne A device set up to record audio from audible sources. • Headset A device with at least one speaker and at least one microphone designed to be worn or held ck and voice input capabilities. o another converting audio data from one encoding format to another (e.g. th at least one microphone and at least one speaker that is d optical inputs and outputs for connection to other devices. 3.6 Audio Interface Class The Audio Interface class groups all functions that can interact with USB-compliant audio data streams. All functions that convert between analog and digital audio domains can be part of this class. In addition, those functions that transform USB-compliant audio data streams into other USB-compliant audio data streams can be part of this class. Even analog audio functions that are controlled throug In facor an audio function to be part of AudioControl interface. No further interaction with the function is mandatory, although most functionsthe audio interface class will support one or more optional AudioStre producing one or more isochronous audio data streams. The Audio Interface cla 3.7 Audio Interface Subclass The Audio Interface class is divided into Subclasses. All audio functions a Subclass. The following three Interface Subclasses are currently defined in this specification • AudioControl Interface Subclass • MIDIStreaming Interface Subclass The assigned codes can be found in Appendix A.5, “Audio Interface Subclass Codes” of this specificatAll other Subclass codes are unused and reserved by this specification for future use. 3.8 Audio Interface Protocol The Audio Interface class and Subclasses can be further qualified by the Interface Protocol code. The Interface Protocol code is used to reflect The assigned codes can be found in Appendix A.6, “Audio Interface Protocol Codes” of this specificationAll other Protocol codes are unused and reserved by this specification for future use. 3.9 Audio Function Category The Audio Funct Function Categories are currently defined in this specification • Desktop Speaker One or more speakers set up in a small environment to provide audio intended primarily for one person. • Home Theater Several speakers set up in a moderately sized environment to provide audio levels significantly louder than a Desktop Speaker setup and intended to be clearly heard by multiple people• Micropho by a user to provide personal audio playba• Telephone A Headset or handset type device that also connects to a telephone system, (e.g. POTs, PBX, VoIP) capable of making and receiving telephone calls. • Converter A device that allows conversion of audio from one electrical or optical format t electrical or optical format, and/or AC-3 to PCM, etc.). • Voice/Sound recorder A device set up wi designed to operate, at least some of the time, independently of the Host to record and store audible sources and play back its recorded content. • IO Box A device designed to deliver one or more, possibly different, electrical an 1 - 6 - 11 - 16 - 21 - 26 - 31 - 36 - 41 - 46 - 51 - 56 - 61 - 66 - 71 - 76 - 81 - 86 - 91 - 96 - 101 - 106 - 111 - 116 - 121 - 126 - 131 - 136 - 141 ここを編集
https://w.atwiki.jp/usb_audio/pages/17.html
原文：Audio Terminal Types 1.0(PDF) USB Device Class Definition for Terminal Types Release 1.0 March 18, 1998 i Universal Serial Bus Device Class Definition for Terminal Types Release 1.0 March 18, 1998 USB Device Class Definition for Terminal Types Release 1.0 March 18, 1998 ii Scope of This Release This document is the 1.0 release of this device class definition. Contributors Gal Ashour IBM Corporation Billy Brackenridge Microsoft Corporation Oren Tirosh Altec Lansing Craig Todd Dolby Laboratories Remy Zimmermann Logitech Geert Knapen Philips ITCL Interleuvenlaan 74-76 B-3001 Leuven-Heverlee BELGIUM Phone +32 16 390 734 Fax +32 16 390 600 E-mail Geert.Knapen(at)innet.be Revision History Revision Date Filename Author Description 0.1 Dec. 1, 96 Termt01.doc Oren Tirosh Initial version 0.2 Jan. 1, 97 Termt02.doc Geert Knapen Corrected typos. Restructured the divisions. 0.3 Mar. 1, 97 Termt03.doc Geert Knapen Adapted template and contents to correspond with core document. 0.9rc Apr. 1, 97 Termt09rc.doc Geert Knapen Minor style adjustments. Added Synthesizer Terminal type. 0.9 May 1, 97 Termt09.doc Geert Knapen No changes. 0.9CE Sep 1, 97 Termt09CE.doc Geert Knapen Copy-edited for publication on the web. 1.0RC Mar 1, 98 Termt10RC.doc Geert Knapen Cleaned up the formatting. 1.0 Mar 18, 98 Termt10.doc Geert Knapen Changed all references to 1.0 USB Device Class Definition for Terminal Types Release 1.0 March 18, 1998 iii Copyright © 1997, USB Implementers ForumAll rights reserved. INTELLECTUAL PROPERTY DISCLAIMER THIS SPECIFICATION IS PROVIDED “AS IS” WITH NO WARRANTIES WHATSOEVER INCLUDING ANY WARRANTY OF MERCHANTABILITY, FITNESS FOR ANY PARTICULAR PURPOSE, OR ANY WARRANTY OTHERWISE ARISING OUT OF ANY PROPOSAL, SPECIFICATION, OR SAMPLE. A LICENSE IS HEREBY GRANTED TO REPRODUCE AND DISTRIBUTE THIS SPECIFICATION FOR INTERNAL USE ONLY. NO OTHER LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY OTHER INTELLECTUAL PROPERTY RIGHTS IS GRANTED OR INTENDED HEREBY. AUTHORS OF THIS SPECIFICATION DISCLAIM ALL LIABILITY, INCLUDING LIABILITY FOR INFRINGEMENT OF PROPRIETARY RIGHTS, RELATING TO IMPLEMENTATION OF INFORMATION IN THIS SPECIFICATION. AUTHORS OF THIS SPECIFICATION ALSO DO NOT WARRANT OR REPRESENT THAT SUCH IMPLEMENTATION(S) WILL NOT INFRINGE SUCH RIGHTS. Dolby™, AC-3™, Pro Logic™ and Dolby Surround™ are trademarks of Dolby Laboratories, Inc. All other product names are trademarks, registered trademarks, or service marks of their respective owners. Please send comments via electronic mail to techsup(atusb.org) USB Device Class Definition for Terminal Types Release 1.0 March 18, 1998 iv Table of Contents Scope of This Release.........................................................................................................ii Contributors........................................................................................................................ii Revision History ..................................................................................................................ii Table of Contents ...............................................................................................................iv List of Tables .......................................................................................................................v 1 Introduction ..................................................................................................................6 1.1 Scope......................................................................................................................6 1.2 Related Documents .................................................................................................6 1.3 Terms and Abbreviations.........................................................................................6 2 Terminal Types.............................................................................................................7 2.1 USB Terminal Types................................................................................................7 2.2 Input Terminal Types ...............................................................................................7 2.3 Output Terminal Types ............................................................................................8 2.4 Bi-directional Terminal Types ..................................................................................8 2.5 Telephony Terminal Types ......................................................................................9 2.6 External Terminal Types..........................................................................................9 2.7 Embedded Function Terminal Types .....................................................................10 3 Adding New Terminal Types......................................................................................12 USB Device Class Definition for Terminal Types Release 1.0 March 18, 1998 v List of Tables Table 2-1 USB Terminal Types ..........................................................................................7 Table 2-2 Input Terminal Types.........................................................................................7 Table 2-3 Output Terminal Types......................................................................................8 Table 2-4 Bi-directional Terminal Types ...........................................................................9 Table 2-5 Telephony Terminal Types................................................................................9 Table 2-6 External Terminal Types..................................................................................10 Table 2-7 Embedded Terminal Types..............................................................................10 1 - 6 - 11 ここを編集