Subject: RE: Farallon PhoneNet Support
To: Port-Mac68k@Netbsd. Org <port-mac68k@netbsd.org>
From: None <brad@baileylink.net>
List: port-mac68k
Date: 09/25/1999 14:26:02
Hello Allen,
Thank you for arming me with the information that I need to get started.

I do have this card working in MacOS, I believe that I can get the RAM, ROM
and Control memory addresses with TechTool.  I will confirm tomorrow.  Does
anyone have more ideas on getting these numbers from another source (maybe
Farallon?).  I assume that these "addresses" are actually offsets from some
address that the kernel can determine for the card.  Is this correct?  If
not how do you support more than one card in a machine (I intend on this
computer being a router box).

Thank you all for your input,

BMG



-----Original Message-----
From: port-mac68k-owner@netbsd.org
[mailto:port-mac68k-owner@netbsd.org]On Behalf Of Allen Briggs
Sent: Friday, September 24, 1999 7:49 AM
To: Brad Guillory
Cc: Bill Studenmund; brad@baileylink.net; port-mac68k@netbsd.org
Subject: Re: Farallon PhoneNet Support


> nubus0 slot e: PhoneNET® IIN (Vendor: Farallon Computing, Inc., Part: ???)
Type:
>  0004 0001 0108 0100 not configured
> slot_noint() slot e

It looks like your PhoneNET card is generating interrupts that we aren't
handling.  Do you know (or does anyone on the list know) if the PhoneNET
cards need any extra programming support, or do they look exactly like
ethernet to the driver?

If you add the constants 0x0108 and 0x0100 (DrSW & DrHW) to the nubus.h
file and add the proper code in if_ae_nubus.c (ae_nb_car_vendor() and
possibly ae_nubus_match/_attach(), the card will no longer say, "not
configured".  The hard part might be to find the proper RAM, ROM, and
control memory addresses for the card.  If you're lucky, the PhoneNET
card uses the same addresses as the other Farallon card (which has
DrSW 0x010C, which is different from 0x0108, meaning that they chose to
make a distinction between this and another ethernet card).  DrSW is
supposed to identify the driver that is needed for the device whereas
DrHW differentiates different hardware revisions/types within a driver.
We do it somewhat differently, obviously, and use the same driver for
a number of different DrSWs.

-allen