public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: GPL source code for Smart USB 56 modem (includes ALSA AC97  patch)
Date: Thu, 9 Sep 2004 09:59:45 -0400	[thread overview]
Message-ID: <20040909135945.GC6690@thunk.org> (raw)
In-Reply-To: <20040909114747.GC30162@lkcl.net>

On Thu, Sep 09, 2004 at 12:47:47PM +0100, Luke Kenneth Casson Leighton wrote:
> dear linux kernel people,
> 
> i was staggered to find that swansmart (smlink.com) have a GPL
> driver for their smart usb 56k modem.
> 
> i trust that someone will download, check it, and if
> appropriate, incorporate it into the mainstream linux kernel.

It's mostly GPL'ed, but there are binary-only objects both in the
user-mode daemon (modem/dsplibs.o) and in the kernel driver
(drivers/amrlibs.o). 

The good news is that there a completely GPL'ed, source-complete
driver already in the 2.6 kernel, sound/pci/intel8x0m.c, which will
work with the user-mode daemon found in the smlink.com distribution.
This driver doesn't have all of the functionality of slamr driver
(which requires the propietary, binary-only object file) --- most
notably, ATM1 doesn't work when using the completely open-source
intl8x0m driver.  However, it does work just fine, and so as long as
you don't mind using the propietary object file in user-space, it's a
great solution.  I've been using the smlink daemon with both the
open-source and partial-propietary driver, and both work just fine on
my T40 laptop.

						- Ted

  parent reply	other threads:[~2004-09-09 16:36 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-09 11:47 GPL source code for Smart USB 56 modem (includes ALSA AC97 patch) 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 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-09-09 14:04 tvrtko.ursulin
2004-09-09 15:47 ` Luke Kenneth Casson Leighton
     [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-11 10:26 Mikael Pettersson
2004-09-11 13:48 ` SashaK
     [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
2004-09-11 18:50 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
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

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=20040909135945.GC6690@thunk.org \
    --to=tytso@mit.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkcl@lkcl.net \
    /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