9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Sape Mullender <sape@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] VT6306 chip is for OHCI or UHCI?
Date: Tue, 24 Aug 2004 21:02:11 -0400	[thread overview]
Message-ID: <5dd41f06b48bb3708a5fdb2068994cc3@plan9.bell-labs.com> (raw)
In-Reply-To: <f8c21c55e1bf6d77a7d0b0d7c77fb5fd@granite.cias.osakafu-u.ac.jp>

> Thanks Sape for your kind comment.

Well, I'm glad there are people out there helping with Plan 9.  Thank YOU.

> This time, my case is at now, however, related to the number of
> channels, 8 (7.1) for this case, but hard coded as 2 in the source.
> After solving this, I may touch the problem you encountered.

Yep, in theory you can have mutiple input and multiple output audio streams.
I never went there; it's hard enough as it is.  FIguring out from the descriptors how
a device is configured is pure AI.  (proof below in what you just discovered :-)

> By the way, I learned somewhat so far:
>
>>desc 1.0 [12] 0x24: 1.1: Audio Input Terminal Descriptor
>>	bTerminalId 4, wTerminalType 0x201 (<unnamed>), bAssocTerminal >0 bNrChannels 2, wChannelConfig 3, iChannelNames 0 iTerminal 0
>>Device can record from <unnamed>
>
> This 0x201 must be microphone.

Very possible.  I'll look in the standards docs tomorrow to see if I can find what
0x201 and 0x605 mean (probably they're undefined -- I must have typed the names
in for the ones that were defined).

>>desc 1.0 [12] 0x24: 1.1: Audio Input Terminal Descriptor
>>	bTerminalId 5, wTerminalType 0x605 (<unnamed>), bAssocTerminal >0 bNrChannels 2, wChannelConfig 3, iChannelNames 0 iTerminal 0
>>Device can record from <unnamed>
>
> This 0x605 may be S/PDIF...  This device has S/PDIF input and output for
> light connectors.   Unfortunately, this device has no CD input connector,
> which may make me to forget internal DVD drive of the desk top?

Your device also has a mixer (if I remember a previous message correctly)
This may take a number of inputs or outputs and connect them together.

	Sape



  reply	other threads:[~2004-08-25  1:02 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-23  7:56 Kenji Okamoto
2004-08-23 15:00 ` Sape Mullender
2004-08-24  0:57   ` Kenji Okamoto
2004-08-24  3:13     ` Kenji Okamoto
2004-08-24 14:07     ` Sape Mullender
2004-08-25  0:23       ` Kenji Okamoto
2004-08-25  1:02         ` Sape Mullender [this message]
2004-08-25  1:27       ` Kenji Okamoto
2004-08-25  2:00       ` Kenji Okamoto
2004-08-25  3:06         ` Sape Mullender
2004-08-24  6:53   ` Kenji Okamoto
2004-08-24  7:17     ` Kenji Okamoto
2004-08-25  4:44     ` Kenji Okamoto
2004-09-01  6:06 ` Kenji Okamoto
2004-09-01  8:58   ` Kenji Okamoto
2004-09-02  8:21     ` Kenji Okamoto
2004-09-09  8:00     ` Kenji Okamoto
2004-09-09  8:15       ` Kenji Okamoto
2004-09-09  9:06       ` Kenji Okamoto
2004-09-09  9:48         ` Kenji Okamoto
2004-09-10  3:03           ` Kenji Okamoto
2004-09-10 10:36             ` Bruce Ellis
2004-08-24  3:13 Kenji Okamoto

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5dd41f06b48bb3708a5fdb2068994cc3@plan9.bell-labs.com \
    --to=sape@plan9.bell-labs.com \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).