9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Tim Newsham <newsham@lava.net>
To: 9fans@cse.psu.edu
Subject: [9fans] docs vs code
Date: Thu,  6 Jan 2005 10:23:32 -1000	[thread overview]
Message-ID: <Pine.BSI.4.58.0501061018470.10670@malasada.lava.net> (raw)

Looks like the documents and the code are out of synch on this.
On windows using the 79c970 (which shares common ethernet code
with all the windows drivers) the driver doesnt behave in the same
way as documented in the manual.

The manual says setting the type to "1" should receive all packets.
If I set the type to 1 and read, I get nothing.

The manual says that if multiple connections are of the same type,
duplicates get sent to all readers.  However, the driver seems to
only allow one connection to be bound to a given type before returning
"device or object already in use."

Tim N.


             reply	other threads:[~2005-01-06 20:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-06 20:23 Tim Newsham [this message]
2005-01-06 21:06 ` Charles Forsyth
2005-01-07  1:22   ` Tim Newsham
2005-01-13  0:31     ` Russ Cox
2005-01-13  3:00       ` Thomas

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=Pine.BSI.4.58.0501061018470.10670@malasada.lava.net \
    --to=newsham@lava.net \
    --cc=9fans@cse.psu.edu \
    /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).