From owner-freebsd-multimedia Wed Dec 8 6:10:14 1999 Delivered-To: freebsd-multimedia@freebsd.org Received: from fleming.cs.strath.ac.uk (fleming.cs.strath.ac.uk [130.159.196.126]) by hub.freebsd.org (Postfix) with ESMTP id BC5A615538 for ; Wed, 8 Dec 1999 06:10:09 -0800 (PST) (envelope-from roger@cs.strath.ac.uk) Received: from muir-10 (roger@muir-10.cs.strath.ac.uk [130.159.148.10]) by fleming.cs.strath.ac.uk (8.8.8/8.8.8) with SMTP id OAA07576 Wed, 8 Dec 1999 14:09:48 GMT Message-ID: <384E66AB.167E@cs.strath.ac.uk> Date: Wed, 08 Dec 1999 14:09:47 +0000 From: Roger Hardiman Organization: University of Strathclyde X-Mailer: Mozilla 3.04Gold (X11; I; OSF1 V4.0 alpha) MIME-Version: 1.0 To: Chris Csanady , "Kenneth D. Merry" , Randy Bush Cc: multimedia@freebsd.org Subject: bktr driver changes Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-multimedia@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi there. Well, I've noticed that the three people who reported the bktr driver in -current being broken are all NTSC users. Previously I had suspected motherboard chipsets and/or slow CPUs but it looks like NTSC is the common factor to you all. So, as a stop-gap, I've backed out the changes made to bktr_core 1.102. There is a new bktr_core 1.103 which is actually the 1.101 code. So, please can you CVSup and check that things are working for you once again. Of course, we still need to fix the bug. I've made the NTSC users happy, but I've lost some of the functionality form 1.102 which made life better for PAL users. Roger -- Roger Hardiman | Telepresence Research Group roger@cs.strath.ac.uk | DMEM, University of Strathclyde tel: 0141 548 2897 | Glasgow, Scotland, G1 1XJ, UK fax: 0141 552 0557 | http://www.telepresence.strath.ac.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message