From: linas@austin.ibm.com
To: Tim Seufert <tas@mindspring.com>
Cc: Stefan Jeglinski <jeglin@4pi.com>, linuxppc-dev@lists.linuxppc.org
Subject: Re: OT: wanting to write PCI daemon
Date: Wed, 9 Jul 2003 10:22:20 -0500 [thread overview]
Message-ID: <20030709102220.A40374@forte.austin.ibm.com> (raw)
In-Reply-To: <DAD09CD5-B1C0-11D7-8101-003065F22EAA@mindspring.com>; from tas@mindspring.com on Tue, Jul 08, 2003 at 08:53:09PM -0700
On Tue, Jul 08, 2003 at 08:53:09PM -0700, Tim Seufert wrote:
>
> On Tuesday, July 8, 2003, at 03:46 PM, Stefan Jeglinski wrote:
> > We then just need a)
> > to talk TCP/IP out the one end, and b) PCI on the other.
??
tcpip has the concept of sockets and ports. Maybe you mean 'udp'?
Do you need to forward *all* internet traffic, or just some of it?
Not everything on an ethernet cable is tcpip; there's a whole zoo
of protocols that one typically sees on a LAN.
> (Though I'm not sure whether it would be a good idea to use an existing
> daemon as anything beyond sample code to see how real live TCP/IP
> communications work.
Agreed. The standard unix programming interfaces are not that hard.
You can write a simple daemon yourself with a few dozen lines of code.
(and less if you're clever). After that, its all custom, app-specific
code. I think you need a good book w/ examples in it.
--linas
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2003-07-09 15:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-08 22:46 OT: wanting to write PCI daemon Stefan Jeglinski
2003-07-09 3:53 ` Tim Seufert
2003-07-09 7:52 ` Giuliano Pochini
2003-07-09 14:20 ` Stefan Jeglinski
2003-07-09 14:58 ` Giuliano Pochini
2003-07-09 15:42 ` Stefan Jeglinski
2003-07-09 22:48 ` Tim Seufert
2003-07-09 14:22 ` Stefan Jeglinski
2003-07-09 15:22 ` linas [this message]
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=20030709102220.A40374@forte.austin.ibm.com \
--to=linas@austin.ibm.com \
--cc=jeglin@4pi.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=tas@mindspring.com \
/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).