Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Davis <pbd@op.net>
To: Ivica Bukvic <ico@fuse.net>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: HDSP -- how to configure modules.conf?
Date: Wed, 15 May 2002 18:24:10 -0400	[thread overview]
Message-ID: <E1787AL-00007A-00@usw-sf-list1.sourceforge.net> (raw)
In-Reply-To: Your message of "Wed, 15 May 2002 17:38:19 EDT." <000201c1fc58$d4c73070$ac1f830a@ico>

>> How did you compile? I mean right from the very beginning ... I've
>> obviously been building from CVS all along, and I assume that Jaroslav
>> did a rebuild after he committed the changes.
>> 
>> --p
>
>Thank you for your continuous help!

well, after some more digging, it seems that the problem is the
acinclude file in alsa-driver, which is what defines the list of cards
that exist and sets them up to be compiled.

i believed that it was stored in CVS, but it apparently is not. it
needs modifications that i believe i sent to jaroslav, but because its
not in CVS, i did not ("cvs -z3 diff" didn't notice it).

instead, it seems that acinclude is built from several files called
Module.deps by a utility call mod-deps. i don't understand when its
built. 

jaroslav or takashi or someone who understands how this works: would
you please modify Modules.dep or whatever needs to be done to fix this
issue? the existing Modules.dep file doesn't contain entries for the
H-DSP, and it continue to name snd-rme9652-mem, rather than
snd-hammerfall-mem. 

it worked for me because i had edited acinclude by hand, and for some
reason that i don't understand it was never rebuilt by the automated
process (which would have removed the hdsp entries, i think).

--p


_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: bandwidth@sourceforge.net

  reply	other threads:[~2002-05-15 22:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20020515172558.KHLI981.mta02.fuse.net@newmx1.fast.net>
2002-05-15 21:38 ` HDSP -- how to configure modules.conf? Ivica Bukvic
2002-05-15 22:24   ` Paul Davis [this message]
2002-05-15  0:02 Failed to compile HDSP driver from the CVS Paul Davis
2002-05-15  2:11 ` HDSP -- how to configure modules.conf? Ivica Bukvic
2002-05-15 12:41   ` Paul Davis
2002-05-15 17:22     ` Ivica Bukvic
2002-05-15 17:27       ` Paul Davis

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=E1787AL-00007A-00@usw-sf-list1.sourceforge.net \
    --to=pbd@op.net \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=ico@fuse.net \
    /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