On Wed, 01 Feb 2006 19:33:47 +0100
Krzysztof Halasa <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] (Marco d'Itri) writes:
>
> > Why you cannot support autoloading the modules when a specific protocol
> > is needed?
>
> I probably could but it would complicate things a bit - currently only
> the
[EMAIL PROTECTED] (Marco d'Itri) writes:
> Why you cannot support autoloading the modules when a specific protocol
> is needed?
I probably could but it would complicate things a bit - currently only
the protocol module knows about existence of its protocol.
I will look at it, though. Thanks.
--
On Feb 01, Krzysztof Halasa <[EMAIL PROTECTED]> wrote:
> 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 -
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 proto