Re: Humble request for an updated slamr driver for Ubuntu 9.04 ( 2.6.28-11-generic )

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Ahmed,

RE: suggested that each of slamr/slusb code could be split into two
further modules (one that is GPL
---------
Some history here is worth reporting.

The Smartlink driver once was unitary.  After someone with Mandrake
several years ago (forgot his name) suggested a split into the slamr
driver and non-driver slmodemd, maintainer Sasha Khapyorsky
enthusiastically adopted it. This also contributed to the current
service of slmodemd for non-Smartlink hardware, through
complementation of ALSA modem drivers.

In the support of Lucent/Agere/LSI winmodems with a digital signal
processing "DSP" chip, Alexei Chentsov did a similar split, with
consequence that upon loading of the driver, a /dev/pts/N is created ,
with complementation by a non-driver martian_modem helper.  I'm not
significantly competent in COMM or C code, but perhaps the martian
code at http://linmodems.technion.ac.il/packages/ltmodem/kernel-2.6/martian/
would provide some guide in further shiifting the port creation
capability from slamr into an Open Source component.

Among the winmodems various only the SmartLink code is to the best of
my knowledge capable of supporting multiple winmodems on the same host
PC, though I cannot recall whether this  also extends to the
non-Smartlink harder supported by  ALSA drivers plus slmodemd.

Some years ago there was some experimentation with the DSP chip
modems, to asses if multiple modems could be managed on one host PC.
This ultimate failed, because the CPU did not separate the data
streams for the different modems.  Also Agere staff informed us that
such sophistication had never been intended for the "consumer" ltmodem
code, and recommended hardware/controller chipset modems for such
multimodem services.

MarvS

On Sun, Apr 12, 2009 at 1:45 AM, أحمد المحمودي
<aelmahmoudy@xxxxxxxxxxxxxxxxxxxxx> wrote:
> On Sat, Apr 11, 2009 at 11:45:52PM -0500, Antonio Olivares wrote:
>> The code exists, although I am not sure whether it is appropriate or
>> not within GPL.  The device node gets created if the following is
>> placed in /etc/modprobe.d/modprobe.conf
>>
>>      Within /etc/modprobe.conf files:
>> /etc/modprobe.d/modprobe.conf:install slamr modprobe --ignore-install
>> ungrab-winmodem ;  modprobe --ignore-install slamr; test -e
>> /dev/slamr0 || (/bin/mknod -m 660 /dev/slamr0 c 242 0 2>/dev/null &&
>> chgrp uucp /dev/slamr0)
>>
>> That will create the device nodes and appropriate permissions to dialout.
> ---end quoted text---
>
>  That used to exist in the slmodem Debian package indeed, yet Ubuntu
>  developers removed it.
>
>  Yet this line only creates one device (which I think will be for just
>  1 modem), let's suppose that a machine got 2 modems, this
>  modprobe.conf line won't create the device for the 2nd modem. I think
>  there is a way that would create the appropriate device if a correct
>  udev rule (and probably some supporting code in the module) is made.
>
>  Yet maybe that won't work if the MODULE_LICENSE isn't GPL.
>
>  Which made me make some experiment a couple of weeks ago: I changed
>  the MODULE_LICENSE to GPL (Not Dual BSD/GPL), but GPL, and compiled
>  slmodem, and used the slamr device, I noticed that I got extra output
>  from udevadm when I did this, but the kernel freezed after that, so I
>  didn't bother to try again, since that won't be legal to distribute
>  anyways.
>
> --
>  ‎أحمد المحمودي (Ahmed El-Mahmoudy)
>  Digital design engineer
>  GPG KeyID: 0x9DCA0B27 (@ subkeys.pgp.net)
>  GPG Fingerprint: 087D 3767 8CAC 65B1 8F6C  156E D325 C3C8 9DCA 0B27
>


[Index of Archives]     [Linux Media Development]     [Asterisk]     [DCCP]     [Netdev]     [X.org]     [Xfree86]     [Fedora Women]     [Linux USB]

  Powered by Linux