From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from cantor2.suse.de ([195.135.220.15]:60270 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753427Ab1JJMlI (ORCPT ); Mon, 10 Oct 2011 08:41:08 -0400 Date: Mon, 10 Oct 2011 14:41:05 +0200 Message-ID: (sfid-20111010_144112_411274_DF892BBF) From: Takashi Iwai To: "Luis R. Rodriguez" Cc: Jesper Andersen , linux-wireless , alsa-devel@alsa-project.org, julia@diku.dk, linux-kernel@vger.kernel.org Subject: Re: [alsa-devel] Using spdiff for backporting In-Reply-To: References: <1317721043.11231.2.camel@jmachine> MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Sender: linux-wireless-owner@vger.kernel.org List-ID: At Fri, 7 Oct 2011 10:41:06 -0700, Luis R. Rodriguez wrote: > > > Also, in the slides from the plumbers-conf. I think I saw it mentioned > > that there's also an alsa-compat git-tree somewhere. Maybe that is a > > more compelling usecase? I was unable to find it though so I'd > > appreciate a link. > > It was on kernel.org, but if it got rm -rf'd then its gone as I do not > have a local copy. Oh, I didn't know of such a tree. So you created alsa driver build system with your spdiff? That's interesting. > The compat-alsa stuff though was determined to be > superflous with the ALSA's team's own backport work which is currently > independent. Yes, the external alsa-driver build tree has existed since 10 years ago :) It was even possible to build with 2.2/2.4 kernels until recently. The current tree is found in github, git://github.com/tiwai/alsa-driver-build.git > My hope though is to unify these through the compat.git / > compat-kernel (currently just called compat-wireless) effort. The common framework would be really nice to have. V4L also have own build system, and possible other subsystem trees too. thanks, Takashi