public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: linux-usb-devel@lists.sourceforge.net
Cc: Michael Helmling <supermihi@web.de>, linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] New, yet unsupported USB-Ethernet adaptor
Date: Tue, 2 May 2006 22:29:47 -0700	[thread overview]
Message-ID: <200605022229.47937.david-b@pacbell.net> (raw)
In-Reply-To: <200605030706.56908.supermihi@web.de>

On Tuesday 02 May 2006 10:06 pm, Michael Helmling wrote:

> > Was it you who removed the copyrights from the "usbnet" driver and
> > changed the author assertion to one "M Subrahmanya Srihdar" ??
> > I'm guessing the latter; the www.moschip.com site implies that
> > its engineering HW is in India.
> 
> No, I did not change the code in any way, it is exactly the version they 
> mailed me.

That's what I strongly suspected.


> But I don't really understand what you are saying about the usbnet  
> module. They gave me the sourcecode for a yet not available kernel module 
> "mcs7830", not usbnet. Or did they just modify usbnet? I don't know enough 
> about such things to distinguish from both. 

They just hacked "usbnet".  There are huge chunks of code, and comments,
that are clearly identical.  At least half of the "moschip" driver.


> > Either way, blatant plagiarism and theft of copyright is unlikely
> > to get into upstream kernels.
> 
> I personally have the feeling that they didn't do this by purpose. They were 
> very willing to help me with the driver and don't seem to understand much of 
> kernel development. Anyway, if this IS a copyright violation, they should 
> really change it quickly.

"M Subrahmanya Srihdar" didn't "accidentally" copy the bulk of usbnet, remove all
the attributions, and replace them ... not possible.  There were certainly a few
chip-specific additions of course, right where "usbnet" expects them, but the
core driver is obviously all "usbnet" code.

- Dave


  reply	other threads:[~2006-05-03  5:29 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-02 18:02 New, yet unsupported USB-Ethernet adaptor Michael Helmling
2006-05-02 19:13 ` Ioan Ionita
2006-05-02 20:40 ` Ioan Ionita
2006-05-02 21:03   ` Michael Helmling
     [not found]     ` <d9def9db0605050554m7b1e093di85782c1b09ca2636@mail.gmail.com>
2006-05-06 21:05       ` Michael Helmling
2006-05-02 21:25   ` Oliver Neukum
2006-05-02 22:09 ` [linux-usb-devel] " David Brownell
2006-05-03  5:06   ` Michael Helmling
2006-05-03  5:29     ` David Brownell [this message]
2006-05-03 13:28       ` Michael Helmling
2006-05-03 14:44         ` David Hollis
2006-05-03 15:31           ` Andrey Panin
2006-05-03 18:14             ` Michael Helmling
2006-05-03 18:33               ` Pavel Machek
2006-05-03 19:10           ` David Brownell
2006-05-03 19:23             ` David Brownell
2006-05-03 18:31   ` Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2006-05-06 23:23 linux
2006-05-08 15:51 ` Markus Rechberger

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=200605022229.47937.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=supermihi@web.de \
    /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