public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Linus Torvalds <torvalds@osdl.org>,
	LKML <linux-kernel@vger.kernel.org>, Ian Molton <spyro@f2s.com>,
	Richard Purdie <rpurdie@rpsys.net>
Subject: Re: [PATCH][MMC] Secure Digital (SD) support
Date: Sat, 05 Mar 2005 14:46:47 +0100	[thread overview]
Message-ID: <4229B847.5050301@drzeus.cx> (raw)
In-Reply-To: <20050305124420.A342@flint.arm.linux.org.uk>

Russell King wrote:

>On Sat, Mar 05, 2005 at 01:23:16PM +0100, Pierre Ossman wrote:
>  
>
>>I can make a new patch or you can just undo that line once you've 
>>applied the current one.
>>    
>>
>
>I'd rather not just apply this patch - there's rather a lot there to
>just apply on top of what's already merged.
>
>Is there any chance you can split it up into a smaller set of changes
>so it's more obvious what's going on at each stage please?
>  
>
Sure. I'll try to divide it into smaller pieces. It will result in some 
patches that are just there to prepare for the other ones though (i.e. 
they don't add any functionality by themselves).

>We'll also need to run this by Linus first, explaining why you believe
>it's now ok to merge this.  (Added Linus...)
>
>  
>
First of, I can't really back up the claim that it isn't ok. The SDA has 
a paragraph about non-disclosure in their "IP Policy" 
(http://www.sdcard.org/membership/images/ippolicy.pdf) but it also 
states that exceptions can be granted.

Against this stands the new information that the SDA is changing its 
policy and making the specs public. This information comes from some of 
the guys at HP research and hasn't been confirmed by any public 
statement from SDA. The SDA have, however, already released the SDIO 
specs. Presumably as part of this new policy.

It was also pointed out in the previous thread by myself, Alan Cox and 
Ian Molton that SD specs have been publically available from different 
companies for quite some time. As such it is difficult for anyone to 
claim that these are secret and can be regulated by a NDA. The only part 
that hasn't been found in the wild is the spec for the 'secure' parts of 
the cards. But that also means that it isn't included in this patch so 
it shouldn't pose a problem.

As always, IANAL so I can't give any definite answer. But from my point 
of view they would have a very weak case if they tried to claim that the 
information in this patch is a trade secret.

Rgds
Pierre



  reply	other threads:[~2005-03-05 13:46 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-03 12:22 [PATCH][MMC] Secure Digital (SD) support Pierre Ossman
2005-03-04 13:22 ` Pavel Machek
2005-03-04 15:00 ` Marcel Holtmann
2005-03-04 15:12   ` Pierre Ossman
2005-03-04 16:22     ` Marcel Holtmann
2005-03-04 21:04     ` Ian Molton
2005-03-05 11:37 ` Russell King
2005-03-05 12:23   ` Pierre Ossman
2005-03-05 12:44     ` Russell King
2005-03-05 13:46       ` Pierre Ossman [this message]
2005-03-05 16:24         ` Richard Purdie
2005-05-06 14:15         ` Pierre Ossman
2005-03-06  1:34       ` [PATCH][MMC][0/6] " Pierre Ossman
2005-03-06  1:37         ` [PATCH][MMC][1/6] Secure Digital (SD) support : protocol Pierre Ossman
2005-03-19 16:35           ` Russell King
2005-03-06  1:44         ` [PATCH][MMC][2/6] Secure Digital (SD) support : init Pierre Ossman
2005-03-06  1:47         ` [PATCH][MMC][3/6] Secure Digital (SD) support : ro Pierre Ossman
2005-03-06  1:50         ` [PATCH][MMC][4/6] Secure Digital (SD) support : SCR Pierre Ossman
2005-03-06  1:52         ` [PATCH][MMC][5/6] Secure Digital (SD) support : sysfs Pierre Ossman
2005-03-06  1:57         ` [PATCH][MMC][6/6] Secure Digital (SD) support : wide bus Pierre Ossman
2005-03-12 17:35         ` [PATCH][MMC][7/6] Secure Digital (SD) support : Copyright Pierre Ossman

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=4229B847.5050301@drzeus.cx \
    --to=drzeus-list@drzeus.cx \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk+lkml@arm.linux.org.uk \
    --cc=rpurdie@rpsys.net \
    --cc=spyro@f2s.com \
    --cc=torvalds@osdl.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