GPL source code for Smart USB 56 modem (includes ALSA AC97 patch)
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 11 lines · SashaK
Quoted 4 lines · On Sat, 11 Sep 2004 12:26:00 +0200 (MEST) Mikael Pettersson <[email protected]>…
I hope you succeed with open-sourcing all of slmodem's driver code. My Targa Athlon64 laptop has the AMR thingy and the 32-bit x86 binary only slmodem driver prevents me from using the modem while running a 64-bit kernel.
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. The later should be much easier to free.
Modern CPUs are usually fast enough that the additional latency caused by this doesn't matter.
The 64bit kernel can run 32bit programs without problems.
-Andi
Quoted 9 lines · On Sat, 11 Sep 2004 16:09:41 +0200 Andi Kleen <[email protected]> wrote:
Quoted 3 lines · SashaK
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.
Quoted 1 line
The later should be much easier to free.
There was such approach, but seems it was wrong.
Quoted 1 line
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.
Sasha.
Quoted 9 lines · SashaK
Quoted 6 lines · On Sat, 11 Sep 2004 16:09:41 +0200 Andi Kleen <[email protected]> wrote:
Quoted 3 lines · SashaK
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'.
Quoted 6 lines
Quoted 3 lines
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.
Quoted 4 lines
Quoted 2 lines
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?
Quoted 7 lines
Quoted 2 lines
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
Quoted 5 lines · On 12 Sep 2004 10:30:39 +0200 Andi Kleen <[email protected]> wrote:
Quoted 3 lines
Quoted 1 line
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?
Current binary kernel part (slamr) is not a problem - it may be removed, then ALSA drivers will be finished. But user-space program still have binary code and there is no replacement.
Quoted 8 lines
Quoted 7 lines
Quoted 2 lines
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.
Quoted 4 lines
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.
Thanks for explanations.
Sasha.