For a start we could copy the the if_infiniband.h file. It only has a
single define in it, address length.
I noticed our missing if_xxx file when adding the link local support.
All other hardware classes were including if_ and I had to include
af_ to get our address length. The other hardw
From: Dmitry Eremin-Solenikov
Date: Wed, 11 Aug 2010 01:31:44 +0400
> Adding David Miller to the discussion, as the net-related stuff maintainer
Better to add [email protected], so that all the rest of
the world of networking developers can respond when (as is the
case right now) I am too b
Hello,
Adding David Miller to the discussion, as the net-related stuff maintainer
On 8/11/10, Jon Smirl wrote:
> On Tue, Aug 10, 2010 at 4:28 PM, Dmitry Eremin-Solenikov
> wrote:
>> On 8/11/10, Dmitry Eremin-Solenikov wrote:
>>> Hello,
>>>
>>> On 8/10/10, Jon Smirl wrote:
Other network h
On Tue, Aug 10, 2010 at 4:28 PM, Dmitry Eremin-Solenikov
wrote:
> On 8/11/10, Dmitry Eremin-Solenikov wrote:
>> Hello,
>>
>> On 8/10/10, Jon Smirl wrote:
>>> Other network hardware has a include/linux/if_.h file describing
>>> it. IEEE 802.15.4 has the same info, it is just spread out over
>
On 8/11/10, Dmitry Eremin-Solenikov wrote:
> Hello,
>
> On 8/10/10, Jon Smirl wrote:
>> Other network hardware has a include/linux/if_.h file describing
>> it. IEEE 802.15.4 has the same info, it is just spread out over
>> different files. There are also naming conventions that don't match.
Hello,
On 8/10/10, Jon Smirl wrote:
> Other network hardware has a include/linux/if_.h file describing
> it. IEEE 802.15.4 has the same info, it is just spread out over
> different files. There are also naming conventions that don't match.
> For example IEEE80215_ADDR_LEN vs ARCNET_ALEN, ETH
Other network hardware has a include/linux/if_.h file describing
it. IEEE 802.15.4 has the same info, it is just spread out over
different files. There are also naming conventions that don't match.
For example IEEE80215_ADDR_LEN vs ARCNET_ALEN, ETH_ALEN, etc...
Do you want to reorganize the h
