netdev
[Top] [All Lists]

Re: ETH_P_X25 type (was Re: [PATCH] cyclom2x driver update)

To: Arnaldo Carvalho de Melo <acme@xxxxxxxxxxxxxxxx>
Subject: Re: ETH_P_X25 type (was Re: [PATCH] cyclom2x driver update)
From: Henner Eisen <eis@xxxxxxxxxxxxx>
Date: 01 Nov 1999 21:51:31 +0100
Cc: cyclom2x device driver devel list <cycsyn-devel@xxxxxxxxxxxxxxxxxxxxxx>, linux-x25@xxxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx
In-reply-to: Arnaldo Carvalho de Melo's message of "Mon, 1 Nov 1999 16:57:29 -0200 (EDT)"
References: <Pine.LNX.4.20.9911011628080.15054-100000@xxxxxxxxxxxxxxxxx>
Sender: owner-netdev@xxxxxxxxxxx
>>>>> "Arnaldo" == Arnaldo Carvalho de Melo <acme@xxxxxxxxxxxxxxxx> writes:

    Arnaldo> cool, I was trying just to hack the X.25 packet layer to
    Arnaldo> make it work without that much changes, but seems like
    Arnaldo> we'll get a cleaner hack... ;)

Well, lets wait for comments from others, in particular I'd like to
know, what the ETH_P_CONTROL was originally intended for.

The other question is whether changes like this are appropriate at
the currrent (feature freeze) state of the kernel.

Another question to other network developers:

I think it would be nice to have reserved a dummy ETH_P_EXP in if_ether.h
and a dummy ARPHRD_EXP in if_arp.h that can be be safely used (without
risking to clash with future official extensions) by experimential
protocol/device_type implementations until they get an officially
assigned ID. Should I prepare a patch?

Henner 

<Prev in Thread] Current Thread [Next in Thread>