From: Takashi Iwai <tiwai@suse.de>
To: Hannu Savolainen <hannu@opensound.com>
Cc: Jaroslav Kysela <perex@suse.cz>, alsa-devel@lists.sourceforge.net
Subject: Re: Implementing ALSA compatibility in OSS
Date: Mon, 15 Nov 2004 19:52:46 +0100 [thread overview]
Message-ID: <s5hd5yfdjwh.wl@alsa2.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0411151859220.9516@zeus.compusonic.fi>
At Mon, 15 Nov 2004 19:31:23 +0200 (EET),
Hannu Savolainen wrote:
>
> On Mon, 15 Nov 2004, Jaroslav Kysela wrote:
>
> > On Mon, 15 Nov 2004, Hannu Savolainen wrote:
> >
> > > OSS is a driver API and it's definitely designed to be used directly.
> >
> > It's (and was) a broken idea. We have never ending trouble to reroute your
> > API to ours, because you have not designed a proper library in the user
> > space to handle application requests.
> Interesting point. Do you mean that all Linux drivers for whatever devices
> should have defined their own library interface instead of the using the
> traditional Unix device/file interface?
It depends. Accessing to the device file would make sense for many
simple devices, but not for the devices with wide variety.
The problem of the direct device access is that it restricts the
extension of the API. It can never exceed the limitation of the
kernel. That is, you can't use floating point in the lowlevel
(i.e. system level) layer.
> To me this uniform and robust device/file abstraction was the main reason
> to get married with Unix. That happened exactly 20 years ago, btw. It was
> also the reason why I originally designed OSS in this way.
>
> OSS doesn't have it's own library API. Our goal has been to develop as
> good device drivers as possible and nothing else. As a small company have
> intentionally left all user space development (including libraries) to
> others.
I see your point. I would say it's a different design decision.
For example, the current design of ALSA lib isn't well suitable for
the embedded system. It's because we wanted to have a powerful and
extensible middle layer which can be used uniquely by apps. For the
tiny systems, OTOH, it's too bold.
Takashi
-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
next prev parent reply other threads:[~2004-11-15 18:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-15 10:38 Implementing ALSA compatibility in OSS Hannu Savolainen
2004-11-15 13:13 ` Clemens Ladisch
2004-11-15 13:41 ` Hannu Savolainen
2004-11-15 16:01 ` Jaroslav Kysela
2004-11-15 17:31 ` Hannu Savolainen
2004-11-15 18:52 ` Takashi Iwai [this message]
2004-11-15 19:58 ` Jaroslav Kysela
2004-11-16 9:34 ` Takashi Iwai
2004-11-16 9:56 ` Jaroslav Kysela
2004-11-15 19:14 ` Paul Davis
2004-11-15 16:27 ` Clemens Ladisch
2004-11-15 17:58 ` Hannu Savolainen
2004-11-15 19:03 ` Takashi Iwai
-- strict thread matches above, loose matches on Subject: below --
2004-11-15 11:25 Peter Zubaj
2004-11-15 11:48 ` Hannu Savolainen
2004-11-15 12:29 ` Hannu Savolainen
2004-11-15 13:11 Peter Zubaj
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=s5hd5yfdjwh.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=hannu@opensound.com \
--cc=perex@suse.cz \
/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.