9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Ethernet card recogition -- Farallon Enet (3C589) -- kernel lines?
Date: Mon,  5 Jan 2009 16:08:07 -0500	[thread overview]
Message-ID: <36542ebc5431acafc96c929365d3456e@quanstro.net> (raw)
In-Reply-To: <95ce15640901050935j2431f71pae7bbb6e979e577a@mail.gmail.com>

> According to the Plan9 wiki, the above results indicate that recognition for
> this card isn't built into the kernel, which leads me to my main question:

alternately, the card was not detected.

> What modification(s), if any, would I need to make to the kernel config file
> (9pcf)? This card type is referenced under the "link" section, but would I
> also need to reference it under dev, or modify the line "ether   netif" in
> that section?

no, you just need to add it in the link section.  the dev section is for
devices and some special magic turns "fu" in the device section into
a request to compile devfu.c into devfu.8 and does what's required
to link the device into devtab.  the stuff in the link section is just
called at boot time.  addetherdevice is the hook to link controllers.
which are then called back by the ethernet device when it's ready.

the ether netif line declares a device devether that requires the
netif support file.

- erik



  reply	other threads:[~2009-01-05 21:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-05 17:35 James Deagle
2009-01-05 21:08 ` erik quanstrom [this message]
2009-01-06 20:09 ` [9fans] Ethernet card recogition -- Farallon Enet (3C589) -- kernel blstuart
2009-01-06 20:58   ` James Deagle
2009-01-06 21:50     ` [9fans] Ethernet card recogition -- Farallon Enet (3C589) -- blstuart

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=36542ebc5431acafc96c929365d3456e@quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).