mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Friesen <cfriesen@nortel.com>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Kyle Moffett <mrmacman_g4@mac.com>, Pavel Roskin <proski@gnu.org>,
	Joseph Pingenot <trelane@digitasaru.net>,
	Patrick Mochel <mochel@digitalimplant.org>,
	linux-kernel@vger.kernel.org, Greg Kroah-Hartman <greg@kroah.com>
Subject: Re: Please open sysfs symbols to proprietary modules
Date: Mon, 07 Feb 2005 10:05:43 -0600	[thread overview]
Message-ID: <420791D7.3020408@nortel.com> (raw)
In-Reply-To: <1107674683.3532.26.camel@krustophenia.net>

Lee Revell wrote:
> On Wed, 2005-02-02 at 21:50 -0500, Kyle Moffett wrote:
> 
>>It's not like somebody will have
>>some innate commercial advantage over you because they have your
>>driver source code.
> 
> 
> For a hardware vendor that's not a very compelling argument.  Especially
> compared to what their IP lawyers are telling them.
> 
> Got anything to back it up?

I have a friend who works for a company that does reverse-engineering of 
ICs.  Companies hire them to figure out how their competitor's chips 
work.  This is the real threat to hardware manufacturers, not publishing 
the chip specs.

Having driver code gives you the interface to the device.  That can be 
reverse-engineered from watching bus traces or disassembling binary 
drivers (which is how many linux drivers were originally written). 
Companies have these kinds of resources.

If you look at the big chip manufacturers (TI, Maxim, Analog Devices, 
etc.) they publish specs on everything.  It would be nice if others did 
the same.

Chris

  reply	other threads:[~2005-02-07 16:07 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-02 22:56 Pavel Roskin
2005-02-02 23:07 ` Greg KH
2005-02-02 23:23 ` Patrick Mochel
2005-02-02 23:29   ` Greg KH
2005-02-03  0:07     ` Pavel Roskin
2005-02-03  0:30       ` Greg KH
2005-02-03  4:54         ` Zan Lynx
2005-02-03  5:07           ` Greg KH
2005-02-03  8:59           ` Helge Hafting
2005-02-03 15:12           ` Alan Cox
2005-02-03 17:26             ` Theodore Ts'o
2005-02-03 13:47         ` linux-os
2005-02-04 16:05       ` David Woodhouse
2005-02-03  0:09 ` Joseph Pingenot
2005-02-03  1:13   ` Pavel Roskin
2005-02-03  2:50     ` Kyle Moffett
2005-02-03  3:17       ` Jon Masters
2005-02-06  7:24       ` Lee Revell
2005-02-07 16:05         ` Chris Friesen [this message]
2005-02-07 16:55           ` linux-os
2005-02-07 18:58             ` jerome lacoste
2005-02-07 19:35               ` linux-os
2005-02-07 16:55           ` Randy.Dunlap
2005-02-08  1:40             ` Horst von Brand
2005-02-03  4:57     ` Greg KH
2005-02-03  8:41 ` Arjan van de Ven
2005-02-03 21:00 ` Ben Greear
2005-02-04  9:20 ` Andrew Morton
2005-02-04  9:40   ` Arjan van de Ven
2005-02-15  1:41   ` Alan Cox
2005-02-03  4:08 Jonathan A. George
2005-02-03  5:07 ` Kyle Moffett
2005-02-03 12:30 Jonathan A. George
2005-02-04 15:16 ` Adrian Bunk
2005-02-17 23:13 parker
2005-02-18  3:32 ` Chris Friesen
2005-02-18 13:13 ` Arjan van de Ven

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=420791D7.3020408@nortel.com \
    --to=cfriesen@nortel.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mochel@digitalimplant.org \
    --cc=mrmacman_g4@mac.com \
    --cc=proski@gnu.org \
    --cc=rlrevell@joe-job.com \
    --cc=trelane@digitasaru.net \
    /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