public inbox for linux-m68k@lists.linux-m68k.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: Tue, 16 May 2017 10:44:57 +0200	[thread overview]
Message-ID: <s5ho9utyyuu.wl-tiwai@suse.de> (raw)
In-Reply-To: <CAMuHMdUfMt_HMybx9T0mUSCaNqhJSstqXaWYC7jhnzo36iBHKA@mail.gmail.com>

On Tue, 16 May 2017 09:45:04 +0200,
Geert Uytterhoeven wrote:
> 
> Hi Iwai-san,
> 
> On Fri, May 12, 2017 at 10:01 AM, Takashi Iwai <tiwai@suse.de> wrote:
> >> > 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?
> >>
> >> Because ALSA doesn't have any drivers that can be used on m68k platforms?
> >
> > But we have virtual and generic drivers (such as UART support), so
> > there seems no reason to stop it.  Maybe the lack of proper MMU
> 
> It seems to date back to the move of sound from arch/*/Kconfig
> to sound/Kconfig. I guess at that time there was just no use for ALSO on
> m68k.
> 
> > support was the reason?  Let's try to cross-build...
> 
> Building seems to work fine...

Worked fine with my cross-build test, too.
OK, let's enable the build on 4.13.  The patch is attached below.


thanks,

Takashi

-- 8< --
From: Takashi Iwai <tiwai@suse.de>
Subject: [PATCH] ALSA: Enable build with m68k

By some reason in the ancient history, we disabled the build of ALSA
drivers for m68k.  Since we'd like to move sound/oss/dmasound stuff
into ALSA for the complete drop of the legacy OSS stuff, let's try to
start building with m68k.

Signed-off-by: Takashi Iwai <tiwai@suse.de>
---
 sound/Kconfig | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/sound/Kconfig b/sound/Kconfig
index ee2e69a9ecd1..6437e398b08e 100644
--- a/sound/Kconfig
+++ b/sound/Kconfig
@@ -56,7 +56,7 @@ config SOUND_OSS_CORE_PRECLAIM
 
 source "sound/oss/dmasound/Kconfig"
 
-if !M68K && !UML
+if !UML
 
 menuconfig SND
 	tristate "Advanced Linux Sound Architecture"
@@ -124,7 +124,7 @@ source "sound/oss/Kconfig"
 
 endif # SOUND_PRIME
 
-endif # !M68K
+endif # !UML
 
 endif # SOUND
 
-- 
2.12.2

  reply	other threads:[~2017-05-16  8:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170511082133.GA20304@lst.de>
     [not found] ` <s5hh90rhjbc.wl-tiwai@suse.de>
     [not found]   ` <20170511091511.GA21055@lst.de>
     [not found]     ` <s5hy3u32lhi.wl-tiwai@suse.de>
2017-05-12  7:03       ` [alsa-devel] future of sounds/oss Geert Uytterhoeven
2017-05-12  7:10         ` Takashi Iwai
2017-05-12  7:17           ` Geert Uytterhoeven
2017-05-12  7:27             ` Takashi Iwai
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 [this message]
2017-05-12  8:28               ` John Paul Adrian Glaubitz

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=s5ho9utyyuu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox