From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751728AbdEPHpI (ORCPT ); Tue, 16 May 2017 03:45:08 -0400 Received: from mail-it0-f47.google.com ([209.85.214.47]:37860 "EHLO mail-it0-f47.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751253AbdEPHpG (ORCPT ); Tue, 16 May 2017 03:45:06 -0400 MIME-Version: 1.0 In-Reply-To: References: <20170511082133.GA20304@lst.de> <20170511091511.GA21055@lst.de> From: Geert Uytterhoeven Date: Tue, 16 May 2017 09:45:04 +0200 X-Google-Sender-Auth: 28_BeFNgFPqsM867-TeDDlKk2gI Message-ID: Subject: Re: [alsa-devel] future of sounds/oss To: Takashi Iwai Cc: Christoph Hellwig , Jaroslav Kysela , Linus Torvalds , ALSA Development Mailing List , "linux-kernel@vger.kernel.org" , "Linux/m68k" Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Iwai-san, On Fri, May 12, 2017 at 10:01 AM, Takashi Iwai 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... Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds