mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@fenrus.demon.nl>
To: Ulrich Weigand <Ulrich.Weigand@de.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: lcs ethernet driver source
Date: Thu, 30 Aug 2001 21:10:52 +0100	[thread overview]
Message-ID: <20010830211052.A21173@fenrus.demon.nl> (raw)
In-Reply-To: <OF598D8FCF.4FFE0C4C-ONC1256AB8.004CFE69@de.ibm.com>
In-Reply-To: <OF598D8FCF.4FFE0C4C-ONC1256AB8.004CFE69@de.ibm.com>

Ulrich Weigand <Ulrich.Weigand@de.ibm.com> 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.

I actually believed that IBM took Open Source and the community seriously.
Not releasing key parts of the S/390 architecture port make me very 
disappointed in IBM given the very massive and public claims of support.

It makes all the fuss IBM is making about how great Linux is look, well, 
fake. I know that large parts of IBM actually do take Open Source seriously 
but it's regrettable that an influential part of the S/390 division doesn't.

> Well, you're right that without network connection, there's not much
> useful you can do.  However [.. snip ..] you can also use a CTC or IUCV
> network interface. Especially in a virtual machine, you can simply define
> a virtual CTC or IUCV connection and access your network via those
> devices.

The drivers you mention suffer a severe performance hit and are also, as I
understand them, nothing more than a sort of pipe to a proprietary driver on
the other side of the VM barrier; this is actually worse as the VM for S/390
is rather expensive. So I have the choice between not being able to
recompile the kernel while using the binary only module, and paying a lot of
money for a piece of software that isn't as fast as the direct drivers. 

This makes dwmw2@infradead.org's assertion -- that the S/390 code in the
current kernel is actually useless -- be a very valid point. Imagine Linux
for the x86 architecture had PPP as it's only open source network driver.
Wouldn't that limit its acceptance and utility ? IBM customers for S/390
might feel the same way; it will help IBM and the customers a lot if such
essential drivers were Open Source. Creative ideas by users might leverage
the S/390 platform into areas IBM didn't think of before; having all basic
parts open sourced is essential for that.

Now it's not all bad. I'm not trying to paint IBM as the corporate bad guy.
Most of IBM is doing a lot of great work for Linux and I hope that the small
part of IBM that seems to be blocking these drivers sees the light soon. If
there is anything I can do to help expedite that, just let me know.

Greetings,
   Arjan van de Ven



  parent reply	other threads:[~2001-08-30 20:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-08-30 17:20 Ulrich Weigand
2001-08-30 16:58 Ulrich Weigand
2001-09-04  7:22 ` Florian Weimer
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=20010830211052.A21173@fenrus.demon.nl \
    --to=arjan@fenrus.demon.nl \
    --cc=Ulrich.Weigand@de.ibm.com \
    --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

all inboxes | Powered by JetHome®