From: jim.cromie@gmail.com
To: Muni Sekhar <munisekharrms@gmail.com>
Cc: alsa-devel <alsa-devel@alsa-project.org>,
"Valdis Klētnieks" <valdis.kletnieks@vt.edu>,
linux-sound@vger.kernel.org,
kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: ALSA kernel projects - for academic purposes
Date: Fri, 24 Sep 2021 12:23:04 -0600 [thread overview]
Message-ID: <CAJfuBxxVrbo6LyErMea8JWL0joZBrLa4Kg5r9qzwgW4JUVQvYQ@mail.gmail.com> (raw)
In-Reply-To: <CAHhAz+i48QEecqQ16u2s_Y_iw6V6dJzTDzEJO+w-eTYs6rYB7Q@mail.gmail.com>
On Fri, Sep 24, 2021 at 11:53 AM Muni Sekhar <munisekharrms@gmail.com> wrote:
>
> On Fri, Sep 24, 2021 at 10:46 PM <jim.cromie@gmail.com> wrote:
> >
> > On Fri, Sep 24, 2021 at 10:58 AM Muni Sekhar <munisekharrms@gmail.com> wrote:
> > >
> > > On Fri, Sep 24, 2021 at 10:02 PM Valdis Klētnieks
> > > <valdis.kletnieks@vt.edu> wrote:
> > > >
> > > > On Fri, 24 Sep 2021 19:34:59 +0530, Muni Sekhar said:
> > > > > What small projects would you suggest to a novice with the ALSA
> > > > > kernel. The aim is to develop a familiarity with the ALSA kernel
> > > > > source code, and also to submit it for academic purposes.
> > > >
> > > > A good place to start is getting a good handle on what the phrase "the ALSA
> > > > kernel" even means.
> > > Basically looking for kernel space audio subsystem projects rather
> > > than its user-space library(alsa-lib) and utilities(alsa-utils).
> >
> > why ?
> > if your interest is better sound, then improving user-space is going
> > to be more productive.
> >
> > also, theres now pipewire, which is new, and all the buzz.
> > its apparently the future of linux audio
> Sounds interesting. Could you please give few more pointers on how to
> start on pipewire project.
> >
https://pipewire.org/
you know everything I do now
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
WARNING: multiple messages have this Message-ID (diff)
From: jim.cromie@gmail.com
To: Muni Sekhar <munisekharrms@gmail.com>
Cc: alsa-devel <alsa-devel@alsa-project.org>,
"Valdis Klētnieks" <valdis.kletnieks@vt.edu>,
linux-sound@vger.kernel.org,
kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: ALSA kernel projects - for academic purposes
Date: Fri, 24 Sep 2021 12:23:04 -0600 [thread overview]
Message-ID: <CAJfuBxxVrbo6LyErMea8JWL0joZBrLa4Kg5r9qzwgW4JUVQvYQ@mail.gmail.com> (raw)
In-Reply-To: <CAHhAz+i48QEecqQ16u2s_Y_iw6V6dJzTDzEJO+w-eTYs6rYB7Q@mail.gmail.com>
On Fri, Sep 24, 2021 at 11:53 AM Muni Sekhar <munisekharrms@gmail.com> wrote:
>
> On Fri, Sep 24, 2021 at 10:46 PM <jim.cromie@gmail.com> wrote:
> >
> > On Fri, Sep 24, 2021 at 10:58 AM Muni Sekhar <munisekharrms@gmail.com> wrote:
> > >
> > > On Fri, Sep 24, 2021 at 10:02 PM Valdis Klētnieks
> > > <valdis.kletnieks@vt.edu> wrote:
> > > >
> > > > On Fri, 24 Sep 2021 19:34:59 +0530, Muni Sekhar said:
> > > > > What small projects would you suggest to a novice with the ALSA
> > > > > kernel. The aim is to develop a familiarity with the ALSA kernel
> > > > > source code, and also to submit it for academic purposes.
> > > >
> > > > A good place to start is getting a good handle on what the phrase "the ALSA
> > > > kernel" even means.
> > > Basically looking for kernel space audio subsystem projects rather
> > > than its user-space library(alsa-lib) and utilities(alsa-utils).
> >
> > why ?
> > if your interest is better sound, then improving user-space is going
> > to be more productive.
> >
> > also, theres now pipewire, which is new, and all the buzz.
> > its apparently the future of linux audio
> Sounds interesting. Could you please give few more pointers on how to
> start on pipewire project.
> >
https://pipewire.org/
you know everything I do now
WARNING: multiple messages have this Message-ID (diff)
From: jim.cromie@gmail.com
To: Muni Sekhar <munisekharrms@gmail.com>
Cc: alsa-devel <alsa-devel@alsa-project.org>,
"Valdis Klētnieks" <valdis.kletnieks@vt.edu>,
linux-sound@vger.kernel.org,
kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: ALSA kernel projects - for academic purposes
Date: Fri, 24 Sep 2021 18:23:04 +0000 [thread overview]
Message-ID: <CAJfuBxxVrbo6LyErMea8JWL0joZBrLa4Kg5r9qzwgW4JUVQvYQ@mail.gmail.com> (raw)
In-Reply-To: <CAHhAz+i48QEecqQ16u2s_Y_iw6V6dJzTDzEJO+w-eTYs6rYB7Q@mail.gmail.com>
On Fri, Sep 24, 2021 at 11:53 AM Muni Sekhar <munisekharrms@gmail.com> wrote:
>
> On Fri, Sep 24, 2021 at 10:46 PM <jim.cromie@gmail.com> wrote:
> >
> > On Fri, Sep 24, 2021 at 10:58 AM Muni Sekhar <munisekharrms@gmail.com> wrote:
> > >
> > > On Fri, Sep 24, 2021 at 10:02 PM Valdis Klētnieks
> > > <valdis.kletnieks@vt.edu> wrote:
> > > >
> > > > On Fri, 24 Sep 2021 19:34:59 +0530, Muni Sekhar said:
> > > > > What small projects would you suggest to a novice with the ALSA
> > > > > kernel. The aim is to develop a familiarity with the ALSA kernel
> > > > > source code, and also to submit it for academic purposes.
> > > >
> > > > A good place to start is getting a good handle on what the phrase "the ALSA
> > > > kernel" even means.
> > > Basically looking for kernel space audio subsystem projects rather
> > > than its user-space library(alsa-lib) and utilities(alsa-utils).
> >
> > why ?
> > if your interest is better sound, then improving user-space is going
> > to be more productive.
> >
> > also, theres now pipewire, which is new, and all the buzz.
> > its apparently the future of linux audio
> Sounds interesting. Could you please give few more pointers on how to
> start on pipewire project.
> >
https://pipewire.org/
you know everything I do now
next prev parent reply other threads:[~2021-09-24 18:23 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-24 14:04 ALSA kernel projects - for academic purposes Muni Sekhar
2021-09-24 14:16 ` Muni Sekhar
2021-09-24 14:04 ` Muni Sekhar
2021-09-24 16:32 ` Valdis Klētnieks
2021-09-24 16:32 ` Valdis Klētnieks
2021-09-24 16:32 ` Valdis Klētnieks
2021-09-24 16:57 ` Muni Sekhar
2021-09-24 16:58 ` Muni Sekhar
2021-09-24 16:58 ` Muni Sekhar
2021-09-24 17:15 ` jim.cromie
2021-09-24 17:15 ` jim.cromie
2021-09-24 17:15 ` jim.cromie
2021-09-24 17:52 ` Muni Sekhar
2021-09-24 17:53 ` Muni Sekhar
2021-09-24 17:53 ` Muni Sekhar
2021-09-24 18:23 ` jim.cromie [this message]
2021-09-24 18:23 ` jim.cromie
2021-09-24 18:23 ` jim.cromie
2021-09-29 14:59 ` Ruben Safir
2021-09-29 14:59 ` Ruben Safir
2021-09-29 14:59 ` Ruben Safir
2021-09-29 15:00 ` Ruben Safir
2021-09-29 15:00 ` Ruben Safir
2021-09-29 15:00 ` Ruben Safir
2021-10-01 8:54 ` Ricard Wanderlof
2021-10-01 8:54 ` Ricard Wanderlof
2021-10-01 8:54 ` Ricard Wanderlof
2021-09-24 22:26 ` Geraldo Nascimento
2021-09-24 22:26 ` Geraldo Nascimento
2021-09-24 22:26 ` Geraldo Nascimento
2021-09-29 15:07 ` Ruben Safir
2021-09-29 15:07 ` Ruben Safir
2021-09-29 15:07 ` Ruben Safir
2021-09-29 18:42 ` Geraldo Nascimento
2021-09-29 18:42 ` Geraldo Nascimento
2021-09-29 18:42 ` Geraldo Nascimento
2021-09-30 1:46 ` Ruben Safir
2021-09-30 1:46 ` Ruben Safir
2021-09-30 1:46 ` Ruben Safir
2021-09-30 16:31 ` Valdis Klētnieks
2021-09-30 16:31 ` Valdis Klētnieks
2021-09-30 16:31 ` Valdis Klētnieks
2021-09-30 2:11 ` Aruna Hewapathirane
2021-09-30 2:11 ` Aruna Hewapathirane
2021-09-30 3:01 ` Ruben Safir
2021-09-30 3:01 ` Ruben Safir
2021-09-30 3:01 ` Ruben Safir
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=CAJfuBxxVrbo6LyErMea8JWL0joZBrLa4Kg5r9qzwgW4JUVQvYQ@mail.gmail.com \
--to=jim.cromie@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=kernelnewbies@kernelnewbies.org \
--cc=linux-sound@vger.kernel.org \
--cc=munisekharrms@gmail.com \
--cc=valdis.kletnieks@vt.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.