From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: The Dream Master Solo <dreammastersolo@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [alsa-devel] Tascam Coding Inquiry
Date: Wed, 8 Jan 2020 18:54:31 +0900 [thread overview]
Message-ID: <20200108095430.GA16741@workstation> (raw)
In-Reply-To: <CAFmvAS8d0DCbJnzZjFbAD9-mP6gjRzjeEiVzOHDyCY5TLPKknw@mail.gmail.com>
Hi,
On Wed, Jan 08, 2020 at 01:36:36AM -0700, The Dream Master Solo wrote:
> Hello and good day to you. I am reaching out in regards to code I've
> found online. I looks like you are the author.
> [1]https://elixir.bootlin.com/linux/v5.5-rc5/source/sound/firewire/tascam
> I am interested in using this code in creating a 64 bit driver for OSX
> 10.13 or newer. I've just begun to learn coding a few weeks ago. Any
> help that you can give me towards accomplishing this goal would be
> greatly appreciated!
It's my pleasure to help developers ;) You can freely utilize the idea
written in the source of ALSA firewire-tascam driver with respect for
the modern framework of copyright treaty and law.
(This is one of my aim to publish the result of my reverse engineering
work for the series of device; FW-1884, FW-1082, FW-1804 and FE-8.)
I notice that it's better for you to have enough care of software
licensing itself. The source of driver is licensed under GNU General
Public License version 2.0 (GPLv2)[1]. Roughly speaking, when you just
copy any code from the source of driver to your software and distribute
your software to the others, your software should be licensed by GPLv2
or compatible ones because it includes lines in the source of driver.
On the other hand, as long as you write your software by your hand at
first place, you can freely license your software because the borrowing
of idea is free from the license on the copyright treaty and law.
Well, ALSA firewire-tascam driver uses controllers compliant to 1394
OHCI specification to communicate to the devices. For this purpose,
the driver uses kernel implementation of Linux FireWire subsystem. I
think that MacOS still includes the similar implementation and as a
first step you start study for it. Additionally the specification of
1394 OHCI will help your work:
* 1394 Open Host Controller Interface Specification Release 1.00
(October 20, 1997, Promoters of the 1394 Open HCI)
* 1394 Open Host Controller Interface Specification Release 1.1
(January 6, 2000, Promoters of the 1394 Open HCI)
[1] https://www.gnu.org/licenses/old-licenses/gpl-2.0.en.html
Regards
Takashi Sakamoto
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
parent reply other threads:[~2020-01-08 9:55 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAFmvAS8d0DCbJnzZjFbAD9-mP6gjRzjeEiVzOHDyCY5TLPKknw@mail.gmail.com>]
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=20200108095430.GA16741@workstation \
--to=o-takashi@sakamocchi.jp \
--cc=alsa-devel@alsa-project.org \
--cc=dreammastersolo@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox