From owner-freebsd-hackers  Wed Sep 25 01:05:09 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id BAA04482
          for hackers-outgoing; Wed, 25 Sep 1996 01:05:09 -0700 (PDT)
Received: from relay.philips.nl (ns.philips.nl [130.144.65.1])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA04435
          for <freebsd-hackers@freebsd.org>; Wed, 25 Sep 1996 01:05:04 -0700 (PDT)
Received: (from smap@localhost) by relay.philips.nl (8.6.9/8.6.9-950414) id KAA19597; Wed, 25 Sep 1996 10:04:39 +0200
Received: from unknown(192.26.173.32) by ns.philips.nl via smap (V1.3+ESMTP) with ESMTP
	id sma019481; Wed Sep 25 10:03:58 1996
Received: from spooky.lss.cp.philips.com (spooky.lss.cp.philips.com [130.144.199.105]) by smtp.nl.cis.philips.com (8.6.10/8.6.10-0.9z-02May95) with ESMTP id KAA24093; Wed, 25 Sep 1996 10:06:48 +0200
Received: (from guido@localhost) 
	by spooky.lss.cp.philips.com (8.6.10/8.6.10-0.991c-08Nov95) id KAA02127; Wed, 25 Sep 1996 10:03:26 +0200
From: Guido van Rooij <Guido.vanRooij@nl.cis.philips.com>
Message-Id: <199609250803.KAA02127@spooky.lss.cp.philips.com>
Subject: Re: new if_vx driver in incoming on freefal
To: nao@sbl.cl.nec.co.jp (Naoki Hamada)
Date: Wed, 25 Sep 1996 10:03:23 +0200 (MET DST)
Cc: Guido.vanRooij@nl.cis.philips.com, freebsd-hackers@freebsd.org
Reply-To: Guido.vanRooij@nl.cis.philips.com
In-Reply-To: <199609250745.QAA04292@sirius.sbl.cl.nec.co.jp> from Naoki Hamada at "Sep 25, 96 04:45:52 pm"
X-Mailer: ELM [version 2.4ME+ PL19 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Naoki Hamada wrote:
> Guido wrote:
> >With this driver the 'hanging card in OACTIVE' should b fixed without
> >the gross hack I introduced earlier. I am planning to implement a fix
> >for the early revision adapters. These are not identified by my driver,
> >but the old (original if_vx)  way of identifying them was *correct*.
> 
> No. When the old vx driver attempt to read the EEPROM_SOFT_INFO_2
> register, 'WINDOW 2' is selected instead of the right 'WINDOW 0'. Then
> the driver reports that all the adapters are defective, which is not
> the truth :-<

Oops you're right. Know what: I'll put in the correct test on upload
it directly.

-Guido