Return to BSD News archive
Newsgroups: comp.os.386bsd.questions
Path: sserve!newshost.anu.edu.au!munnari.oz.au!bunyip.cc.uq.oz.au!news.qut.edu.au!orac.crissp.qut.edu.au!reilly
From: reilly@orac.crissp.qut.edu.au (Andrew Reilly)
Subject: Re: Devices, we0, and WD8013EP ethernet card
Message-ID: <1993May9.231041.5974@news.qut.edu.au>
Keywords: DEC EtherWORKS Turbo
Sender: news@news.qut.edu.au (USENET News System)
Reply-To: A.Reilly@qut.edu.au
Organization: Signal Processing Research Center, QUT, AUS
References: <C6rFMA.1qv@implode.rain.com>
Date: Sun, 9 May 93 23:10:41 GMT
Lines: 32
In article <C6rFMA.1qv@implode.rain.com>, davidg@implode.rain.com (David Greenman) writes:
> reilly@orac.crissp.qut.edu.au (Andrew Reilly) writes:
> ...
> >>Why doesn't the /dev/MAKEDEV script have a section to create /dev/we0?
> >>
> >>Why doesn't /sys/i386/conf/devices (?) list a major device number for
> >>we0, so that I could modify the MAKEDEV script?
> >
> >>Where would I find such a number? I'm new to device drivers...
> >>
> >>Is this even relevant? (There aren't MAKEDEV options for any of the
> >>other accepted ethernet devices, either, so maybe that's not the way
> >>it works.)
> Network
> devices aren't accessed through the bdev/cdev structure. The device is accessed
> through a special data structure for network devices (called ifnet). There
> *isn't* any /dev/we* device, nor are there any /dev/sl* devices (for SLIP).
Thanks. That clears up that mystery. Now all I need to do is get the
kernel to recognize this WD8013EP ethernet card, then everything
should be fine?
I also have access to a DEC "EtherWORKS Turbo" ethernet card, but
NetBSD doesn't support it. Does anyone have a driver for this card?
Thanks in advance,
-- Andrew Reilly -- | A.Reilly@qut.edu.au |
Signal Processing Research Centre |
QUT, GPO 2434, Brisbane 4001, Australia. |
phone: +61 7 864 2124 | fax: +61 7 864 1516 |