public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sasha Khapyorsky <sashak@smlink.com>
To: Giuseppe Bilotta <bilotta78@hotpop.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: GPL source code for Smart USB 56 modem (includes ALSA AC97     patch)
Date: Sat, 18 Sep 2004 14:29:00 +0300	[thread overview]
Message-ID: <20040918142900.06a9ff96@localhost> (raw)
In-Reply-To: <MPG.1bb4d933f584efee9896f0@news.gmane.org>

On Fri, 17 Sep 2004 12:22:05 +0200
Giuseppe Bilotta <bilotta78@hotpop.com> wrote:

> That's it:
> 
> > 0000:00:1f.6 Modem: Intel Corp. 82801CA/CAM AC'97 Modem Controller (rev 02) 

This is on-board controller.

> OTOH, ALSA in 2.6.5 doesn't like the modem controller:
> 
> > PCI: Setting latency timer of device 0000:00:1f.5 to 64
> > MC'97 1 converters and GPIO not ready (0xff00)
> > intel8x0_measure_ac97_clock: measured 52287 usecs
> > intel8x0: clocking to 48000
> > PCI: Setting latency timer of device 0000:00:1f.6 to 64
> > MC'97 1 converters and GPIO not ready (0xff00)
> 
> and 2.6.7 totally fails on both the audio and modem controller
> 
> > unable to grab IRQ 7
> > Intel ICH: probe of 0000:00:1f.5 failed with error -16
> > unable to grab IRQ 7
> > Intel ICH Modem: probe of 0000:00:1f.6 failed with error -16 

Not sure that last one is ALSA related. As noted in mesg 'request_irq' fails.

> I will try one of the 2.6.9 rcs one of these days and see if I 
> can get things to work.

If not please report a problem here https://bugtrack.alsa-project.org/alsa-bug/,
Or let me know.

Sasha.

  reply	other threads:[~2004-09-18 10:26 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-11 18:50 GPL source code for Smart USB 56 modem (includes ALSA AC97 patch) Mikael Pettersson
2004-09-11 22:11 ` SashaK
2004-09-13 20:26   ` David Lloyd
2004-09-14 13:19     ` Mario R. Carro
2004-09-14 14:59     ` Sasha Khapyorsky
2004-09-14 21:04       ` Giuseppe Bilotta
2004-09-15  0:58         ` Sasha Khapyorsky
2004-09-17 10:22           ` Giuseppe Bilotta
2004-09-18 11:29             ` Sasha Khapyorsky [this message]
2004-09-18 14:35               ` Giuseppe Bilotta
2004-09-18 20:20                 ` Sasha Khapyorsky
2004-09-20 20:23                   ` Giuseppe Bilotta
2004-09-21 16:55   ` David Woodhouse
2004-09-21 20:09     ` David Lloyd
2004-09-22  8:19       ` David Woodhouse
2004-09-22 19:07         ` David Lloyd
2004-09-22  1:08     ` Sasha Khapyorsky
     [not found] <2DdiX-6ye-17@gated-at.bofh.it>
     [not found] ` <2Dfup-7Zv-9@gated-at.bofh.it>
2004-09-11 14:09   ` Andi Kleen
2004-09-11 20:07     ` SashaK
2004-09-12  8:30       ` Andi Kleen
2004-09-12 13:11         ` Sasha Khapyorsky
  -- strict thread matches above, loose matches on Subject: below --
2004-09-11 10:26 Mikael Pettersson
2004-09-11 13:48 ` SashaK
     [not found] <2CvrA-Fv-11@gated-at.bofh.it>
     [not found] ` <2CAhw-4dR-3@gated-at.bofh.it>
2004-09-10 16:51   ` SashaK
2004-09-09 14:04 tvrtko.ursulin
2004-09-09 15:47 ` Luke Kenneth Casson Leighton
2004-09-09 11:47 Luke Kenneth Casson Leighton
2004-09-09 13:25 ` Ian Campbell
2004-09-09 13:46 ` Erik Mouw
2004-09-09 14:46   ` Luke Kenneth Casson Leighton
2004-09-09 13:59 ` Theodore Ts'o

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=20040918142900.06a9ff96@localhost \
    --to=sashak@smlink.com \
    --cc=bilotta78@hotpop.com \
    --cc=linux-kernel@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