From: Wayne.Brown@altec.com
To: pavel@suse.cz, linux-kernel@vger.kernel.org
Subject: Re: Fasttrak100 questions...
Date: Sun, 3 Dec 2000 10:41:20 -0600 [thread overview]
Message-ID: <862569AA.005C068D.00@smtpnotes.altec.com> (raw)
Where can this Lucent driver be found? The one I use with my Thinkpad is
version 5.68. It comes as a loadable module (ltmodem.o) with no serial.c, and I
havent gotten it to work with any kernel later than 2.2.14.
Pavel Machek <pavel@suse.cz> on 12/02/2000 10:50:35 AM
To: Alan Cox <alan@lxorguk.ukuu.org.uk>, "Dr. Kelsey Hudson"
<kernel@blackhole.compendium-tech.com>
cc: "Henning P. Schmiedehausen" <hps@tanstaafl.de>,
linux-kernel@vger.kernel.org (bcc: Wayne Brown/Corporate/Altec)
Subject: Re: Fasttrak100 questions...
Hi!
> > You are wrong: If you modify the kernel you have to make it available for
> > anyone who wishes to use it; that's also in the GPL. You can't add stuff
>
> No it isnt. Some people seem to think it is. You only have to provide a
> change if you give someone the binaries concerned. Some people also think
> that 'linking' clauses mean they can just direct the customer to do the link,
> that also would appear to be untrue in legal precedent - the law cares about
> the intent.
This is currently happening with lucent winmodem driver: there's
modified version of serial.c, and customers are asked to compile it
and (staticaly-)link it against proprietary code to get usable
driver. Is that okay or not?
Pavel
--
I'm pavel@ucw.cz. "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at discuss@linmodems.org
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-12-03 17:16 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-03 16:41 Wayne.Brown [this message]
2000-12-03 17:49 ` Fasttrak100 questions Pavel Machek
2000-12-03 18:45 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2000-11-24 22:46 James Lamanna
2000-11-25 1:35 ` Andre Hedrick
2000-11-25 12:10 ` Henning P. Schmiedehausen
2000-11-25 17:20 ` Andre Hedrick
2000-11-25 17:22 ` Andre Hedrick
2000-11-29 19:53 ` Dr. Kelsey Hudson
2000-11-29 20:08 ` Henning P . Schmiedehausen
2000-11-29 21:11 ` Andre Hedrick
2000-11-29 23:52 ` Jeff V. Merkey
2000-11-30 15:14 ` Christopher Friesen
2000-11-30 18:43 ` Jeff V. Merkey
2000-11-30 18:09 ` Christopher Friesen
2000-11-30 20:10 ` Jeff V. Merkey
2000-12-02 3:44 ` Peter Samuelson
2000-12-03 22:54 ` Pavel Machek
2000-12-05 4:10 ` Peter Samuelson
2000-11-29 20:42 ` Alan Cox
2000-11-29 21:05 ` Andre Hedrick
2000-11-29 21:10 ` James A Sutherland
2000-11-29 21:18 ` Alan Cox
2000-11-29 21:30 ` Andre Hedrick
2000-12-02 16:50 ` Pavel Machek
2000-12-02 17:18 ` Alan Cox
2000-12-02 23:46 ` Theodore Y. Ts'o
2000-12-03 1:21 ` Jeff V. Merkey
2000-12-03 1:31 ` Jeff V. Merkey
2000-12-03 3:42 ` Theodore Y. Ts'o
2000-12-03 5:11 ` Jeff V. Merkey
2000-12-05 7:07 ` Brian F. G. Bidulock
2000-12-05 8:25 ` Jeff V. Merkey
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=862569AA.005C068D.00@smtpnotes.altec.com \
--to=wayne.brown@altec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
/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