mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: "Kilau, Scott" <Scott_Kilau@digi.com>
Cc: 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 18:23:32 +0200	[thread overview]
Message-ID: <20050412162332.GL4965@lug-owl.de> (raw)
In-Reply-To: <335DD0B75189FB428E5C32680089FB9F122152@mtk-sms-mail01.digi.com>

[-- Attachment #1: Type: text/plain, Size: 1958 bytes --]

On Tue, 2005-04-12 10:30:19 -0500, Kilau, Scott <Scott_Kilau@digi.com>
wrote in message <335DD0B75189FB428E5C32680089FB9F122152@mtk-sms-mail01.digi.com>:
> > There are people who just want the card supported.  There's no reason
> > to deny the driver to them.
> 
> Oh, it *is* supported, using our GPL'ed DGNC driver available on our
> ftp/web site.
> 
> This is not some argument of closed binaries versus open source
> binaries,
> As both the JSM and DGNC drivers are completely open source and GPL'ed.

So then please do *all* the work, not only the first half. Writing a
driver is a nice thing, but doesn't actually help anybody. Doing a
driver for eg. Linux means to *care* for it. That is, writing it is only
the very first step of a longer way. The next step is to supply patches
for review. Then you'll get some feedback and you're expected to work
the issues out. Then you can again submit patches -- and repeat this
until it's merged.

> This is about having the users of this card end up 
> getting a worse experience by using the JSM driver.

Then please work on getting your driver included into Linus' and Andrews
kernel sources. For some time, both drivers may co-exist, but once one
driver is *really* superior over the other one and there are *no* issues
left that force people to use the worse driver, that one will die out at
some time.

But please be prepared to be in a competitive position. You've won't get
your driver included by just telling once about it; you'll need to work
towards that goal, and probably monitor the driver to be useable in the
future.

MfG, JBG

-- 
Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481             _ O _
"Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg  _ _ O
 fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!   O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2005-04-12 16:26 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [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 21:46 Kilau, Scott
2005-04-12 22:28 ` Matt Mackall
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 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=20050412162332.GL4965@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=Scott_Kilau@digi.com \
    --cc=admin@list.net.ru \
    --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

Powered by JetHome