From: Christoph Hellwig <hch@infradead.org>
To: chas williams - CONTRACTOR <chas@cmf.nrl.navy.mil>
Cc: netdev@vger.kernel.org, davem@davemloft.net
Subject: Re: [PATCH net-2.6.25 4/7][ATM]: [br2864] routed support
Date: Mon, 31 Dec 2007 09:09:58 +0000 [thread overview]
Message-ID: <20071231090957.GA28855@infradead.org> (raw)
In-Reply-To: <200712300107.lBU17O8i003566@cmf.nrl.navy.mil>
> +#define BR2684_ETHERTYPE_LEN 2
> +#define BR2684_PAD_LEN 2
> +
> +#define LLC 0xaa, 0xaa, 0x03
> +#define SNAP_BRIDGED 0x00, 0x80, 0xc2
> +#define SNAP_ROUTED 0x00, 0x00, 0x00
> +#define PID_ETHERNET 0x00, 0x07
> +#define ETHERTYPE_IPV4 0x08, 0x00
> +#define ETHERTYPE_IPV6 0x86, 0xdd
> +#define PAD_BRIDGED 0x00, 0x00
> +
> +static unsigned char ethertype_ipv4[] =
> + { ETHERTYPE_IPV4 };
> +static unsigned char ethertype_ipv6[] =
> + { ETHERTYPE_IPV6 };
> static unsigned char llc_oui_pid_pad[] =
> - { 0xAA, 0xAA, 0x03, 0x00, 0x80, 0xC2, 0x00, 0x07, 0x00, 0x00 };
> -#define PADLEN (2)
> + { LLC, SNAP_BRIDGED, PID_ETHERNET, PAD_BRIDGED };
> +static unsigned char llc_oui_ipv4[] =
> + { LLC, SNAP_ROUTED, ETHERTYPE_IPV4 };
> +static unsigned char llc_oui_ipv6[] =
> + { LLC, SNAP_ROUTED, ETHERTYPE_IPV6 };
I think this should be in a global header. And IIRC we already have
at least some of these somewhere as part of the general llc support.
next prev parent reply other threads:[~2007-12-31 9:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-30 1:07 [PATCH net-2.6.25 4/7][ATM]: [br2864] routed support chas williams - CONTRACTOR
2007-12-31 7:18 ` David Miller
2007-12-31 9:09 ` Christoph Hellwig [this message]
2007-12-31 15:44 ` chas williams - CONTRACTOR
2008-01-16 4:16 ` Chung-Chi Lo
2008-01-26 12:20 ` chas williams - CONTRACTOR
2008-01-29 7:42 ` Chung-Chi Lo
2008-01-30 20:49 ` chas williams - CONTRACTOR
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=20071231090957.GA28855@infradead.org \
--to=hch@infradead.org \
--cc=chas@cmf.nrl.navy.mil \
--cc=davem@davemloft.net \
--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.