From owner-freebsd-multimedia@FreeBSD.ORG Tue Oct 31 06:09:45 2006 Return-Path: X-Original-To: freebsd-multimedia@freebsd.org Delivered-To: freebsd-multimedia@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6E93916A412 for ; Tue, 31 Oct 2006 06:09:45 +0000 (UTC) (envelope-from kosio.dimitrov@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.186]) by mx1.FreeBSD.org (Postfix) with ESMTP id 532E643D4C for ; Tue, 31 Oct 2006 06:09:43 +0000 (GMT) (envelope-from kosio.dimitrov@gmail.com) Received: by nf-out-0910.google.com with SMTP id p77so162892nfc for ; Mon, 30 Oct 2006 22:09:42 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=CtBMvHwBYRUtYZffOCvVKpEFEl+zbd/zB9QGCDjjpF/PIWDKYwk1xPEPV0df9iXVABt4y/DVDZiGpSCi4Ct+64geht8eJGH5gq5HJjNxs2wqRdqZGuMDInO9o/MMdJeLOwf/KgCAxskyr1GwOZOiq+4n/UQhOHFHrJC/+74XYR8= Received: by 10.82.124.10 with SMTP id w10mr979752buc; Mon, 30 Oct 2006 22:09:41 -0800 (PST) Received: by 10.82.98.7 with HTTP; Mon, 30 Oct 2006 22:09:41 -0800 (PST) Message-ID: <8103ad500610302209y4f76f8c3pdc3370097f587f94@mail.gmail.com> Date: Tue, 31 Oct 2006 08:09:41 +0200 From: "Konstantin Dimitrov" To: pyunyh@gmail.com In-Reply-To: <20061031005233.GC55910@cdnetworks.co.kr> MIME-Version: 1.0 References: <200606072039.13422.shoesoft@gmx.net> <8103ad500607180035t50633780wbf585805464b8696@mail.gmail.com> <787520ee0607180732r6bcb1ae4h1591230d2db366a@mail.gmail.com> <200610111331.39605.lrntct@gmail.com> <8103ad500610111048v756778c6pcac4006746ec3f0a@mail.gmail.com> <20061028082147.GB44390@cdnetworks.co.kr> <8103ad500610291101l291c5e04xfc6874e4abda6f83@mail.gmail.com> <20061031005233.GC55910@cdnetworks.co.kr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-multimedia@freebsd.org Subject: Re: Status of VIA Envy24 audio controller X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Oct 2006 06:09:45 -0000 On 10/31/06, Pyun YongHyeon wrote: > > On Sun, Oct 29, 2006 at 09:01:30PM +0200, Konstantin Dimitrov wrote: > > sorry for my late answer, i'm too busy, but today i had some free time > to > > look at the problems. the two described problems are different and not > > related. here is the new working code: > > > > for Envy24 (fix mutex problems on current and panic on verbose boot) : > > http://envy24.svobodno.com/driver/envy24/current/envy24.c > > > > for Envy24HT(fix mutex problems on current and panic on verbose boot, > enable > > vchans): > > http://envy24.svobodno.com/driver/envy24ht/current/envy24ht.c > > http://envy24.svobodno.com/driver/envy24ht/current/envy24ht.h > > > > vchans support is now enabled in the Envy24HT code and hope it's working > ok. > > > > Thanks. It now loads ok on CURRENT but I can't hear anything. > I can't sure but I have to make a cfg_table for > "ONKYO SE-150PCI PLUS". ATM it seems that it uses generic > configuration for the hardware. I'll let you if I mananged to > make it work. you can't hear anything, because DAC on your ONKYO SE-150PCI PLUS is not initialized. Laurent Courty (lrntct at gmail.com) has ONKYO SE-90PCI and I have been trying to get it running for more than 2 weeks now, but without success and filling the cfg_table is not so easy at all, because it involves knowing the hardware specific design of the board, so the process on adding support for new unsupported card can be summarized in the following steps: 0) examine the board to see what ICs they use for DACs, ADCs, DITs, etc. 1) make EEPROM dump (i wrote small kernel module that do the job: http://www.nbritton.org/uploads/envy24/envy24_dump_v01.tar) 2) find the hardware specific design of the board (wiring between Envy24 chip and other important chips on the board like DACs) 3) fill the cfg_table and if needed write the necessary card specific code (codec init code, etc.) on the table here: http://envy24.svobodno.com , you can see all the above info for supported boards till now - ICs, EEPROM dumps, wiring info, etc. so do the steps 0) and 1) and mail me that info, then i will try to help you with 2) and 3). > On 10/28/06, Pyun YongHyeon wrote: > > > > > >On Sat, Oct 28, 2006 at 02:43:53AM -0500, Nikolas Britton wrote: > > >> Hey Konstantin, I think I found a bug in the code. If I boot FreeBSD > > >> with verbose logging the envy24 driver will panic the system during > > >> the boot process. fatal trap 12, page fault, and something about > > >> "envy24(play): setmap; xxxxx", I'd have to build a debug kernel etc. > > >> if you want the full message and backtrace but this should be easy to > > >> reproduce. I'm using envy24 sources from -CURRENT that I manually > > >> MFC'd to FreeBSD 6.2-PRERELEASE. Oh... I'm using an M Audio > Audiophile > > >> 2496. > > >> > > > > > >I saw the panic on envy24ht(4) too and sent a mail to Konstantin but > > >got no reply yet. With WITNESS enabled kernel it shows several LORs > > >and panicked due to use of recursed mutex(channel lock can't be > > >acquired recursively). I guess correct fix could be done by moving > > >buffer resizing code to channel_setblocksize method instead of > > >channel_setformat method. Unfortunately I haven't have free time > > >to investiage further due to msk(4) work and still have little time. > :-( > > > > > >-- > > >Regards, > > >Pyun YongHyeon > > > > > -- > Regards, > Pyun YongHyeon >