AudioScience driver

AudioScience driver

[Eliot Blennerhassett]

[-- Attachment #1: Type: text/plain, Size: 830 bytes --]

Hello all,

thanks to various people on this list, I have managed to make an ALSA driver
that works for most AudioScience cards.  

I have attached a patch against alsa-driver-0.9.4
But I'm not sure if this is the desired form, or whether I have located the
driver in the correct part of the tree.

This driver depends on a module external to ALSA (asihpi, (GPL), available from
our website).  I couldn't figure out how to add a driver specific include path,
so  I made a symbolic link across to the (only one) header file.

Any constructive advice on how to proceed will be appreciated,

thanks and regards

Eliot Blennerhassett
AudioScience Inc.
--
Junk footer beyond this point. Read at your own risk.


-------------------------------------------------------------
Sign up for ICQmail at http://www.icq.com/icqmail/signup.html

[-- Attachment #2: alsa-driver-0.9.4asihpi.tar.gz --]
[-- Type: application/x-gzip, Size: 10714 bytes --]

Re: AudioScience driver

[Takashi Iwai]

At Mon, 23 Jun 2003 22:14:51 -0700 (PDT),
Eliot Blennerhassett wrote:
> 
> Hello all,
> 
> thanks to various people on this list, I have managed to make an ALSA driver
> that works for most AudioScience cards.  
> 
> I have attached a patch against alsa-driver-0.9.4
> But I'm not sure if this is the desired form, or whether I have located the
> driver in the correct part of the tree.
> 
> This driver depends on a module external to ALSA (asihpi, (GPL), available from
> our website).  I couldn't figure out how to add a driver specific include path,
> so  I made a symbolic link across to the (only one) header file.

an easy solution is to copy the necessary header files from the asihpi
driver to the alsa driver tree.  if it's under GPL, no problem about
this action :)

however, if the asihpi driver is subjected to be changed often (and
its external functions, too), it's of course better to use symlink to
follow it.
in this case, we'll add a configure option to specify the directory of
the asihpi driver source. then audioscience driver will be disabled
unless this option is specified.


Takashi


-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php

Re: AudioScience driver

[Fred Gleason]

On Tuesday 24 June 2003 01:14, Eliot Blennerhassett wrote:

> I have attached a patch against alsa-driver-0.9.4
> But I'm not sure if this is the desired form, or whether I have located the
> driver in the correct part of the tree.

I've tried building things with the patch, and have some questions:

1)  Your directions tell me to execute a './cvsconfigure' command (at the root 
of the ALSA source tree).  There is no such command in the 0.9.4 tree (at 
least in the tarball).  Does this patch require use of a checked-out CVS 
tree?

2)  What is the name of the module that this should generate?  'snd-asihpi' is 
coming up as not found.

3)  What is the exact relationship between the ALSA module and 'asihpi'?  Does 
one need to be loaded for the other to work?  Exactly what is dependent upon 
what?  An example 'modules.conf' setup would be very helpful here!


> This driver depends on a module external to ALSA (asihpi, (GPL), available
> from our website).  I couldn't figure out how to add a driver specific
> include path, so  I made a symbolic link across to the (only one) header
> file.

I'd like to propose that the "standard" location of the HPI header henceforth 
be:

	/usr/include/hpi/hpi.h

Then, applications need only do:

#include <hpi/hpi.h>

for things to work.  I've been using this layout in my own apps for some time 
now.  While we're at it, perhaps we could add an install rule for this into 
the makefile for hpklinux (and one for libhpi.a >> /usr/lib as well).  This 
would have the added benefit of getting strange symlinks out of the ALSA 
source tree.  :)

Cheers!


|-------------------------------------------------------------------------|
|      Frederick F. Gleason, Jr.      |         Salem Radio Labs          |
|       Voice: 1-(540)-341-2880       |      87 Lee Highway, Suite 11     |
|        FAX: 1-(540)-341-7176        |        Warrenton, VA 20188        |
|-------------------------------------------------------------------------|
|   Some people call them "cars" or "trucks"; I call them "dimensional    |
|   transmogrifiers" because they change three-dimensional cats into      |
|   two-dimensional ones.                                                 |
|                                         -- F. Frederick Skitty          |
|-------------------------------------------------------------------------|



-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php

Re: AudioScience driver

[Eliot Blennerhassett]

Fred thanks for your feedback

> I've tried building things with the patch, and have some questions:

> 1)  Your directions tell me to execute a './cvsconfigure' command (at the root 
> of the ALSA source tree).  There is no such command in the 0.9.4 tree (at 
> least in the tarball).  Does this patch require use of a checked-out CVS 
> tree?

