Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rene Herman <rene.herman@gmail.com>
To: Krzysztof Helt <krzysztof.h1@gmail.com>
Cc: Takashi Iwai <tiwai@suse.de>, alsa-devel <alsa-devel@alsa-project.org>
Subject: Re: [PATCH] Gallant SC-6000 driver (4th version)
Date: Thu, 06 Sep 2007 23:16:39 +0200	[thread overview]
Message-ID: <46E06E37.4090304@gmail.com> (raw)
In-Reply-To: <20070906231206.2ba8f939.krzysztof.h1@gmail.com>

On 09/06/2007 11:12 PM, Krzysztof Helt wrote:

> On Thu, 06 Sep 2007 12:12:42 +0200
> Rene Herman <rene.herman@gmail.com> wrote:
> 
>> On 09/06/2007 08:49 AM, Krzysztof Helt wrote:
>>
>>> Actually, the parport_pc driver is loaded by the udev by default, so the
>>> IRQ7 cannot be requested (I tested - IRQ7 request failed even if I had 
>>> not used the printer).
>> Not everybody uses udev. But more importantly, only if the hardware in 
>> question is discoverable. [...]
>>
>> And _then_ there's the bit about the ISA probing being a huge gaping race by 
>> design. There's really no defending that massive junk. All ISA autoprobing 
>> is bad engineering and should be ripped out and shot, period. It's broken 
>> both by design and implementation. The solution to making things nicer is 
>> not autoprobing but not using legacy ISA -- and basically noone is other 
>> than for entertainment purposes.
>>
> 
> I am quite sure we won't agree on this one. My reason (to keep autodection)
> is sheer laziness of giving two numbers. Even giving them does not make
> user free of problems how to avoid irqs and dmas with installed devices 
> but not visible in the /proc/interrupts file).

No, but then at least you aren't hiding the problem by promising the user to 
figure it all out automatically. And as said, /etc/modprobe.conf works...

> I would like to ask Takashi to decide on this issue. I will done as he says.

Oh, I've not much doubt he'll not mind it terribly. Still many drivers in 
sound/isa that do probing. Doesn't change that it's all counter-productive, 
broken junk though!

> Will this driver be included? I found a bug in probing - if something is wrong
> after the SB region is requested it won't be released. So the next version is
> needed to be done anyway (or a small patch later).

Still testing with snd-galaxy here and haven't really looked at integrating 
them yet. Will do, but I believe I saw some differences stand out already.

Rene.

  reply	other threads:[~2007-09-06 21:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-06  6:49 [PATCH] Gallant SC-6000 driver (4th version) Krzysztof Helt
2007-09-06 10:12 ` Rene Herman
2007-09-06 11:20   ` Rene Herman
2007-09-06 14:03     ` Krzysztof Helt
2007-09-06 15:18       ` Rene Herman
2007-09-07  8:34         ` full duplex AD1848 (was SC-6000 driver) Krzysztof Helt
2007-09-07 12:00           ` Rene Herman
2007-09-06 21:12   ` [PATCH] Gallant SC-6000 driver (4th version) Krzysztof Helt
2007-09-06 21:16     ` Rene Herman [this message]
2007-09-07 11:11       ` Takashi Iwai
2007-09-07 12:11         ` Rene Herman
  -- strict thread matches above, loose matches on Subject: below --
2007-09-05 20:25 Krzysztof Helt
2007-09-05 21:53 ` Rene Herman

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=46E06E37.4090304@gmail.com \
    --to=rene.herman@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=krzysztof.h1@gmail.com \
    --cc=tiwai@suse.de \
    /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