From: Jiri Slaby <jirislaby@gmail.com>
To: Simon Morgan <sjmorgan@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Outdated Sangoma Drivers
Date: Sat, 06 Aug 2005 21:01:34 +0200 [thread overview]
Message-ID: <42F5090E.4070608@gmail.com> (raw)
In-Reply-To: <de63970c05080602496c2c8b11@mail.gmail.com>
Simon Morgan napsal(a):
>Hi,
>
>I couldn't help noticing that the Sangoma drivers distributed with the
>current kernel are slightly out of date and was wondering whether there
>was any reason for this?
>
>For example the kernel copy of sdla.c was last updated Mar 20, 2001 while
>the version contained in the drivers distributed on sangoma.com[1] was
>last updated Dec 15. 2003.
>
Hi,
this is letter from sangoma:
<cite>
the sdla.c is not Sangoma's file :) or if it is it should be erased.
The sdla.c
has not been used since 2001.
It is true that wanpipe drivers are not part of linux 2.6 kernel. We have
been so busy developing that there is no way the linux kernel could
keep up with the changes.
Bottom line we have to put a whole new wanpipe driver into the kernel
source, and that is a big task.
It is much easier for us to ask people to use our drivers from the web.
Once the wanpipe drivers stop changing so fast we will be able
to push the new release into the kernel. It doesn't make sense to do it
now
because if anyone wants to use wanpipe, that person would have to
get the latest drivers from the web!
</cite>
So what do you think we would do?
Add some lines to Kconfig with address of ftp sangoma?
Delete old version from the tree and wait for the new one?
next prev parent reply other threads:[~2005-08-06 19:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-06 9:49 Outdated Sangoma Drivers Simon Morgan
2005-08-06 10:43 ` Jesper Juhl
2005-08-06 12:19 ` Jiri Slaby
2005-08-06 19:01 ` Jiri Slaby [this message]
2005-08-06 19:38 ` Adrian Bunk
2005-08-06 20:17 ` Simon Morgan
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=42F5090E.4070608@gmail.com \
--to=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sjmorgan@gmail.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