alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: "Giovanni Maruzzelli" <gmaruzz.lists@gmail.com>
To: John Utz <john.utz@dmx.com>
Cc: alsa-devel@alsa-project.org,
	"Alexander E. Patrakov" <patrakov@gmail.com>
Subject: Re: No sound from usb on Motorola C350 cellphone
Date: Mon, 12 Nov 2007 19:49:20 +0100	[thread overview]
Message-ID: <7c5010d60711121049q3ed60354me3c7dd492163043a@mail.gmail.com> (raw)
In-Reply-To: <20071112103947.0e3afc4b@jutz-gnto64>

Johnu,

device string, and all the "usual" kind of detailed informations are
in the files contained by the compressed archive you can download at:
http://www.celliax.org/c350_usb_sound.tgz (lsusb -vv before and after,
stream0, etc etc).

maybe there is need for a quirk in snd_usb_audio ?

the problem is that the device appear to works, but do not captures or
plays samples.

On Nov 12, 2007 7:39 PM, John Utz <john.utz@dmx.com> wrote:
> Hi All;
>
> I think this is a totally fascinating thing and i hope it will be
> possible to make it work.....
>
> onto the specifics
>
> On Mon, 12 Nov 2007 19:14:06 +0500
> "Alexander E. Patrakov" <patrakov@gmail.com> wrote:
>
>
> > Giovanni Maruzzelli wrote:
> > > Needs more info, tests?
> >
> > If you can make the audio functionality work under Windows 2000 or XP
> > with the new (non-standard) driver, snoopy logs will be interesting.
> > Snoopy is available from http://www.wingmanteam.com/usbsnoopy/ or
> > (different version) http://sourceforge.net/projects/usbsnoop/
> >
>
> i am not staring at the USB code right now (it's on a different box),
> but i would think that one of the first things that you might need to
> uncover is the USB device string. It may be offered up as part of the
> device probe when it's attached (check in dmesg) or you may find it in
> a registry or .inf file on the windows file system after you install
> the drivers.
>
> if it's a class compliant device, then it may just work once alsa get's
> taught about it (dont hold me to that, i am not looking at code)
>
> however, as one of you alluded to, there may be an AT command that
> needs to get tickled to turn it on.
>
> the other annoying thing to consider is that it may actually be probe
> and connected, but you havent yet figured out how to turn up the
> volume :-( (yes, that happens)
>
> i'll be really curious about this, so please continue to share with
> the list....
>
> tnx!
>
> johnu
>
>

  reply	other threads:[~2007-11-12 18:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-12 13:28 No sound from usb on Motorola C350 cellphone Giovanni Maruzzelli
2007-11-12 13:34 ` Giovanni Maruzzelli
2007-11-12 13:44   ` Giovanni Maruzzelli
2007-11-12 13:50   ` Alexander E. Patrakov
     [not found]     ` <7c5010d60711120555r28363e3ax8bb1efa33209cc8c@mail.gmail.com>
2007-11-12 13:57       ` Giovanni Maruzzelli
2007-11-12 14:14         ` Alexander E. Patrakov
2007-11-12 18:39           ` John Utz
2007-11-12 18:49             ` Giovanni Maruzzelli [this message]
2007-11-12 22:29             ` Jesse Burt

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=7c5010d60711121049q3ed60354me3c7dd492163043a@mail.gmail.com \
    --to=gmaruzz.lists@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=john.utz@dmx.com \
    --cc=patrakov@gmail.com \
    /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).