public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Richard Purdie" <rpurdie@rpsys.net>
To: "Pierre Ossman" <drzeus-list@drzeus.cx>,
	"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>
Subject: Re: [PATCH][MMC] Secure Digital (SD) support
Date: Sat, 5 Mar 2005 16:24:47 -0000	[thread overview]
Message-ID: <01b801c5219f$df6a00b0$0f01a8c0@max> (raw)
In-Reply-To: 4229B847.5050301@drzeus.cx

Pierre Ossman:
> 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.

That IP policy covers their members and has no bearing on us as we have no 
agreements with them.

The code is "our" own so it isn't covered by any IP or copyright 
restrictions other than the GPL.

There aren't any patents relating to SD cards.

The simple sequences we use have been gleaned from various public documents 
(intel's website, SD card manufacturer data sheets, etc.) so nobody can 
claim we're using anything secret.

I therefore can't see a problem with including the code.

Richard 


  reply	other threads:[~2005-03-05 16:36 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
2005-03-05 16:24         ` Richard Purdie [this message]
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='01b801c5219f$df6a00b0$0f01a8c0@max' \
    --to=rpurdie@rpsys.net \
    --cc=drzeus-list@drzeus.cx \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk+lkml@arm.linux.org.uk \
    --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