All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Christoph Hellwig <hch@lst.de>, Jaroslav Kysela <perex@perex.cz>,
	Linus Torvalds <torvalds@linuxfoundation.org>,
	ALSA Development Mailing List <alsa-devel@alsa-project.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Linux/m68k" <linux-m68k@vger.kernel.org>
Subject: Re: [alsa-devel] future of sounds/oss
Date: Fri, 12 May 2017 09:27:56 +0200	[thread overview]
Message-ID: <s5hbmqy356r.wl-tiwai@suse.de> (raw)
In-Reply-To: <CAMuHMdX_gzspdn0r37GWvdvYwomy7T1M9baxsxmX_jBmwUWhRg@mail.gmail.com>

On Fri, 12 May 2017 09:17:35 +0200,
Geert Uytterhoeven wrote:
> 
> Hi Iwai-san,
> 
> On Fri, May 12, 2017 at 9:10 AM, Takashi Iwai <tiwai@suse.de> wrote:
> > On Fri, 12 May 2017 09:03:07 +0200,
> > Geert Uytterhoeven wrote:
> >> On Thu, May 11, 2017 at 10:21 PM, Takashi Iwai <tiwai@suse.de> wrote:
> >> > From: Takashi Iwai <tiwai@suse.de>
> >> > Subject: [PATCH] sound: Disable the build of OSS drivers
> >> >
> >> > OSS drivers are left as badly unmaintained, and now we're facing a
> >> > problem to clean up the hackish set_fs() usage in their codes.  Since
> >> > most of drivers have been covered by ALSA, and the others are dead old
> >> > and inactive, let's leave them RIP.
> >> >
> >> > This patch is the first step: disable the build of OSS drivers.
> >> > We'll eventually drop the whole codes and clean up later.
> >> >
> >> > Signed-off-by: Takashi Iwai <tiwai@suse.de>
> >> > ---
> >> >  sound/Kconfig | 26 ++++++++++++++------------
> >> >  1 file changed, 14 insertions(+), 12 deletions(-)
> >> >
> >> > diff --git a/sound/Kconfig b/sound/Kconfig
> >> > index ee2e69a9ecd1..41eda578d08e 100644
> >> > --- a/sound/Kconfig
> >> > +++ b/sound/Kconfig
> >> > @@ -54,7 +54,8 @@ config SOUND_OSS_CORE_PRECLAIM
> >> >
> >> >           If unsure, say Y.
> >> >
> >> > -source "sound/oss/dmasound/Kconfig"
> >> > +### TO-BE-REMOVED
> >> > +# source "sound/oss/dmasound/Kconfig"
> >>
> >> Please note the dmasound drivers do not have ALSA equivalents.
> >
> > These belong to the latter, "dead old and inactive" ones :)
> >
> > Are these driver still used with the latest kernel?  If users are
> 
> I believe so.
> 
> > willing to help, we can provide the port to ALSA drivers, too.
> 
> That would be great, thanks!

OK, we can go forward, then.

But, looking at the tree again, I noticed that ALSA isn't built yet at
all for m68k.  I don't remember why it's disabled.
Jaroslav, do you know the reason behind it?

And, dmasound is a completely different implementation from the other
OSS, thus it doesn't suffer from set_fs() hack.  That is, we may still
keep dmasound, while removing other OSS stuff.

Meanwhile we'll try to support ALSA on m64k and eventually target to
drop dmasound stuff.

Does it sound more feasible?


thanks,

Takashi

  reply	other threads:[~2017-05-12  7:28 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-11  8:21 future of sounds/oss Christoph Hellwig
2017-05-11  8:46 ` [alsa-devel] " Takashi Iwai
2017-05-11  8:46   ` Takashi Iwai
2017-05-11  9:15   ` [alsa-devel] " Christoph Hellwig
2017-05-11  9:15     ` Christoph Hellwig
2017-05-11 20:21     ` [alsa-devel] " Takashi Iwai
2017-05-11 20:21       ` Takashi Iwai
2017-05-11 20:28       ` [alsa-devel] " Linus Torvalds
2017-05-11 20:28         ` Linus Torvalds
2017-05-11 20:36         ` Randy Dunlap
2017-05-11 20:36           ` Randy Dunlap
2017-05-11 20:40         ` Takashi Iwai
2017-05-11 20:40           ` Takashi Iwai
2017-05-12  7:03       ` [alsa-devel] " Geert Uytterhoeven
2017-05-12  7:10         ` Takashi Iwai
2017-05-12  7:17           ` Geert Uytterhoeven
2017-05-12  7:27             ` Takashi Iwai [this message]
2017-05-12  7:30               ` Geert Uytterhoeven
2017-05-12  8:01                 ` Takashi Iwai
2017-05-16  7:45                   ` Geert Uytterhoeven
2017-05-16  8:44                     ` Takashi Iwai
2017-05-12  8:28               ` John Paul Adrian Glaubitz
2017-05-11 10:01   ` Takashi Sakamoto
2017-05-11 10:36     ` Takashi Sakamoto
2017-05-11 12:14       ` Takashi Iwai

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=s5hbmqy356r.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=geert@linux-m68k.org \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=torvalds@linuxfoundation.org \
    /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.