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 23:20:55 +0300	[thread overview]
Message-ID: <20040918232055.00cb25b0@localhost> (raw)
In-Reply-To: <MPG.1bb665cd5b40a4ed9896f1@news.gmane.org>

On Sat, 18 Sep 2004 16:35:32 +0200
Giuseppe Bilotta <bilotta78@hotpop.com> wrote:

> Ok, I found the reason of the latter failure: in 2.6.7 I have 
> ISA-PnP enabled (not in 2.6.5) and this loads the parport 
> driver before the sound driver. parport steals the IRQ.
> 
> Module loading order is important: if I load the i8x0 sound 
> modules first, the messages are more or less the same as the 
> ones in 2.6.5 (including the "MC'97 1 converters and GPIO not 
> ready" message), and then parport accepts IRQ 7 to be taken by 
> resorting to polled operation:
> 
> > parport: PnPBIOS parport detected.
> > parport0: PC-style at 0x378 (0x778), irq 7, dma 1 [PCSPP,TRISTATE,COMPAT,ECP,DMA]
> > parport0: irq 7 in use, resorting to polled operation

I don't know really, but suppose that parport does not accept irq sharing.

> I will. Do you have any idea on the "not ready" issue?

This one is more interesting, probably special patch is necessary for conexant codec, let's see.

Please report bug to alsa and attach there output of 'lspci -vv' and tar of '/proc/asound' directory (or send to me).

Let's detach from linux-kernel list - things become pure-ALSA related.

Thanks,
Sasha.


  reply	other threads:[~2004-09-18 19:18 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
2004-09-18 14:35               ` Giuseppe Bilotta
2004-09-18 20:20                 ` Sasha Khapyorsky [this message]
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=20040918232055.00cb25b0@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