public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Grant Edwards <grante@visi.com>
To: Gary Thomas <gthomas@cambridge.redhat.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] RedBoot: __eth_install_handler?
Date: Mon, 22 Jan 2001 12:53:00 -0000	[thread overview]
Message-ID: <20010122145740.A24763@visi.com> (raw)
In-Reply-To: <XFMail.20010122130352.gthomas@cambridge.redhat.com>

> > In RedBoot's net.h file, there's a declaration for
> > __eth_install_handler(), which would seem from the declaration to
> > do exactly what I want to do: set a call-back to handle packets
> > with Ethernet protocol type <whatever>.
> > 
> > That functionality hasn't been implemented, so I'm about to
> > implement it.  
> > 
> > Were I doing this just for myself, I would probably just use
> > CYG_HAL_TABLE_xxxx to set up handlers at compile/link time and
> > not bother with run-time handler set up.  It's a bit simpler,
> > and you don't to guess ahead of time how many different handler
> > need to be allowed.  [I really like the HAL_TABLE mechanism:
> > it's quite clever, and it's something that I've needed on a
> > number of occasions.]
> > 
> > However, if people think run-time handler set-up is useful,
> > I'll go ahead and implement the existing API instead of using
> > the HAL_TABLE method.
> 
> Setting up the handler at runtime is much better IMHO.

Done.

-- 
Grant Edwards
grante@visi.com

  reply	other threads:[~2001-01-22 12:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-22 11:54 Grant Edwards
2001-01-22 12:04 ` Gary Thomas
2001-01-22 12:53   ` Grant Edwards [this message]
2001-01-22 14:09     ` Grant Edwards
2001-01-22 14:51       ` Gary Thomas
2001-01-23  0:13         ` Andrew Lunn
2001-01-22 14:51 ` Grant Edwards
2001-01-22 15:56   ` Grant Edwards
2001-01-31  4:25   ` Gary 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=20010122145740.A24763@visi.com \
    --to=grante@visi.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=gthomas@cambridge.redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).