Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Ulf Carlsson <grim@zigzegv.ml.org>
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: HAL2
Date: Sun, 4 Oct 1998 16:38:40 +0200	[thread overview]
Message-ID: <19981004163840.40084@alpha.franken.de> (raw)
In-Reply-To: <Pine.LNX.3.96.981004125525.2569A-100000@calypso.saturn>; from Ulf Carlsson on Sun, Oct 04, 1998 at 01:23:12PM +0200

On Sun, Oct 04, 1998 at 01:23:12PM +0200, Ulf Carlsson wrote:
> level applications. The implementation of my HAL2 driver will exist in
> kernel space, and a user level library will provide higher level interface
> to the applications (the same interface as libaudio.a in IRIX). Do we know
> what the interface between libaudio.a and the Irix kernel looks like or am
> I free to do what I want?

For IRIX compatibilty, we may want to implement the same interface as
IRIX has. But for Linux compatiblity we should have something, which fits
into the current Linux sound devices scheme. And as the Linux interface is 
available in source, I would go that way. And when you do the libaudio.a 
stuff based on the Linux sound devices, it will also be available for other 
Linux architectures.

Maybe it's even possible to get IRIX compatible sound, with a user level
only solution.

Thomas.

-- 
See, you not only have to be a good coder to create a system like Linux,
you have to be a sneaky bastard too ;-)
                   [Linus Torvalds in <4rikft$7g5@linux.cs.Helsinki.FI>]

      parent reply	other threads:[~1998-10-04 14:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-10-04 11:23 HAL2 Ulf Carlsson
1998-10-04 12:49 ` HAL2 Alan Cox
1998-10-04 12:06   ` HAL2 Ulf Carlsson
1998-10-04 13:08     ` HAL2 Alan Cox
1998-10-04 13:08       ` HAL2 Alan Cox
1998-10-04 12:49   ` HAL2 Alan Cox
1998-10-04 14:38 ` Thomas Bogendoerfer [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=19981004163840.40084@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=grim@zigzegv.ml.org \
    --cc=linux@cthulhu.engr.sgi.com \
    /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