NetBSD Problem Report #8261

Received: (qmail 11029 invoked from network); 24 Aug 1999 06:18:30 -0000
Message-Id: <199908240608.PAA00609@rerun.tenjin.org>
Date: Tue, 24 Aug 1999 15:08:04 +0900 (JST)
From: kawamoto@tenjin.org
Reply-To: kawamoto@tenjin.org
To: gnats-bugs@gnats.netbsd.org
Cc: kawamoto@tenjin.org
Subject: pcmcia ether card information: Contec C-NET(PC)C
X-Send-Pr-Version: 3.95

>Number:         8261
>Category:       kern
>Synopsis:       pcmcia ether card information: Contec C-NET(PC)C
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    kern-bug-people
>State:          closed
>Class:          support
>Submitter-Id:   net
>Arrival-Date:   Mon Aug 23 23:20:00 +0000 1999
>Closed-Date:    Tue Aug 24 17:54:30 +0000 1999
>Last-Modified:  Tue Aug 24 17:54:50 +0000 1999
>Originator:     Kawamoto Yosihisa
>Release:        1999/08/23
>Organization:
tenjin.org
>Environment:
	note pc (SONY VAIO 505RX)
System: NetBSD rerun.tenjin.org 1.4K NetBSD 1.4K (RERUN) #212: Tue Aug 24 12:39:38 JST 1999 kawamoto@rerun.tenjin.org:/usr/src/sys/arch/i386/compile/RERUN i386


>Description:
	  The Contec C-NET(PC)C is MB8696x based pcmcia ethernet card.
	This card is recognizd by following patches.
	  These patches have a ploblem.  The product id of C-NET(PC)C
	is defined to 0.  This may be illegal, but CIS string is more
	illegal, I think:-P  The following system messages show the
	CIS string.  The MSB enabled 5 chars are Japanese string
	coded in MS-Kanji.
	  I never want to describe Japanese strings in device list,
	so some mechanisms like a wild card pattern matching may be
	needed.

pcmcia0: CIS version PCMCIA 2.0 or 2.1
pcmcia0: CIS info: CONTEC Co.,Ltd., C-NET(PC)C\M-<\M-X\M-0\M-=\M-^
pcmcia0: Manufacturer code 0xc001, product 0x0
pcmcia0: function 0: network adapter, ccr addr 800 mask 3
pcmcia0: function 0, config table entry 1: I/O card; irq mask def8; iomask 4, iospace 0; memspace 0; powerdown
mbe0 at pcmcia0 function 0 port 0x330-0x33f: Contec C-NET(PC)C

>How-To-Repeat:
>Fix:
diff -cr /base/src/sys/dev/pcmcia/if_mbe_pcmcia.c ./if_mbe_pcmcia.c
*** /base/src/sys/dev/pcmcia/if_mbe_pcmcia.c	Tue Jun 29 09:05:09 1999
--- ./if_mbe_pcmcia.c	Tue Aug 24 14:33:03 1999
***************
*** 105,110 ****
--- 105,114 ----
  	  PCMCIA_STR_TDK_LAK_DFL9610 }
  #endif

+ 	{ PCMCIA_VENDOR_CONTEC,		PCMCIA_PRODUCT_CONTEC_CNETPC,
+ 	  0,				0,
+ 	  PCMCIA_STR_CONTEC_CNETPC },
+ 
  	{ PCMCIA_VENDOR_FUJITSU,	PCMCIA_PRODUCT_FUJITSU_LA501,
  	  0,				0x20,
  	  PCMCIA_STR_FUJITSU_LA501 },
diff -cr /base/src/sys/dev/pcmcia/pcmciadevs ./pcmciadevs
*** /base/src/sys/dev/pcmcia/pcmciadevs	Sun Aug 15 20:17:25 1999
--- ./pcmciadevs	Tue Aug 24 14:36:21 1999
***************
*** 60,65 ****
--- 60,66 ----
  vendor IODATA			0x01bf	I-O DATA
  vendor LASAT			0x3401	Lasat Communications A/S
  vendor COMPEX			0x8a01	Compex Corporation
+ vendor CONTEC			0xc001	Contec
  vendor COREGA			0xc00f	Corega K.K.
  vendor HAGIWARASYSCOM		0xc012	Hagiwara SYS-COM

***************
*** 154,159 ****
--- 155,163 ----
  /* Standard Microsystems Corporation Products */
  product SMC 8016		0x0105 SMC 8016 EtherCard
  product SMC EZCARD		0x8022 SMC EXCard 10 PCMCIA
+ 
+ /* Contec C-NET(PC) */
+ product CONTEC CNETPC		0x0000 Contec C-NET(PC)C

  /* Lucent WaveLAN/IEEE */
  product LUCENT WAVELAN_IEEE	0x0002	WaveLAN/IEEE
>Release-Note:
>Audit-Trail:

From: christos@zoulas.com (Christos Zoulas)
To: kawamoto@tenjin.org, kern-bug-people@netbsd.org,
        gnats-bugs@gnats.netbsd.org, gnats@netbsd.org (GNATS Management)
Cc:  Subject: Re: kern/8261: pcmcia ether card information: Contec C-NET(PC)C
Date: Tue, 24 Aug 1999 09:15:58 -0400

 On Aug 24,  3:08pm, kawamoto@tenjin.org (kawamoto@tenjin.org) wrote:
 -- Subject: kern/8261: pcmcia ether card information: Contec C-NET(PC)C

 | 	  The Contec C-NET(PC)C is MB8696x based pcmcia ethernet card.
 | 	This card is recognizd by following patches.
 | 	  These patches have a ploblem.  The product id of C-NET(PC)C
 | 	is defined to 0.  This may be illegal, but CIS string is more
 | 	illegal, I think:-P  The following system messages show the
 | 	CIS string.  The MSB enabled 5 chars are Japanese string
 | 	coded in MS-Kanji.
 | 	  I never want to describe Japanese strings in device list,
 | 	so some mechanisms like a wild card pattern matching may be
 | 	needed.

 Well, as long as the vendor code is non zero, it will not cause problems.
 As far as them using product 0, I suspect it is ok, as long as the
 start to use other values for different products. If they don't
 we can switch to use pmatch()...

 christos
State-Changed-From-To: open->closed 
State-Changed-By: tron 
State-Changed-When: Tue Aug 24 10:54:30 PDT 1999 
State-Changed-Why:  
Patch applied, thanks. 
>Unformatted:

NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.51 2026/08/10 02:28:17 riastradh Exp $
$NetBSD: gnats_config.sh,v 1.10 2026/05/13 22:00:09 riastradh Exp $
Copyright © 1994-2026 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.