From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Richard Purdie <rpurdie@rpsys.net>
Cc: Russell King <rmk+lkml@arm.linux.org.uk>,
Ian Molton <spyro@f2s.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Pierre Ossman <drzeus-list@drzeus.cx>
Subject: Re: MMC Driver RFC
Date: Sun, 16 Jan 2005 22:33:20 +0000 [thread overview]
Message-ID: <1105914799.12196.29.camel@localhost.localdomain> (raw)
In-Reply-To: <047701c4fc21$a1579b50$0f01a8c0@max>
On Sul, 2005-01-16 at 23:17, Richard Purdie wrote:
> On the subject of patents, the whole idea behind SD is that there aren't
> patents as for a patent to exist, we'd have some publicly available
> information on how SD works. We're not breaking any copyrights as I nobody
> involved with this code has see any code to copy from.
>
> So in short, I can't see any reason we can't put the code we have into the
> kernel...
Given that companies like Intel have been published the SD
initialisation sequences since 2002 and nobody has taken any action I
can't see this as being credibly a trade secret or obtained maliciously.
Nor does the document state anything is secret.
See Intel app note 278533-001 "Using SDCard and SDIO with Intel (r)
PXA250 Applications Processor MMC Controller"
http://www.intel.com/design/pca/applicationsprocessors/applnots/278533-001.htm
If there were any secrets the owners appear to have failed to take any
action neccessary to defend them.
Alan
next prev parent reply other threads:[~2005-01-16 23:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-12 21:10 MMC Driver RFC Richard Purdie
2005-01-12 21:43 ` Russell King
2005-01-12 22:07 ` Richard Purdie
2005-01-12 22:17 ` Russell King
2005-01-12 23:23 ` Ian Molton
2005-01-12 23:58 ` Richard Purdie
2005-01-14 11:37 ` Pierre Ossman
2005-01-14 14:55 ` Ian Molton
2005-01-16 12:22 ` Pierre Ossman
2005-01-16 13:19 ` Ian Molton
2005-01-16 19:43 ` Pierre Ossman
2005-01-16 23:17 ` Richard Purdie
2005-01-16 22:33 ` Alan Cox [this message]
2005-01-17 6:07 ` Pierre Ossman
2005-01-17 9:53 ` Richard Purdie
2005-01-17 11:59 ` 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=1105914799.12196.29.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=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 \
/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.