From: Martin Langer <martin-langer@gmx.de>
To: Takashi Iwai <tiwai@suse.de>
Cc: Thierry Vignaud <tvignaud@mandrakesoft.com>, alsa-devel@alsa-project.org
Subject: Re: [RFC] re-queuing usx2y-fw
Date: Fri, 1 Apr 2005 13:16:11 +0200 [thread overview]
Message-ID: <20050401111611.GC7037@tuba> (raw)
In-Reply-To: <s5hk6nmepkn.wl@alsa2.suse.de>
On Fri, Apr 01, 2005 at 12:52:56PM +0200, Takashi Iwai wrote:
> 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:
> > >
> > > > 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?
> >
> > 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.
Controlling a checksum could solve that. md5sum? That would result in a
table of as31 version and their related checksum. If someone wants to
write it, go ahead :)
martin
-------------------------------------------------------
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
prev parent reply other threads:[~2005-04-01 11:15 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
2005-04-01 11:16 ` Martin Langer [this message]
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=20050401111611.GC7037@tuba \
--to=martin-langer@gmx.de \
--cc=alsa-devel@alsa-project.org \
--cc=tiwai@suse.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 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.