All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Martin Langer <martin-langer@gmx.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: [RFC] re-queuing usx2y-fw
Date: Tue, 29 Mar 2005 17:01:55 +0200	[thread overview]
Message-ID: <s5hfyyeijh8.wl@alsa2.suse.de> (raw)
In-Reply-To: <20050328155151.GA3552@tuba>

At Mon, 28 Mar 2005 17:51:51 +0200,
Martin Langer wrote:
> 
> Hi,
> 
> long time ago there was a thread about replacing tascam_loader.ihx with 
> an open firmware:
> 
> http://sourceforge.net/mailarchive/message.php?msg_id=8555003
> 
> http://www.langerland.de/audio/usx2y/usx2y-fw-0.1b.tar.bz2
> 
> All results were quite positive and I've had a lot of downloads since 
> them on my site and I never ever got a bugreport about it :)
> 
> What about a second attempt of merging it into alsa-firmware? Any new 
> strategies for this step?

No, I prefer the traditional one:  Send a patch :)

> The code still depends on as31 (8031/8051 
> crosss-assembler) which still isn't available as .rpm or .deb, at least 
> newer versions since 2.1. Should we care about it?

For convenience, we may include both the firmware source and binary in
the CVS repository, so that one can install even without as31.

> I use it on my US-122 since several months without problems and we have 
> positive results from us224 and us428 owners. Even the size has only 20 
> percent of the size of the original tascam file. Aren't these good 
> reasons for deleting the original closed source file?

Open-source version is _always_ good (if it provides the same
functionality).


> Another point is the license note in the README file for those Tascam 
> files. Is it really true for tascam_loader.ihx? I (we?) know that 
> tascam_loader.ihx and MidiSportLoader.ihx (for M-Audio MidiSport's) are 
> 100% identical; there's no difference. So I believe that this file is 
> part of the same 3rd party development kit and is not be copyrighted by 
> Tascam? I don't know it, but Tascam should know it better... just my 
> two cents.

If so, most likely you're right...


Takashi


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

  reply	other threads:[~2005-03-29 15:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-28 15:51 [RFC] re-queuing usx2y-fw Martin Langer
2005-03-29 15:01 ` Takashi Iwai [this message]
2005-03-29 16:58   ` Martin Langer
2005-03-29 17:03     ` Takashi Iwai
2005-03-31 11:58       ` Martin Langer
2005-03-31 15:48         ` Takashi Iwai
2005-04-01 10:26           ` Martin Langer
2005-04-01 10:50             ` Takashi Iwai
2005-03-31 16:03         ` Thierry Vignaud
2005-04-01 10:33           ` Martin Langer
2005-04-01 10:52             ` Takashi Iwai
2005-04-01 11:16               ` Martin Langer

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=s5hfyyeijh8.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=martin-langer@gmx.de \
    /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.