From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Developing a Linux driver using a USB sniffer
Date: Mon, 5 May 2014 06:10:31 -0700 [thread overview]
Message-ID: <20140505131031.GA3774@kroah.com> (raw)
In-Reply-To: <53677EC6.2070208@gmail.com>
On Mon, May 05, 2014 at 02:06:30PM +0200, Luca Ellero wrote:
> Hi all,
> can someone please tell me if it is legal to develop an USB driver
> analysing the USB protocol with a USB sniffer?
> Can this driver be made public under GPL?
Would you ask a doctor for legal advice? If not, why ask a programmer?
If you have legal questions, ask a lawyer in your country, they are the
only ones that can give you a definitive answer.
good luck,
greg k-h
next prev parent reply other threads:[~2014-05-05 13:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-05 12:06 Developing a Linux driver using a USB sniffer Luca Ellero
2014-05-05 12:50 ` Tovo Rabemanantsoa
2014-05-05 13:10 ` Greg KH [this message]
2014-05-05 20:39 ` Dave Hylands
2014-05-06 14:00 ` Luca Ellero
2014-05-06 15:31 ` Eric Fowler
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=20140505131031.GA3774@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).