From: Takashi Iwai <tiwai@suse.de>
To: Patrick Welche <prlw1@cam.ac.uk>
Cc: alsa-devel@alsa-project.org, Clemens Ladisch <clemens@ladisch.de>
Subject: Re: alsa on non-linux
Date: Thu, 16 Jan 2014 14:46:52 +0100 [thread overview]
Message-ID: <s5hvbxkrqcz.wl%tiwai@suse.de> (raw)
In-Reply-To: <20140116132717.GB10286@quark.internal.precedence.co.uk>
At Thu, 16 Jan 2014 13:27:17 +0000,
Patrick Welche wrote:
>
> On Tue, Jan 14, 2014 at 03:04:58PM +0100, Clemens Ladisch wrote:
> > Patrick Welche wrote:
> > > I started out, writing the attached patch in November, but then it looked
> > > as though the boundaries of application library interface and linux sound
> > > chip driver had become so blurred that I thought that a decision had been
> > > taken to bin all OSes bar linux, hence the question. Can you give me a
> > > hint on how you think it is supposed to work?
> >
> > Only the "hw" plugins access the Linux kernel drivers. Anything else
> > should be portable (with the exception of plugins like "dmix" that
> > require a "hw" plugin as their slave).
> >
> > For most device types (hwdep/seq/rawmidi/timer), the hw plugin is the
> > only implementation, so a portable alsa-lib has only control and pcm
> > devices at the moment.
>
> So, rephrasing for the novice that I am, e.g., include/local.h contains
>
> #include <endian.h>
> ...
> #if __BYTE_ORDER == __LITTLE_ENDIAN
> ...
> #include <linux/types.h>
> #include <linux/ioctl.h>
>
> which are portability headaches. local.h is included by
>
> src/alisp/alisp.c:#include "local.h"
> src/conf.c:#include "local.h"
> src/confmisc.c:#include "local.h"
> src/control/control_local.h:#include "local.h"
> src/control/namehint.c:#include "local.h"
> src/control/setup.c:#include "local.h"
> src/dlmisc.c:#include "local.h"
> src/error.c:#include "local.h"
> src/hwdep/hwdep_local.h:#include "local.h"
> src/input.c:#include "local.h"
> src/mixer/mixer_local.h:#include "local.h"
> src/names.c:#include "local.h"
> src/output.c:#include "local.h"
> src/pcm/pcm_local.h:#include "local.h"
> src/rawmidi/rawmidi_local.h:#include "local.h"
> src/seq/seq_event.c:#include "local.h"
> src/seq/seq_local.h:#include "local.h"
> src/seq/seq_midi_event.c:#include "local.h"
> src/seq/seq_old.c:#include "local.h"
> src/socket.c:#include "local.h"
> src/timer/timer_local.h:#include "local.h"
> src/ucm/ucm_local.h:#include "local.h"
>
> That is fine except for files under directories src/control and src/pcm
> which ought to be portable? Or is it stronger, and everything should be
> portable except files under directory src/hwdep?
Why excluding hwdep...? And, no, the codes have been written to be
portable, but the primary goal is a thin layer for Linux kernel ABI,
thus its support is the highest priority.
The linux/*.h file inclusions are basically for allowing to include
sound/asound.h as is. It's a part of the Linux kernel code, and I
don't think we'd add any extra ifdefs there just for non-Linux.
IOW, you'd need to prepare some compatible defines before including
sound/asound.h if you need to compile for non-Linux systems.
Takashi
next prev parent reply other threads:[~2014-01-16 13:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-10 15:37 alsa on non-linux Patrick Welche
2014-01-13 12:13 ` Takashi Iwai
2014-01-14 10:17 ` Patrick Welche
2014-01-14 13:23 ` Takashi Iwai
2014-02-21 1:27 ` Patrick Welche
2014-02-21 11:04 ` Takashi Iwai
2014-02-23 11:12 ` Patrick Welche
2014-02-24 10:03 ` Takashi Iwai
2014-02-25 12:40 ` Patrick Welche
2014-02-26 7:17 ` Takashi Iwai
2014-01-14 14:04 ` Clemens Ladisch
2014-01-16 13:27 ` Patrick Welche
2014-01-16 13:46 ` Takashi Iwai [this message]
2014-02-25 12:45 ` Patrick Welche
2014-02-26 7:20 ` Takashi Iwai
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=s5hvbxkrqcz.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
--cc=prlw1@cam.ac.uk \
/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