public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean-Francois Moine <moinejf@free.fr>
To: Kyle Baker <kyleabaker@gmail.com>
Cc: linux-media@vger.kernel.org
Subject: Re: Microsoft VX-1000 Microphone Drivers Crash in x86_64
Date: Sun, 11 Jul 2010 15:50:08 +0200	[thread overview]
Message-ID: <20100711155008.1f8f583f@tele> (raw)
In-Reply-To: <AANLkTikrKBpRSI6wVdMO3tSYPhm1CECFGeNiyJdzTa03@mail.gmail.com>

On Sat, 10 Jul 2010 22:30:58 -0400
Kyle Baker <kyleabaker@gmail.com> wrote:

> Is this change from 0x40 to 0x44 intended to fix the "bad interface"
> messages as well as the mic becoming disabled? Also, is a reboot after
> installing these drivers and changes required? I'm only curious
> because it takes so much longer to test changes.

The change from 0x40 to 0x44 is applied to the GPIO register of the
SN9C105 which is the bridge of the webcam. I was thinking that some
values of this register could break the audio input. It does not seem
so.

The "bad interface" messages are printed when the audio interfaces are
called by HAL for probe by the video driver. This is not an error.
I will remove this message in the next version.

Rebooting after installing a new version of a module is not needed. The
module may be removed from memory by 'rmmod'. In your case, when
updating sonixj, you just need to unplug the webcam, do
"rmmod gspca_sonixj" and replug the webcam.

-- 
Ken ar c'hentañ	|	      ** Breizh ha Linux atav! **
Jef		|		http://moinejf.free.fr/

  reply	other threads:[~2010-07-11 13:49 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-05 21:40 Microsoft VX-1000 Microphone Drivers Crash in x86_64 Kyle Baker
2010-07-07  5:44 ` Jean-Francois Moine
2010-07-07  6:57   ` Kyle Baker
2010-07-07  9:06     ` Jean-Francois Moine
2010-07-07 21:32       ` Kyle Baker
2010-07-08 10:14         ` Jean-Francois Moine
2010-07-08 22:54           ` Kyle Baker
2010-07-09 18:03             ` Jean-Francois Moine
2010-07-09 21:04               ` Kyle Baker
2010-07-10  9:36                 ` Jean-Francois Moine
2010-07-11  2:30                   ` Kyle Baker
2010-07-11 13:50                     ` Jean-Francois Moine [this message]
     [not found]                       ` <AANLkTinnNhJ-DoFWfU8U5NuTj_p48SefYzWWAxZqiUb-@mail.gmail.com>
2010-07-12  8:18                         ` Jean-Francois Moine
2010-07-12  9:28                           ` Kyle Baker
2010-07-12 11:21                             ` Jean-Francois Moine
2010-07-12 23:01                               ` Kyle Baker
2010-07-13 19:13                                 ` Jean-Francois Moine
2010-07-13 23:59                                   ` Kyle Baker
2010-07-14  3:01                                     ` Kyle Baker
     [not found]                                       ` <AANLkTikt6QOsrSB3XlgpjQm5wgtfFXlaiqyWsTFDH6PF@mail.gmail.com>
     [not found]                                         ` <20100714123145.01259845@tele>
2010-07-14 10:59                                           ` Kyle Baker

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=20100711155008.1f8f583f@tele \
    --to=moinejf@free.fr \
    --cc=kyleabaker@gmail.com \
    --cc=linux-media@vger.kernel.org \
    /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