> > Hi, > > > > There are 6 token ring bits, which I presume are available when token > > ring is not selected. > > > > #define IFM_TOK_ETR 0x00000200 /* Early token release */ > > #define IFM_TOK_SRCRT 0x00000400 /* Enable source routing > > features */ > > #define IFM_TOK_ALLR 0x00000800 /* All routes / Single route > > bcast */ > > #define IFM_TOK_DTR 0x00002000 /* Dedicated token ring */ > > #define IFM_TOK_CLASSIC 0x00004000 /* Classic token ring */ > > #define IFM_TOK_AUTO 0x00008000 /* Automatic Dedicate/Classic > > token ring */ > > > > Maybe these can be used for other purposes when the type is equal to > > ethernet?
These are the "type-specific options". Ethernet uses three of these (see IFM_ETH_*). I hadn't thought about it, but some of the remaining five bits could be used for extended Ethernet subtypes. > Hi Mike, > My proposal is, convert: > > #define IFM_TOK_DTR 0x00002000 /* Dedicated token ring */ > > #define IFM_TOK_CLASSIC 0x00004000 /* Classic token ring */ > > #define IFM_TOK_AUTO 0x00008000 /* Automatic Dedicate/Classic > Into different network types: > #define IFM_TOKEN_NONE > #define IFM_TOKEN_DTR > #define IFM_TOKEN_CLASSIC > #define IFM_TOKEN_AUTO > and extend the IFM_NMASK like this: > #define IFM_NMASK 0x0000e0e0 /* Network type */ I don't think any change is required for token ring. Finding hardware to test would be a challenge in any case. Simply using some of the options bits for subtype would be simpler. I could outline this if anyone wants. Mike _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"