mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stuffed Crust <pizza@shaftnet.org>
To: "David S. Miller" <davem@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] - 2.4.17 - if_arp.h - Add the Prism2 ARP type
Date: Sat, 22 Dec 2001 00:42:28 -0500	[thread overview]
Message-ID: <20011222004228.A22793@shaftnet.org> (raw)
In-Reply-To: <20011222000105.A22554@shaftnet.org> <20011221.210655.91756024.davem@redhat.com>
In-Reply-To: <20011221.210655.91756024.davem@redhat.com>; from davem@redhat.com on Fri, Dec 21, 2001 at 09:06:55PM -0800

[-- Attachment #1: Type: text/plain, Size: 1451 bytes --]

On Fri, Dec 21, 2001 at 09:06:55PM -0800, David S. Miller wrote:
>    From: Stuffed Crust <pizza@shaftnet.org>
>    Date: Sat, 22 Dec 2001 00:01:05 -0500
> 
>    Hey, this one-line patch (I diffed it against 2.4.17-rc2) defines the
>    ARPHRD_IEEE80211_PRISM arp type.
> 
> Is the allocation of this number standardized somewhere?

Yes and no.  There are a handful of standard hardware ARP types defined
in RFC826, I believe.  [checks.]  No, I guess not.   But those are
definately standardized, probably by the IEEE or somesuch.

Meanwhile, the "Dummy types for non ARP hardware" list in if_arp.h seems
to be the authoratitive non-standard standard, as it starts at 256 and
seems to pretty much sequentially count up with the occasional large
gap.   

Linux's PF_SOCKET code uses this to identify the packet type
coming off the wire.

The ARPHRD_IEEE80211 type was defined in 2.4.6 by incrementing the
number by one and appending it to the end of the list.  I just
incremented the protocol number by one for the _PRISM type.

I have no idea if there was some master list somewhere; google didn't
seem to return any hits other than the linux source.

 - Pizza
-- 
Solomon Peachy                                    pizzaATfucktheusers.org
I ain't broke, but I'm badly bent.                           ICQ# 1318344
Patience comes to those who wait.
    ...It's not "Beanbag Love", it's a "Transanimate Relationship"...

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  reply	other threads:[~2001-12-22  5:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-22  5:01 Stuffed Crust
2001-12-22  5:06 ` David S. Miller
2001-12-22  5:42   ` Stuffed Crust [this message]
2001-12-24  0:49 ` David S. Miller

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=20011222004228.A22793@shaftnet.org \
    --to=pizza@shaftnet.org \
    --cc=davem@redhat.com \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®