From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Takashi Iwai <tiwai@suse.de>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
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 10:28:29 +0200 [thread overview]
Message-ID: <20170512082829.GB29311@physik.fu-berlin.de> (raw)
In-Reply-To: <s5hbmqy356r.wl-tiwai@suse.de>
On Fri, May 12, 2017 at 09:27:56AM +0200, 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?
Might also just be because the m68k port had been dead in Debian for a
while due the lack of TLS support in glibc on m68k. However, the port
is active again and in pretty good shape now.
I'm currently working on fixing debian-installer on m68k, so that
people can install the port without having to resort to things like
debootstrap.
> 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.
Thanks! Highly appreciated.
> Meanwhile we'll try to support ALSA on m64k and eventually target to
> drop dmasound stuff.
Ooooh, that would be awesome. If you need any testers on m68k, please
let us know. I have plenty of m68k hardware for testing.
> Does it sound more feasible?
No idea whether it's feasible. But it sounds awesome :).
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
prev parent reply other threads:[~2017-05-12 8:28 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
2017-05-12 8:28 ` John Paul Adrian Glaubitz [this message]
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=20170512082829.GB29311@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.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=tiwai@suse.de \
--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