Re: [ANNOUNCE] FLAME: external kernel module for L2.5 meshing

[Simon Oosthoek <simon.oosthoek@ti-wmc.nl>]

Stephen Hemminger wrote:
> O
> > Usage
> > =====
> > - Load module:
> >     modprobe flame [debuglevel=]  [flm_topo_timer=]
> >       : debug level, default: 1
> >       : topology check timer (in seconds), default: 5
> > - Open/close a device with:
> >     echo "up   []" > /proc/net/flame/cmd
> >     echo "down " > /proc/net/flame/cmd
> >       : name of FLAME device, e.g. flm0
> >       : comma-separated list of MAC devices (at least one) that are
> >       used below the FLAME device. All of these must be up.
> >     : comma-separated list of MAC addresses of devices
> >       for which traffic should be ignored; each MAC address should
> >       be a semicolon-separated list of 6 hex-pairs
> > - Get current forwarding info from FLAME:
> >     cat /proc/net/flame/fwd
> > - Get nodes/cost information from MACINFO:
> >     cat /proc/net/macinfo
>
>
> Use of /proc for an API is no longer desirable. Please rewrite.
> -

hmm, ok, I'm not sure this will happen anytime soon (being a rather low 
priority thing, which is also the reason it's not submitted as patch to 
the kernel and not signed off), but what is currently the desirable method?

Cheers

Simon

PS, I'm replying for my colleague, who will see this Monday at the 
earliest ;-)

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/