The OSS sound drivers that were formally included in the Linux kernel had the same genesis as the Open Sound System discussed in this forum.See http://www.opensound.com/ossfree/ for details.There is also README file in the kernel documentation that explains the situation with OssFree and its relation to Open Sound System.https://www.kernel.org/doc/readme/Docum ... README.OSSAs Alan Cox is no longer a kernel maintainer I am surprised that OSS has remained in the kernel this long.More worryingly is that the release of Linux kernel 4.15 has broken the official Open Sound System due to changes to the timer API in linux/timer.h.https://lwn.net/Articles/735887/

Anton2 wrote:Could somebody explain the future perspectives of OSS in Linux in conjunction with the following information about linux kernel 4.15 release?

The biggest change from diffstat POV is the removalof the legacy OSS driver codes that have been already disabled for along time. _https://lkml.org/lkml/2017/11/14/346

What was removed is the legacy OSS v.3 (OSS3) driver codes "that have been already disabled for along time."

This does not concern OSS4 users.You are using OSS v.4 (OSS4). Right?

OSS4 was never enabled in the Linux kernel.It was never included into the official releases of the Linux kernel.There is nothing to remove.

See also:State of sound in Linux not so sorry after all _http://insanecoding.blogspot.de/2009/06/state-of-sound-in-linux-not-so-sorry.htmlKernel Deblobing (Gentoo Wiki)_https://wiki.gentoo.org/wiki/Kernel_Deblobing

seawright wrote:More worryingly is that the release of Linux kernel 4.15 has broken the official Open Sound System due to changes to the timer API in linux/timer.h. _https://lwn.net/Articles/735887/

So that, a new "magic patch" might be needed to compile OSS4 for Linux kernel 4.15. Right?

In short, the so-called "legacy OSS driver codes" are the legacy OSS v.3 (OSS3) driver codes.There are useless in an absolute sense, perhaps.These useless drivers "have been already disabled for a long time." _https://lkml.org/lkml/2017/11/14/346The Linux developers simply removed some useless "codes". This was said to be "the biggest change" in the Linux kernel 4.15 release.

"The future perspectives of OSS in Linux" seems to be the same as before. OSS4 users have to practice the magic of patching.

As usual, you have to patch OSS4 to compile it for a new kernel.

The "magic patch" has already been created by seawright_http://ossnext.trueinstruments.com/forum/viewtopic.php?f=3&t=5862You can try to patch OSS4 and compile it for kernel 4.15.

The patch can be applied with a text editor, or with the patch command.

There is a special magic tool, named "quilt", for creating, editing, and testing patches.

Using quiltA simpler way to create patches is using "quilt" which has better job to manage many patches, such as applying patches, refreshing patches, and reverting patched files to original state. "quilt" is used on Debian to manage their patches. _https://wiki.archlinux.org/index.php/Patching_packages#Using_quilt

Quilt has been incorporated into dpkg, Debian's package manager and is one of the standard source formats supported from the Debian "squeeze" release onwards. This source format is identified as "3.0 (quilt)" by dpkg._https://en.wikipedia.org/wiki/Quilt_%28software%29

Guilt allows one to use quilt functionality on top of a Git repository. Changes are maintained as patches which are committed into Git. Commits can be removed or reordered, and the underlying patch can be refreshed based on changes made in the working directory. The patch directory can also be placed under revision control, so you can have a separate history of changes made to your patches. _https://linux.die.net/man/7/guilt