From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Subject: Re: Re: MTP-AV problems (Re: intel8x0 sequencer & MTP-AV) - success Date: Mon, 17 Feb 2003 11:56:57 +0100 Sender: alsa-devel-admin@lists.sourceforge.net Message-ID: References: <1044258789.30428.61.camel@littlewolf2.littlewolf> <1044273602.2013.6.camel@littlewolf2.littlewolf> <1045193186.10268.392.camel@littlewolf2.littlewolf> <1045389509.6765.21.camel@littlewolf2.littlewolf> Mime-Version: 1.0 (generated by SEMI 1.14.4 - "Hosorogi") Content-Type: text/plain; charset=US-ASCII Return-path: In-Reply-To: <1045389509.6765.21.camel@littlewolf2.littlewolf> Errors-To: alsa-devel-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: To: Allan Klinbail Cc: Alsa-dev List-Id: alsa-devel@alsa-project.org At 16 Feb 2003 20:58:23 +1100, Allan Klinbail wrote: > > One glitch I noticed was that the driver seemed to send the note > information to all ports when the sequence I had only sent to one of the > MTPAV ports... When I assigned a second to a different port it began > behaving correctly. i'm not sure whether the driver bug or what else. i guess the hardware port is initialized to 0 (or it IS as default), which corresponds to the broadcast. this may happen even if a message "F5 00" is sent by an application. so, we'll need to trace all F5 xx messages. does this broadcast behavior appear at the first start only? Takashi ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf