From owner-freebsd-arch Sat Jan 20 15:57:47 2001 Delivered-To: freebsd-arch@freebsd.org Received: from vilnya.demon.co.uk (vilnya.demon.co.uk [158.152.19.238]) by hub.freebsd.org (Postfix) with ESMTP id E666A37B400; Sat, 20 Jan 2001 15:57:27 -0800 (PST) Received: from darkstar (darkstar.rings [10.2.4.16]) by vilnya.demon.co.uk (Postfix) with SMTP id 80552D9B8; Sat, 20 Jan 2001 23:57:24 +0000 (GMT) Message-ID: <003401c0833c$39ac3f40$1004020a@darkstar> From: "Cameron Grant" To: , Subject: newpcm/kobj MFC Date: Sat, 20 Jan 2001 23:53:45 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG this is a followup to my proposal some weeks ago which recieved no relevant commentary. unless vetoed for good reason, i intend to MFC kobj support into 4.x and update newpcm to use it in the next few days. this will not affect any other subsystems apart from kernel .m file expansion which will be changed to determine whether its source file is for kobj or device ops and invoke the relevant script. this change will change the newpcm dki again so modules maintained outside the tree will require updating, but will allow many improvements including the latency improvements now present in -current, and the addition of several new drivers, along with future developments. without this change, newpcm in -stable goes into maintenence mode as i have neither time or motivation to to development in two seperate trees. silence will be interpreted as assent. -cg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message