From: Takashi Iwai <tiwai@suse.de>
To: Paul Davis <paul@linuxaudiosystems.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: hdsp driver
Date: Mon, 03 Mar 2003 18:08:30 +0100 [thread overview]
Message-ID: <s5h7kbggyy9.wl@alsa2.suse.de> (raw)
In-Reply-To: <20030303165638.2893E14801@Cantor.suse.de>
At Mon, 03 Mar 2003 11:59:56 -0500,
Paul Davis wrote:
>
> >> they aren't. that's the whole problem. on my old system (148MB of
> >> RAM), allowing fsck to run would prevent memory allocation. i don't
> >> know of any distribution that inserts modules that early. do you?
> >
> >aha, but fsck runs even before snd-hammerfall-mem, doesn't it? (unless
> >you bulit it in kernel) otherwise it's dangerous...
>
> no. absolutely not. i just added something equivalent to this to
> /etc/rc.d/rc.sysinit, right before fsck runs.
>
> insmod snd-hammerfall-mem
>
> since snd-hammerfall-mem has nothing to do with filesystems on disk,
> there is no danger.
as long as the snd-hammerfall-mem module itself on the filesystem is
not broken. it may happen not rarely if the filesystem crashed just
after (or during) installing the new module files.
> many other hammerfall users are doing equivalent
> things, and its also necessary under windows and macos.
> >now i understood the necessity of the allocation way of
> >snd-hammerfall-mem. we can merge the feature but it will be likely
> >after 0.9.0, as long as the old style works. i'd like to concentrate
> >on bug fixes now.
>
> as long as you propose to leave snd-hammerfall-mem in
> place.
> otherwise, you will make it impossible for many people to use
> their audio interfaces!
don't worry, it's been still there. no changes regarding snd-hf-mem
without asking you :)
Takashi
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2003-03-03 17:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-27 18:43 hdsp driver Paul Davis
2003-02-28 15:14 ` Takashi Iwai
2003-03-03 16:11 ` Paul Davis
[not found] ` <20030303160758.C8AD014ECB@Cantor.suse.de>
2003-03-03 16:12 ` Takashi Iwai
2003-03-03 16:37 ` Paul Davis
[not found] ` <20030303163402.5154214599@Cantor.suse.de>
2003-03-03 16:40 ` Takashi Iwai
2003-03-03 16:59 ` Paul Davis
[not found] ` <20030303165638.2893E14801@Cantor.suse.de>
2003-03-03 17:08 ` Takashi Iwai [this message]
2003-03-03 19:11 ` Paul Davis
2003-03-02 20:24 ` Thomas Charbonnel
2003-03-02 23:43 ` [PATCH] HDSP rms and peak registers correct offsets (was: Re: hdsp driver) Thomas Charbonnel
2003-03-03 14:23 ` [PATCH] HDSP rms and peak registers correct offsets (was: driver) Mark Knecht
2003-03-03 14:40 ` Thomas Charbonnel
2003-03-03 15:52 ` [PATCH] HDSP rms and peak registers correct offsets (was:Re:hdsp driver) Mark Knecht
2003-03-03 14:55 ` [PATCH] HDSP rms and peak registers correct offsets (was: Re: hdsp driver) Thomas Charbonnel
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=s5h7kbggyy9.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=paul@linuxaudiosystems.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 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.