Sorry Fred, I misremembered the script name...
I meant ./cvscompile  in alsa-driver-0.9.4/
This rebuilds the dependencies so that snd-asihpi is known about and can be
built.

> 2)  What is the name of the module that this should generate?  'snd-asihpi' is 
> coming up as not found.

Correct

3)  What is the exact relationship between the ALSA module and 'asihpi'?  Does 
one need to be loaded for the other to work?  Exactly what is dependent upon 
what?  An example 'modules.conf' setup would be very helpful here!

snd-asihpi needs asihpi.  This is covered automatically by the "depmod -a" that
happens at the end of a make install.
So if you "modprobe snd-asihpi" all the underlying alsa modules + asihpi will
get loaded.

All I have in my modules.conf is "alias snd-card-0 snd-asihpi"

A note about Card indices
snd-asihpi will try to assign the ALSA device index to be the same as the card
index set by the jumpers on the card.  But if the ALSA driver for another card
has already been loaded, then the ASI card will get the next available ALSA card
index instead.

> ... proposed install locations for user lib and include files

Good idea.
how about /usr/include/asihpi/hpi.h

(thinking maybe /hpi/ is not distinctive enough.

- Eliot

Eliot Blennerhassett
AudioScience Inc.
--
Junk footer beyond this point. Read at your own risk.


-------------------------------------------------------------
Sign up for ICQmail at http://www.icq.com/icqmail/signup.html


-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php

Re: AudioScience driver

[Takashi Iwai]

At Wed, 25 Jun 2003 14:58:23 -0700 (PDT),
Eliot Blennerhassett wrote:
> 
> > ... proposed install locations for user lib and include files
> 
> Good idea.
> how about /usr/include/asihpi/hpi.h

well, assuming the certain header location is not recommended.

basically, the kernel sources must not refer to the standard header
files for user-space.  if you need a header file for the kernel,
include it in the kernel tree.  or, more easily, specify the header
path explicitly with -I option in Makefile (which may be given by the
configure script).


Takashi


-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01

Re: AudioScience driver

[Fred Gleason]

On Monday 30 June 2003 09:26, Takashi Iwai wrote:

> > Good idea.
> > how about /usr/include/asihpi/hpi.h
>
> well, assuming the certain header location is not recommended.
>
> basically, the kernel sources must not refer to the standard header
> files for user-space.  if you need a header file for the kernel,
> include it in the kernel tree.  or, more easily, specify the header
> path explicitly with -I option in Makefile (which may be given by the
> configure script).

Then perhaps '/usr/include/linux/hpi.h'.  

Cheers!


|-------------------------------------------------------------------------|
|      Frederick F. Gleason, Jr.      |         Salem Radio Labs          |
|       Voice: 1-(540)-341-2880       |      87 Lee Highway, Suite 11     |
|        FAX: 1-(540)-341-7176        |        Warrenton, VA 20186        |
|-------------------------------------------------------------------------|
| When you say 'I wrote a program that crashed Windows', people stare     |
| at you and say 'Hey, I got those with the system, *for free*'.          |
|                                         -- Linus Torvalds               |
|-------------------------------------------------------------------------|




-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01

Re: AudioScience driver

[Takashi Iwai]

At Tue, 1 Jul 2003 16:52:48 -0400,
Fred Gleason wrote:
> 
> On Monday 30 June 2003 09:26, Takashi Iwai wrote:
> 
> > > Good idea.
> > > how about /usr/include/asihpi/hpi.h
> >
> > well, assuming the certain header location is not recommended.
> >
> > basically, the kernel sources must not refer to the standard header
> > files for user-space.  if you need a header file for the kernel,
> > include it in the kernel tree.  or, more easily, specify the header
> > path explicitly with -I option in Makefile (which may be given by the
> > configure script).
> 
> Then perhaps '/usr/include/linux/hpi.h'.  

the problem is that you cannot assume that the driver source accepts
the "standard" header-file locations, namely, /usr/include, etc.
these locations should not be referred by the kernel sources. 
all header files for the kernel codes should be private.

in the case of alsa-driver package, this is not strictly prohibited.
but it's better to avoid assume the fixed location.

so, as i suggested, it's better to have an option, such as

	% ./configure --with-hpi=/usr/local/src/hpi

so that the configure script can check the location of hpi.h and
enable the compilation of asihpi driver only when it's found.

i have no objection to /usr/include/asihpi/hpi.h, btw.  it's just the
matter of alsa-driver side.


Takashi


-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01