From owner-freebsd-isdn@FreeBSD.ORG Sun Sep 26 14:15:08 2004 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A5B5616A507 for ; Sun, 26 Sep 2004 14:15:08 +0000 (GMT) Received: from gw02.mail.saunalahti.fi (gw02.mail.saunalahti.fi [195.197.172.116]) by mx1.FreeBSD.org (Postfix) with ESMTP id E824443D45 for ; Sun, 26 Sep 2004 14:15:07 +0000 (GMT) (envelope-from jml@cubical.fi) Received: from snorkkeli.homeip.net (62-142-249-176.pp.saunalahti.fi [62.142.249.176]) by gw02.mail.saunalahti.fi (Postfix) with ESMTP id 80E711E85D; Sun, 26 Sep 2004 17:15:06 +0300 (EEST) Received: (from root@localhost) by snorkkeli.homeip.net (8.12.9p2/8.12.9) id i8QEF33C084806; Sun, 26 Sep 2004 17:15:03 +0300 (EEST) (envelope-from jml@cubical.fi) Received: from [192.168.2.252] (wazoo.koti2.net [192.168.2.252]) i8QEF0SV084795; Sun, 26 Sep 2004 17:15:00 +0300 (EEST) (envelope-from jml@cubical.fi) In-Reply-To: <20040926124720.GA39113@eyore.cobbled.net> References: <20040926124720.GA39113@eyore.cobbled.net> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Juha-Matti Liukkonen Date: Sun, 26 Sep 2004 17:17:59 +0300 To: n0g0013 X-Pgp-Agent: GPGMail 1.0.2 X-Mailer: Apple Mail (2.619) X-Virus-Scanned: by AMaViS perl-11 cc: freebsd-isdn@freebsd.org Subject: Re: driver for usr 3409 pci ta X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Sep 2004 14:15:08 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, based on the chip id, your device should map to the generic Winbond 6692 with iwic just fine. In any case, if you want to make a driver for an ISDN chip in BSD, you should probably take one of the existing i4b layer1 drivers as a base. You must implement the i4b internal l1mux interface towards the stack, which is quite different from anything "regular" drivers do. The bus probe/attach/intr functions are quite basic PCI stuff for them too, though (usually split into _.c). Br, Juha On Sep 26, 2004, at 15:47, n0g0013 wrote: > : > P.S: here is the output from pciconf -lv > none2@pci0:11:0: class=0x028000 card=0x340916ec \ > chip=0x66921050 rev=0x01 hdr=0x00 > vendor = 'Winbond Electronics Corp.' > device = 'W6692/92A/92CF PCI BusISDN S/T-Controller' > class = network > P.P.S: if this is a TA then i don't expect the iwic driver \ > will work. + the subdevice id's don't match any in the \ > source - -- Juha-Matti Liukkonen - Systems Architect, Cubical Solutions Ltd tel: +358-40-5280142 e-mail: jml@cubical.fi -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (Darwin) iD8DBQFBVs+YKDUn3bh7M9gRAhQ3AJwLRW7yR0IIHsUw6pbad/RnuQv2IgCgkdVS GbkQWAvhfVx421zJpubLxWc= =IwlJ -----END PGP SIGNATURE-----