From: Roberto De Leo <deleo@unica.it>
To: alsa-devel@lists.sourceforge.net
Subject: AWE ISA correction + a new question
Date: Thu, 06 Mar 2003 14:32:41 +0000 [thread overview]
Message-ID: <3E675C09.4010609@unica.it> (raw)
Hi,
the user that had reported a code CTL00e3 told me that he had made a
mistake and that the code was actually CTL00c3, so the problem
disappeared. Sorry about that!
Still, I have a question about the isa cards autodetection.
I first tried the isapnpmodules.c program but for some reason it was
unable to detect anything.
At that point, I wrote the following shell script modifying a similar
script I found for pci modules:
<----------------------------------------------------
##############################################
# Detect & load ISA modules #
##############################################
get_isapnp_modules () {
while read IGNORE ID IGNORE
do
DEVICE="0x"`echo $ID | cut -b6-7``echo $ID | cut -b4-5`
cat /lib/modules/`uname -r`/modules.isapnpmap | awk "{ if (
\$3 ~ /$DEVICE/ ) print \$1 }"
done
}
for MODULE in `get_isapnp_modules < /proc/bus/isapnp/devices | sort -u`
do echo Loading module $MODULE
modprobe $MODULE
done
----------------------------------------------------->
I know the script is not very clean, I far from being an expert :-)
My question is: does this script seem to you good for identifying the
isapnp card modules?
I tried on a PC with a "CTL00e4" ISA AWE card but for some odd reason it
seems not to work on the PC of the user with the "CTL00c3" ISA AWE card.
Incidentally, why the exadecimal pairs identifying the card are switched
in /proc/bus/isapnp/devices and modules.isapnpmap?
Thanks and sorry again for the previous mistake,
Roberto De Leo
-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger
for complex code. Debugging C/C++ programs can leave you feeling lost and
disoriented. TotalView can help you find your way. Available on major UNIX
and Linux platforms. Try it free. www.etnus.com
reply other threads:[~2003-03-06 14:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3E675C09.4010609@unica.it \
--to=deleo@unica.it \
--cc=alsa-devel@lists.sourceforge.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 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.