From alsa-devel-owner@alsa.jcu.cz  Mon Mar  1 01:48:22 1999
Received: from cyphyn.219.org (nwhn-sh16-port210.snet.net [204.60.50.210])
	by marvin.jcu.cz (8.9.1a/8.9.1) with ESMTP id BAA23841
	for <alsa-devel@alsa.jcu.cz>; Mon, 1 Mar 1999 01:47:52 +0100
Received: from localhost (ffloberg@localhost)
          by cyphyn.219.org (8.8.4/8.8.4) with ESMTP
	  id TAA27254 for <alsa-devel@alsa.jcu.cz>; Sun, 28 Feb 1999 19:47:30 -0500
Date: Sun, 28 Feb 1999 19:47:29 -0500 (EST)
From: Fred Floberg <ffloberg@snet.net>
To: alsa-devel@alsa.jcu.cz
Subject: Re: (SB Live) Free drivers or not? (fwd) 
In-Reply-To: <m10H6fN-000sLNC@lbscissors.kek.jp>
Message-ID: <Pine.LNX.4.05.9902281912590.27000-100000@cyphyn.219.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: alsa-devel@alsa.jcu.cz
Sender: alsa-devel-owner@alsa.jcu.cz
Precedence: list




On Sun, 28 Feb 1999 sharkey@ale.physics.sunysb.edu wrote:
[snip]
> But attempting to enforce this legally may not be the best course of action
> anyway.  I think its more important to educate ALSA users about the limitations
> of binary modules.  Linus has made his feelings about binary modules clear.
> He does not forbid them, but he won't lift a finger to support them.  If he
> wants to change the kernel in a way that breaks a binary module, he does
> so without blinking.
> 
> If Jaroslav wishes to adopt a similar policy, I think this would be the most
> reasonable solution.  Make it clear to all parties that, if Creative Balls*
> were to release a binary driver for ALSA 0.3-pre4, that this module may not
> work with 0.3-pre5.

These were my thoughts as well when I read the first post in this thread.
While Zippy's Soundcards Inc. may release a binary only driver for
their ScreechMaster 2000 soundcard there is no reason on earth why
Jaroslav would have to support it. He would be completely free to ignore
the existance of that binary only driver (and I would encourage him to do so).

Zippy Inc. will soon find it quite a chore to constantly re-release their
binary driver with every kernel change or change in ALSA, and would hopefully
see the error of their ways and adopt the practice lead by Trident Microsystems.

And if Zippy Inc. doesn't, well, screw them.

The biggest problem that I see is in educating the Linux user base, as Eric
mentions, in ALSA's stance on the matter. If Zippy Inc does release a binary
driver which fails to load or operate properly, then the alsa lists will no
doubt get quite a few "bug reports" from those who don't understand the issues
involved in kernel module version/compatability.

By then again, getting _everyone_ to RTFM has always been challenge. :-)


Fred

I have no knowledge of any real "Zippy Inc." or "ScreechMaster 2000" or for that
matter, any proprietary "Fingernails-on-a-Blackboard" capability.



