Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 6 Nov 2000 02:29:19 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 6 Nov 2000 02:28:59 -0500 Received: from waste.org ([209.173.204.2]:50209 "EHLO waste.org") by vger.kernel.org with ESMTP id ; Mon, 6 Nov 2000 02:28:56 -0500 Date: Mon, 6 Nov 2000 01:28:45 -0600 (CST) From: Oliver Xymoron To: David Woodhouse cc: Keith Owens , linux-kernel@vger.kernel.org Subject: Re: Persistent module storage [was Linux 2.4 Status / TODO page] In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 6 Nov 2000, David Woodhouse wrote: > On Mon, 6 Nov 2000, Oliver Xymoron wrote: > > > Hopefully not. The standard examples (mixer levels, etc) are better > > handled with a userspace tool hooked by modprobe. This even gets > > persistence across reboots if that's what's wanted. > > Implement a way for a userspace tool to get the correct mixer levels in > place at the time the sound hardware is reset, so there are no glitches in > the levels, and I'll agree with you. If I understand you correctly: process 1 process 2 open(/dev/dsp) modprobe-> load module init module (can't remember which context, actually) start writing set mixer levels Is there any reason we ever want to unblock process 1 before process 2 terminates? -- "Love the dolphins," she advised him. "Write by W.A.S.T.E.." - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/