public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matt Mackall <mpm@selenic.com>
To: "Kilau, Scott" <Scott_Kilau@digi.com>
Cc: Greg KH <greg@kroah.com>, Christoph Hellwig <hch@infradead.org>,
	Ihalainen Nickolay <ihanic@dev.ehouse.ru>,
	admin@list.net.ru, linux-kernel@vger.kernel.org,
	Wen Xiong <wendyx@us.ibm.com>
Subject: Re: Digi Neo 8: linux-2.6.12_r2  jsm driver
Date: Tue, 12 Apr 2005 15:28:10 -0700	[thread overview]
Message-ID: <20050412222810.GA3174@waste.org> (raw)
In-Reply-To: <335DD0B75189FB428E5C32680089FB9F122164@mtk-sms-mail01.digi.com>

On Tue, Apr 12, 2005 at 04:46:10PM -0500, Kilau, Scott wrote:
> Hi Matt,
> 
> The ball is in my court, because my wishes as a copyright holder are not
> being honored.
>
> Which is the right of Christoph because of the GPL, but it sure doesn't
> help the end
> users of said product.
> Your claim that you are trying to "help" end users is bogus and just
> plain wrong.

Your end users do not benefit from drivers that are not well
integrated with the kernel. If a user has to jump through hoops to
make their hardware work (including downloading extra drivers, etc.),
that is not a benefit. Case in point: the patch in question _came from
an end user_.

We've now got 12 years experience in the headaches of out of tree
drivers (binary or not) as users, developers, and distributors, and
we're sick of it. We're not supporting that approach any more, they
don't exist as far as we're concerned until they're candidates for
merger. Your hardware is no exception.

> > As such, we make very little allowance
> > for their concerns, especially when they stand in
> > the way of improving things that _are_ in the kernel.
> 
> How is shipping a stripped down version of the driver, by yanking things
> our customers want, improving the "things that are in the kernel"?

End users do not benefit from bad interfaces. This may seem in
conflict with the above, but it's not. One of the main benefits of
kernel integration is that the trouble spots get sorted out and the
interfaces get cleaned up. This is good for everyone. Feel free to
resubmit those features when they're done right.

This is what your customers want, whether they know it yet or not.
Anything else is a stopgap.

> When the user installs my driver with all the extra features that our
> customers
> really want, I will simply check to see if jsm.ko exists, and ask the
> user if I
> can blow away the jsm.ko module.

And the rest of us make a note to not get Digi hardware because we're
sick of these out of tree drivers and the unspeakable hacks they
generally contain in the name of special features.

-- 
Mathematics is the supreme nostalgia of our time.

  reply	other threads:[~2005-04-12 22:34 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-12 21:46 Digi Neo 8: linux-2.6.12_r2 jsm driver Kilau, Scott
2005-04-12 22:28 ` Matt Mackall [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-04-13 14:25 Kilau, Scott
     [not found] <3SAEx-7Yo-9@gated-at.bofh.it>
2005-04-12 23:21 ` Bodo Eggert <harvested.in.lkml@posting.7eggert.dyndns.org>
2005-04-13  7:27   ` Christoph Hellwig
2005-04-12 20:21 Kilau, Scott
2005-04-12 21:32 ` Matt Mackall
2005-04-12 21:42 ` Greg KH
2005-04-12 20:01 Kilau, Scott
2005-04-12 16:54 Kilau, Scott
2005-04-12 17:30 ` Greg KH
2005-04-12 16:42 Kilau, Scott
2005-04-12 18:48 ` Jan-Benedict Glaw
2005-04-12 15:55 Kilau, Scott
2005-04-12 15:30 Kilau, Scott
2005-04-12 15:32 ` Christoph Hellwig
2005-04-13  3:27   ` Ricky Beam
2005-04-13  7:26     ` Christoph Hellwig
2005-04-12 16:16 ` Greg KH
2005-04-12 16:23 ` Jan-Benedict Glaw
2005-04-12 14:55 Kilau, Scott
2005-04-12 15:13 ` Christoph Hellwig
2005-04-12 14:02 Kilau, Scott
2005-04-12 14:44 ` Christoph Hellwig
2005-04-12 12:13 Ihalainen Nickolay
2005-04-12 14:44 ` Christoph Hellwig
2005-04-12 15:38   ` Ihalainen Nickolay

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=20050412222810.GA3174@waste.org \
    --to=mpm@selenic.com \
    --cc=Scott_Kilau@digi.com \
    --cc=admin@list.net.ru \
    --cc=greg@kroah.com \
    --cc=hch@infradead.org \
    --cc=ihanic@dev.ehouse.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wendyx@us.ibm.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