mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bernd Petrovitsch <bernd@firmix.at>
To: Kenneth Lavrsen <kenneth@lavrsen.dk>
Cc: Jesper Juhl <juhl-lkml@dif.dk>, Greg KH <greg@kroah.com>,
	linux-kernel@vger.kernel.org,
	linux-usb-devel@lists.sourceforge.net
Subject: Re: Summarizing the PWC driver questions/answers
Date: Sat, 28 Aug 2004 01:01:19 +0200	[thread overview]
Message-ID: <1093647676.17366.14.camel@gimli.at.home> (raw)
In-Reply-To: <6.1.2.0.2.20040827233253.01c36210@inet.uni2.dk>

On Sat, 2004-08-28 at 00:08, Kenneth Lavrsen wrote:
> >  I have boxes where I can't run the latest version
> >of AIX any more since the hardware is no longer supported, but you don't
> >see me ripping IBM's head off for that reason.

BTW Sun did similar things with Solaris somewhere aroung 2.6 IIRC.

> Ehhh????? No comment.

Why?

[...]
> Why not let the current driver be and then work on the alternative?
> Why is it so important that it is removed now?

Because the driver's maintainer wanted it.

> Linus indicated that since Nemosoft had asked for his driver to be removed 
> noone else could take the sources as they are and add them again. So any 
> altertive would be a start from scratch? Or did I misunderstand this?

Yes, anyone - including you - can take over the maintanance of the
GPL-part of driver. Even if the former maintainer does not like it.

> That can take years. So I cannot update my kernel for years?
> How many normal users knows even how to compile their own kernel?
> You guys on this list talk as if anyone knows how to write a kernel module. 
> I think most of you have lost contact with the real users.

No, they complain all around all the time. I don't think one can loose
contact eeven if he wishes.
The point is: This is GPL software - either you do something, or someone
else does something or nothing is done. Whining doesn't help that much
compared to writing code.

> >And why is it you expect open source developers to assist in supporting
> >binary only drivers?
> 
> I am just asking for you guys to not DESTROY what is already there without 
> an alternative.

It is not destroyed, it is only in another place. Find it and put it
back whereever you need it.

	Bernd
-- 
Firmix Software GmbH                   http://www.firmix.at/
mobil: +43 664 4416156                 fax: +43 1 7890849-55
          Embedded Linux Development and Services



  reply	other threads:[~2004-08-27 23:01 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-27 19:54 Kenneth Lavrsen
2004-08-27 20:14 ` [linux-usb-devel] " David Brownell
2004-08-27 20:22 ` David S. Miller
2004-08-27 20:30 ` David Ford
2004-08-27 21:26   ` Wouter Van Hemel
2004-08-27 22:07     ` [OT] " David Ford
2004-08-27 20:32 ` Zwane Mwaikambo
2004-08-27 21:25 ` Jesper Juhl
     [not found]   ` <Pine.LNX.4.61.0408272259450.2771@dragon.hygekrogen.localho st>
2004-08-27 22:08     ` Kenneth Lavrsen
2004-08-27 23:01       ` Bernd Petrovitsch [this message]
2004-08-27 23:13       ` [linux-usb-devel] " Oliver Neukum
2004-08-29 13:40         ` Alan Cox
2004-08-30  9:14           ` Craig Milo Rogers
2004-08-31  5:04           ` asterix the gual
2004-08-28  0:22       ` Paul Jakma
2004-08-28 15:55         ` [linux-usb-devel] " michel Xhaard
2004-08-30 12:04 ` Geert Uytterhoeven
  -- strict thread matches above, loose matches on Subject: below --
2004-08-28 21:07 linux
2004-08-28 22:06 ` Oliver Neukum
2004-08-27 16:26 Greg KH
2004-08-27 16:58 ` David Woodhouse
2004-08-27 18:26   ` Wouter Van Hemel
2004-08-27 19:05     ` Ian Romanick
2004-08-27 20:36       ` Wouter Van Hemel
2004-08-27 16:58 ` Prakash K. Cheemplavam
2004-08-27 17:54 ` Roman Zippel
2004-08-30 17:31 ` Brian Litzinger
2004-08-30 18:24   ` Jeff Kinz
2004-08-30 19:28   ` viro
2004-08-30 20:11   ` Kenneth Lavrsen

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=1093647676.17366.14.camel@gimli.at.home \
    --to=bernd@firmix.at \
    --cc=greg@kroah.com \
    --cc=juhl-lkml@dif.dk \
    --cc=kenneth@lavrsen.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    /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®