From: "Ulrich Weigand" <Ulrich.Weigand@de.ibm.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: arjan@fenrus.demon.nl (Arjan van de Ven), linux-kernel@vger.kernel.org
Subject: Re: lcs ethernet driver source
Date: Thu, 30 Aug 2001 19:20:04 +0200 [thread overview]
Message-ID: <OFA16538B8.61628554-ONC1256AB8.005D7C15@de.ibm.com> (raw)
Alan Cox wrote:
>> Sorry, at this point we are not allowed to publish the source code of
the
>> lcs and qeth drivers (due to the use of confidential hardware interface
>> specifications). We make those modules available only in binary form
>> on our developerWorks web site.
>
>Is there any plan to change this ?
This is not something we (the Linux for S/390 development team) can decide;
it's up to the hardware groups that 'own' the LCS / QDIO specifications
whether they allow to make these public. As I said, at this point, we
are not allowed to open the specs; while it is conceivable that this might
change in the future, I'm not aware of any specific plan.
(Please note that I'm in no way speaking for IBM here; that's just my
personal opinion.)
Mit freundlichen Gruessen / Best Regards
Ulrich Weigand
--
Dr. Ulrich Weigand
Linux for S/390 Design & Development
IBM Deutschland Entwicklung GmbH, Schoenaicher Str. 220, 71032 Boeblingen
Phone: +49-7031/16-3727 --- Email: Ulrich.Weigand@de.ibm.com
next reply other threads:[~2001-08-30 17:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-30 17:20 Ulrich Weigand [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-08-30 16:58 lcs ethernet driver source Ulrich Weigand
2001-09-04 7:22 ` Florian Weimer
2001-08-30 14:07 Ulrich Weigand
2001-08-30 15:49 ` Alan Cox
2001-08-30 16:23 ` David Woodhouse
2001-08-30 18:03 ` John Alvord
2001-08-30 16:04 ` Richard B. Johnson
2001-08-30 20:10 ` Arjan van de Ven
2001-08-29 21:08 Arjan van de Ven
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=OFA16538B8.61628554-ONC1256AB8.005D7C15@de.ibm.com \
--to=ulrich.weigand@de.ibm.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjan@fenrus.demon.nl \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).