From: erik quanstrom <quanstro@coraid.com>
To: 9fans@cse.psu.edu
Subject: [9fans] rtl8169 funny.
Date: Thu, 13 Dec 2007 13:48:05 -0500 [thread overview]
Message-ID: <de9aecf6d8002009d6648662c2061863@coraid.com> (raw)
i've been working on getting cec in 9load and that's working.
the target machine broadcasts an offer of connection. the
client knows to reconnect. thus one can reboot a server,
talk to 9load, start plan 9 and connect to it. not as
easy as serial, but it doesn't require serial and is much faster.
ideally the offer happens before ipconfig/auth have done
their magic so early boot configuration may be entered.
unfortunately, the rtl8169 seems to eat packets before the
initial arp and the client doesn't ever get the offer. the
intel pcie intel nics (ether82563.c) seem not to suffer this fate.
has anyone else seen this sort of problem with the 8169?
- erik
reply other threads:[~2007-12-13 18:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=de9aecf6d8002009d6648662c2061863@coraid.com \
--to=quanstro@coraid.com \
--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).