NetBSD Problem Report #8642

Received: (qmail 1659 invoked from network); 18 Oct 1999 10:09:29 -0000
Message-Id: <xofyad1dlpu.fsf@blubb.pdc.kth.se>
Date: 18 Oct 1999 12:09:17 +0200
From: joda@pdc.kth.se (Johan Danielsson)
To: cgd@netbsd.org (Chris G. Demetriou)
Cc: gnats-bugs@gnats.netbsd.org,  netbsd-bugs@netbsd.org
In-Reply-To: cgd@netbsd.org's message of "16 Oct 1999 18:32:39 -0700"
Subject: Re: there is no cardbus attachment for the com driver
References: <xofoge0sja6.fsf@blubb.pdc.kth.se> <87d7uehivc.fsf@redmail.netbsd.org>

>Number:         8642
>Category:       pending
>Synopsis:       Re: there is no cardbus attachment for the com driver
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    gnats-admin
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Oct 18 03:12:00 +0000 1999
>Closed-Date:    Sun Oct 31 07:50:15 +0000 1999
>Last-Modified:  Sun Oct 31 07:50:33 +0000 1999
>Originator:     
>Release:        
>Organization:
>Environment:
>Description:
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: cgd 
State-Changed-When: Sun Oct 31 00:50:15 PDT 1999 
State-Changed-Why:  
mis-filed reply to PR#8632. 
>Unformatted:
 cgd@netbsd.org (Chris G. Demetriou) writes:

 > This is not right.

 I agree, but the puc-style `here we have a long list of cards that we
 know about' isn't very pretty either. Guessing that a random serial
 card is based on something that is 16x50 compatible is probably not
 too far from the truth (and this is what puc does too). A negative
 match might be more useful (cards that we know to be non-functional).

 > (2) COMMUNICATIONS/MODEM (0x03) has several programming interfaces
 > which are standardized to provide 16x50-compatible device via the
 > BAR @ 0x10.  You should take them into account.

 Sure.

 > Who's to say it'll be I/O?  At the very least, the PCI 2.2 spec
 > specifically indicates (on page 261) that the 16x50-compatible
 > COMMUNICATIONS/MODEM devices mapped via the BAR @ 0x10 may be in
 > either memory OR I/O space.

 We should get this information from CIS.

 /Johan

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.