Re: Plans for mISDN? Was: [PATCH 00/14] [ISDN] ...

2008-02-21 Thread Gregory Nietsky
Simon Richter wrote: Hi, Tilman Schmidt wrote: mISDN has two problems, which are of course interrelated: mISDN has one problem that is even bigger than these: the kernel oopses if modules aren't loaded in the right order. misdn-init works around that, but if it doesn't work for some

Re: Plans for mISDN? Was: [PATCH 00/14] [ISDN] ...

2008-02-21 Thread Gregory Nietsky
Simon Richter wrote: Hi, Tilman Schmidt wrote: mISDN has two problems, which are of course interrelated: mISDN has one problem that is even bigger than these: the kernel oopses if modules aren't loaded in the right order. misdn-init works around that, but if it doesn't work for some

Re: Plans for mISDN? Was: [PATCH 00/14] [ISDN] ...

2008-02-20 Thread Gregory Nietsky
did someone say interface/API documentation ooops ... seriously this is lacking and im sure as time goes on some volenteer (sucker) will get it up and running.this is not a show stoper but a nice to have.ill perhaps even help out a bit with things, i have some comments on useage and module

Re: Plans for mISDN? Was: [PATCH 00/14] [ISDN] ...

2008-02-20 Thread Gregory Nietsky
did someone say interface/API documentation ooops ... DUCK seriously this is lacking and im sure as time goes on some volenteer (sucker) will get it up and running.this is not a show stoper but a nice to have.ill perhaps even help out a bit with things, i have some comments on useage and

Re: Plans for mISDN? Was: [PATCH 00/14] [ISDN] ...

2008-02-19 Thread Gregory Nietsky
Sam Ravnborg wrote: I'm not sure either it's a good idea to try to merge mISDN if the maintainers don't think it is ready yet. In the spirit of relase early - relase often we should at least see what is going on. well to add mISDN to the kernel tree is straight forward ./std2kern and the

Re: Plans for mISDN? Was: [PATCH 00/14] [ISDN] ...

2008-02-19 Thread Gregory Nietsky
ive been hackin away at mISDN for a while and use it with recent kernels 2.6.2X and have a patch for 2.6.24 (move from semaphore to complition) the distro we built is heavily reliant on mISDN (voip) i dont use the isdn kernel drivers at all any longer. im all for mISDN been mainlined into

Re: Plans for mISDN? Was: [PATCH 00/14] [ISDN] ...

2008-02-19 Thread Gregory Nietsky
ive been hackin away at mISDN for a while and use it with recent kernels 2.6.2X and have a patch for 2.6.24 (move from semaphore to complition) the distro we built is heavily reliant on mISDN (voip) i dont use the isdn kernel drivers at all any longer. im all for mISDN been mainlined into

Re: Plans for mISDN? Was: [PATCH 00/14] [ISDN] ...

2008-02-19 Thread Gregory Nietsky
Sam Ravnborg wrote: I'm not sure either it's a good idea to try to merge mISDN if the maintainers don't think it is ready yet. In the spirit of relase early - relase often we should at least see what is going on. well to add mISDN to the kernel tree is straight forward ./std2kern and the

Odd Ooops jbd ??

2007-11-06 Thread Gregory Nietsky
here is a error i keep bumping into with 2.6.24-rc1 (git11) the trigger is a ISDN call from one port to another (loopback cable) within asterisk i have not been able to replicate it in any other way the error may be in the ISDN what i cant understand is why it would affect the fs. shortly

Odd Ooops jbd ??

2007-11-06 Thread Gregory Nietsky
here is a error i keep bumping into with 2.6.24-rc1 (git11) the trigger is a ISDN call from one port to another (loopback cable) within asterisk i have not been able to replicate it in any other way the error may be in the ISDN what i cant understand is why it would affect the fs. shortly