Hi,
I'm considering some changes/additions to my generic HDLC (WAN) code.
What do you think about:
a) Currently it consists of mid-layer WAN protocols single module (Cisco
HDLC, FR etc.) + low-level hardware HDLC card driver (C101, N2, PCI200SYN
etc.). I'm thinking about splitting the protocol module into separate
modules - it would make them independent, users would be able to
load, say, FR without PPP or X.25 and underlying syncppp, lapb etc.
From the technical POV it would be superior to current code but it
would require sysadmins to change modprobe.conf, add another modprobe
or something like that. Not a real problem but the upgrade can't be
automatic.
b) I'm currently using a dedicated "sethdlc" tool for configuring WAN
devices (both physical parameters like clocking, speeds etc. and
protocol parameters/selection). It uses ioctl(). I'm thinking about
switching configuration interface to sysfs. That would render the
old ioctl interface obsolete.
It would mean much better flexibility, and (when the HDLC ioctl
interface is removed in a year or so) would simplify the code.
I'm not sure about using sysfs for net device configuration, though.
Of course, it would make sysfs mandatory for generic HDLC users.
I'd aim at making changes to ~ 2.6.18.
Opinions?
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
