From owner-freebsd-doc Mon Feb 4 11:27: 5 2002 Delivered-To: freebsd-doc@freebsd.org Received: from mail3.svr.pol.co.uk (mail3.svr.pol.co.uk [195.92.193.19]) by hub.freebsd.org (Postfix) with ESMTP id C65A437B430 for ; Mon, 4 Feb 2002 11:26:54 -0800 (PST) Received: from [195.92.168.141] (helo=tmailb1.svr.pol.co.uk) by mail3.svr.pol.co.uk with esmtp (Exim 3.13 #0) id 16XolR-0005G7-00 for doc@freebsd.org; Mon, 04 Feb 2002 19:26:53 +0000 Received: from modem-1974.wolf.dialup.pol.co.uk ([217.134.87.182] helo=chrysalis) by tmailb1.svr.pol.co.uk with smtp (Exim 3.13 #0) id 16XolP-0006J0-00 for doc@FreeBSD.org; Mon, 04 Feb 2002 19:26:52 +0000 Message-ID: <001901c1adb1$f98145e0$0437a8c0@juice.eu.org> From: "James McGuire" To: Subject: ISDN ASUSCOM P-IN100-ST-D Card not compatible Date: Mon, 4 Feb 2002 19:27:23 -0000 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0016_01C1ADB1.F8DAF3C0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=_NextPart_000_0016_01C1ADB1.F8DAF3C0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Below is a copy of an email I was forwarded from ASUSCOM after reading = that the P-IN100-ST-D was on your compatibility list. And then later, = coming to realise it didn't appear in dmesg, and doing a ``pciconf -lv'' = only to be returned with: none0@pci0:5:0: class=3D0x028000 card=3D0x17040675 chip=3D0x06751043 = rev=3D0x02 hdr=3D0x00 vendor =3D 'Asustek Computer Inc.' device =3D 'HFC-S PCI A Cologne Chip' class =3D network Here is the email: Our P-IN-100-ST series have two kinds of chipset, one is the winbond w6692 chip and the other is the HFC cologne chip. All of the two kinds of card have support the Linux. Attached is one of our driver's document, please reference it. (This driver is fix the Linux kernel can't install the winbond based = card successful, the HFC based should not need any further driver) Regards, I'll summarise, they've stopped making these cards with winbond = chipsets, your ISDN documentation NEEDS updating. Regards James ------=_NextPart_000_0016_01C1ADB1.F8DAF3C0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Below is a copy of an email I was = forwarded from=20 ASUSCOM after reading that the P-IN100-ST-D was on your compatibility = list. And=20 then later, coming to realise it didn't appear in dmesg, and doing a = ``pciconf=20 -lv'' only to be returned with:

none0@pci0:5:0:=20 class=3D0x028000 card=3D0x17040675 chip=3D0x06751043 rev=3D0x02=20 hdr=3D0x00
    vendor   =3D 'Asustek = Computer=20 Inc.'
    device   =3D 'HFC-S PCI A Cologne=20 Chip'
    class    =3D = network

Here is the email:

Our P-IN-100-ST series have two kinds of=20 chipset,

one is the winbond w6692 chip and = the other=20 is the HFC cologne chip.

All of the two kinds of card have support = the=20 Linux.

Attached is one of our driver's document, = please=20 reference it.

(This driver is fix the Linux kernel can't = install the=20 winbond based card successful,

the HFC based should not need any = further=20 driver)

Regards,

I'll summarise, they've stopped making = these cards=20 with winbond chipsets, your ISDN documentation NEEDS = updating.

Regards

James

------=_NextPart_000_0016_01C1ADB1.F8DAF3C0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message