Can you please be a little more specific about the sysfs problem? Should I recompile kernel with CONFIG_SYSFS=n ? Are this issues (with sysfs and unloading modules) going to be fixed any time soon? I ask this because I usually prefer to use the kernels of the distro I am using and not recompiling from the begining.
no the kernel keeps untouched, you can stick with the distro delivered kernel. Only mISDN does not register sysfs classes with the kernel interface anymore, so you don't have /sys/class/mISDN-*

currently with kernels >=2.6.24

Since this is not a good solution at all and it doesn't work for the mISDN master branch, we will have to make a better fix for this problem. But i can't tell when this will happen.

From your answer about fax support inside misdn, I understand it will not happen anytime soon. Is it possible that this functionality will go into LCR?
it is possible, but you need to get Andreas to love this idea :)

Thanks again,

Panagiotis Malakoudis


On Wed, Jun 18, 2008 at 12:57 PM, Christian <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:


        - Is it SMP safe?

    yes, the SMP issues have been resolved ages ago, so it should work
    flawlessly. I have numerous customers using SMP Machines with the
    1.1.X branch of mISDN.

        - Is it 64bit safe?

    well, i have no 64bit hardware to test with. But in general when
    we find 64bit issues we'll try to fix them asap. Anyway i cannot
    tell if it is 64bit safe right now.


        - Does it run without lockups or kernel panics on 2.6.24 kernels?

    I tested it with 2.6.25 and i needed to remove the sysfs support
    to make it run without kernel panics/lockups. The same issue was
    present in 2.6.24, so yes it "runs" without lockups/panics.

    Though there might exist lockups/panics at module unload time.

        - Does this release require recompile of chan-misdn for
        asterisk 1.4 or a previous build based on 1.1.7.2
        <http://1.1.7.2> <http://1.1.7.2/> is ok?

    if you upgrade mISDNuser you need to recompile chan_misdn anyways!


        On another issue, is the misdn team considering to add fax
        support (via spandsp or other library) inside the misdn
        project (over capi perhaps?)


    we are thinking about this since ages, but this is so much work
    that nobody has the time to do that. Also the capi support of
    mISDN is not very well at present. So i think you shouldn't expect
    this in the next years, if no one is willing to pay for it, or if
     Jolly starts to love this idea and does it in his free times.


        Thank you,

        Panagiotis Malakoudis


        On Wed, Jun 18, 2008 at 11:54 AM, Christian
        <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
        <mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>>
        wrote:

           Hi folks,

           i've released mISDN 1.1.8 today which include the following
        changes:

           mISDN:
           * progress messages can also arrive in the alerting phase
           * only load mISDN_capi in case capi is configured
           * fix an skb leak in mISDN_dt_new_frame when debugging is
        disabled
           * Fixed mISDN compile on kernel v2.6.24 (merged from master)
           * added BN2S and BN4S PCIe cards
           * added fix for kernel panic with kernels > 2.6.25
           * fixed kernel panic, that occured, when audio data was
        preloaded
            and then the bridge was activated (only when hz=100 or
        hz=300 in
           the kernel config)

           mISDNuser:

           * added small hack to send restart_acknowledge when we
        receive a
           restart. This fixes a lot of trouble with alcatel S0 pbxs



           Cheers,

           Christian

           _______________________________________________
           Misdn-asterisk mailing list
           [email protected]
        <mailto:[email protected]>
           <mailto:[email protected]
        <mailto:[email protected]>>

http://lists.beronet.com/cgi-bin/mailman/listinfo/misdn-asterisk

           _______________________________________________
           Misdn-asterisk mailing list
           [email protected]
        <mailto:[email protected]>
           <mailto:[email protected]
        <mailto:[email protected]>>

http://lists.beronet.com/cgi-bin/mailman/listinfo/misdn-asterisk


        ------------------------------------------------------------------------

        _______________________________________________
        Misdn-asterisk mailing list
        [email protected]
        <mailto:[email protected]>
        http://lists.beronet.com/cgi-bin/mailman/listinfo/misdn-asterisk



_______________________________________________
Misdn-asterisk mailing list
[email protected]
http://lists.beronet.com/cgi-bin/mailman/listinfo/misdn-asterisk

Reply via email to