lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMuHMdW5WFhX=wEiCfHCReXSeedPAshc_3D=ULx6PFeb9tEd-w@mail.gmail.com>
Date:   Fri, 12 May 2017 09:30:04 +0200
From:   Geert Uytterhoeven <geert@...ux-m68k.org>
To:     Takashi Iwai <tiwai@...e.de>
Cc:     Christoph Hellwig <hch@....de>, Jaroslav Kysela <perex@...ex.cz>,
        Linus Torvalds <torvalds@...uxfoundation.org>,
        ALSA Development Mailing List <alsa-devel@...a-project.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "Linux/m68k" <linux-m68k@...r.kernel.org>
Subject: Re: [alsa-devel] future of sounds/oss

Hi Iwai-san,

On Fri, May 12, 2017 at 9:27 AM, Takashi Iwai <tiwai@...e.de> wrote:
> On Fri, 12 May 2017 09:17:35 +0200,
> Geert Uytterhoeven wrote:
>> On Fri, May 12, 2017 at 9:10 AM, Takashi Iwai <tiwai@...e.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@...e.de> wrote:
>> >> > 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?

Because ALSA doesn't have any drivers that can be used on m68k platforms?

> 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.

That's indeed good to know.

> Meanwhile we'll try to support ALSA on m64k and eventually target to
> drop dmasound stuff.
>
> Does it sound more feasible?

Yes, definitely in the short run ;-)

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