From: Ian Molton <ian@mnementh.co.uk>
To: Don Mullis <don.mullis@gmail.com>
Cc: linux-mmc@vger.kernel.org
Subject: Re: legal status of code derived from sdcard.org specs?
Date: Sun, 16 Aug 2009 18:23:56 +0100 [thread overview]
Message-ID: <4A8840AC.5050204@mnementh.co.uk> (raw)
In-Reply-To: <4A860486.1030001@gmail.com>
Don Mullis wrote:
> sdcard.org specs appear to not be (any longer) public. When downloading
> some today I had to give an employer's name, and received in return PDFs
> watermarked with that name.
If you can put in any name, and they dont verify it, I cant imagine they
can claim the specs are private.
> This is a practical issue for a couple of patches that I'd like to post
> for review. They extend the existing code that extracts the CSD and SCR
> registers to extract as well an SD-specific register containing some
> performance-related parameters.
Are the details unavailable in earlier 'open' versions of the docs ?
> Any ideas on how we might seek clarification?
email sdcard.org ?
-Ian
next parent reply other threads:[~2009-08-16 17:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4A860486.1030001@gmail.com>
2009-08-16 17:23 ` Ian Molton [this message]
2009-08-17 21:49 ` legal status of code derived from sdcard.org specs? Don Mullis
2009-08-17 16:12 ` H Hartley Sweeten
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=4A8840AC.5050204@mnementh.co.uk \
--to=ian@mnementh.co.uk \
--cc=don.mullis@gmail.com \
--cc=linux-mmc@vger.kernel.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