All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniele Orlandi <daniele@orlandi.com>
To: netdev@vger.kernel.org
Cc: netdev@oss.sgi.com
Subject: Re: Request for an ARPHRD_
Date: Mon, 24 Oct 2005 23:33:04 +0200	[thread overview]
Message-ID: <200510242333.05366.daniele@orlandi.com> (raw)
In-Reply-To: <200510241807.23290.ak@suse.de>

On Monday 24 October 2005 18:07, Andi Kleen wrote:
>
> ETH_P_* is managed by the IEEE (part of the ethernet standard) You would
> need to ask them.

I need a pseudo protocol like it is already done for some internal protocol, 
e.g.:

/*
 *      Non DIX types. Won't clash for 1500 types.
 */
[.....]
#define ETH_P_WAN_PPP   0x0007          /* Dummy type for WAN PPP frames*/
#define ETH_P_PPP_MP    0x0008          /* Dummy type for PPP MP frames */
#define ETH_P_LOCALTALK 0x0009          /* Localtalk pseudo type        */
#define ETH_P_PPPTALK   0x0010          /* Dummy type for Atalk over PPP*/
[....]

> Normally Linux doesn't pre-allocate ABIs for out of tree code, mostly
> because it is not guaranteed that the interface won't change there.

Could you clarify? What interface do you fear that could change?

My main concern is that without an ARPHRD_ constant guaranteed to be unique I 
wouldn't be able to propose a patch for libpcap people to map the (already 
allocated) DLT_ to the correct ARPHRD_.

Bye,

-- 
  Daniele Orlandi

       reply	other threads:[~2005-10-24 21:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200510240255.28416.daniele@orlandi.com>
     [not found] ` <200510241807.23290.ak@suse.de>
2005-10-24 21:33   ` Daniele Orlandi [this message]
2005-10-24 21:51     ` Request for an ARPHRD_ Lennert Buytenhek
2005-10-24 22:08       ` Daniele Orlandi
2005-10-24 22:22         ` Lennert Buytenhek
2005-10-24 22:58           ` Daniele Orlandi
2005-10-24 22:24     ` Andi Kleen

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=200510242333.05366.daniele@orlandi.com \
    --to=daniele@orlandi.com \
    --cc=netdev@oss.sgi.com \
    --cc=netdev@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.