Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Martin Langer <martin-langer@gmx.de>
Cc: Thierry Vignaud <tvignaud@mandrakesoft.com>, alsa-devel@alsa-project.org
Subject: Re: [RFC] re-queuing usx2y-fw
Date: Fri, 01 Apr 2005 12:52:56 +0200	[thread overview]
Message-ID: <s5hk6nmepkn.wl@alsa2.suse.de> (raw)
In-Reply-To: <20050401103348.GB7037@tuba>

At Fri, 1 Apr 2005 12:33:48 +0200,
Martin Langer wrote:
> 
> On Thu, Mar 31, 2005 at 06:03:41PM +0200, Thierry Vignaud wrote:
> > Martin Langer <martin-langer@gmx.de> writes:
> > 
> > > > > > > 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.
> > > > > 
> > > > > Yep. I will try to introduce a new configure option like
> > > > > '--enable-buildfw' for it, or any similar solution.
> > > > 
> > > > That'll be nice.
> > > 
> > > Here it is. The new configure option for alsa-firmware is called
> > > '--enable-buildfw'. If you want to build it from source you have to
> > > install one of the latest versions of as31, which you can find at
> > > 
> > > http://wiki.erazor-zone.de/doku.php?id=wiki:projects:linux:as31
> > 
> > why not auto enabling it if we detect the non free as31 rather than
> > just providing such flag?
> > 
> 
> BSD license is non free?
> 
> Is it really necessary to build it by default? I see a lot of trouble at 
> the horizon due to version mismatches of as31. An as31 version check 
> could solve it, though.

Agreed.  The resultant firmware should be 100% identical even if you
build by yourself.  Hence I don't think it's needed so much.


Takashi


-------------------------------------------------------
This SF.net email is sponsored by Demarc:
A global provider of Threat Management Solutions.
Download our HomeAdmin security software for free today!
http://www.demarc.com/Info/Sentarus/hamr30

  reply	other threads:[~2005-04-01 10:52 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
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 [this message]
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=s5hk6nmepkn.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=martin-langer@gmx.de \
    --cc=tvignaud@mandrakesoft.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