From: Lee Revell <rlrevell@joe-job.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Mateusz Berezecki <mateuszb@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Atheros wi-fi card drivers (?)
Date: Tue, 08 Mar 2005 15:13:59 -0500 [thread overview]
Message-ID: <1110312840.4600.4.camel@mindpipe> (raw)
In-Reply-To: <1110216394.3072.72.camel@localhost.localdomain>
On Mon, 2005-03-07 at 17:26 +0000, Alan Cox wrote:
> On Llu, 2005-03-07 at 15:45, Mateusz Berezecki wrote:
> > I've been doing some reverse engineering of madwifi HAL (Hardware
> > Abstraction Layer) object file recently.
> > I ended up with an almost complete source code for one chipset so far
> > and I was wondering if it is legal
> > to publish such source code on the internet?
>
> You should normally avoid doing this. Instead write a description of the
> chip registers and functions from the source you have produced and get
> someone else to write a chip driver from that. This avoids the risk of
> you being held to have "copied" their code - in the EU while you have
> rights to reverse engineer for interoperability in general if you copy
> their code that may still be a copyright violation.
>
Just to clarify, this also applies to the USA.
> There is other code in the kernel where reverse engineering was used.
>
Heh, that is putting it mildly. Linux driver support would be nowhere
without reverse engineering.
Lee
next prev parent reply other threads:[~2005-03-08 20:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-07 15:45 Atheros wi-fi card drivers (?) Mateusz Berezecki
2005-03-07 15:55 ` Raphael Jacquot
2005-03-08 11:25 ` Rene Rebe
2005-03-11 15:52 ` Bernd Petrovitsch
2005-03-07 17:26 ` Alan Cox
2005-03-08 20:13 ` Lee Revell [this message]
2005-03-07 17:36 ` Roland Dreier
2005-03-08 0:41 ` Christoph Hellwig
2005-03-08 6:08 ` Mateusz Berezecki
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=1110312840.4600.4.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mateuszb@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.