mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andi Kleen <ak@muc.de>
To: SashaK <sashak@smlink.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: GPL source code for Smart USB 56 modem (includes ALSA AC97 patch)
Date: 12 Sep 2004 10:30:39 +0200	[thread overview]
Date: Sun, 12 Sep 2004 10:30:39 +0200	[thread overview]
Message-ID: <20040912083039.GB87823@muc.de> (raw)
In-Reply-To: <20040911230753.1c1d73de@localhost>

On Sat, Sep 11, 2004 at 11:07:53PM +0300, SashaK wrote:
> On Sat, 11 Sep 2004 16:09:41 +0200
> Andi Kleen <ak@muc.de> wrote:
> 
> > SashaK <sashak@smlink.com> writes:
> > 
> > > You mean to GPL user-space program slmodemd?
> > > I think it is good idea, but unfortunately this code is not just my,
> > > and final decision was 'no'.
> > 
> > One way that would work is to make the binary parts of your driver run
> > in user space and let the kernel part just provide a kind of simple
> > sound card. 
> 
> It is done so - user space daemon (with binary part) interacts with ALSA
> drivers.

Ok, thanks for the correction. 

> 
> > The later should be much easier to free.
> 
> There was such approach, but seems it was wrong.

What's the problem exactly - your kernel part is still binary only? 

> 
> > The 64bit kernel can run 32bit programs without problems.
> 
> This should be possible (don't check yet). But the problem here was
> that AMD64 machines are usually based on non-Intel chipsets
> (VIA, NVidia), supports for those chipsets were added to ALSA just in
> last days. Now it may be tested with recent version of ALSA.

One small issue is that when you have custom ioctls there may 
be some need to add them to the compat layer, otherwise the user
space part cannot issue them. This could be even done in a separate 
module from your driver though.

-Andi

  reply	other threads:[~2004-09-12  8:30 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]
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
  -- 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=20040912083039.GB87823@muc.de \
    --to=ak@muc.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sashak@smlink.com \
    /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

all inboxes | Powered by JetHome®