Andi Kleen <[EMAIL PROTECTED]> wrote:
>> we were talking about the load order. This will solve the load order,
>> but if we have races like the kind you described, then the whole mISDN
>> design is broken.
>
> It's more a generic problem of the module code.
It's a problem of not enough synchroni
On 22.02.2008 13:04, Karsten Keil wrote:
These design issues are fixed in the new mISDN socket branch.
The old mISDN design was too complicated because it allow access to
every layer and build the ISDN stack dynamically, both feature were never
needed in practice and contain many race conditions.
Hi Karsten.
> Normally I reserved the complete last week for working on mISDN to get it
> ready to submit it to -mm, but reality did hit me and I had to do some
> other importent stuff :-(
When you do your first submission can you please submit the minimal
possible configuration.
I tried enabling
Hi,
sorry that I step in so late, procmail sorted this thread in the wrong
box.
Normally I reserved the complete last week for working on mISDN to get it
ready to submit it to -mm, but reality did hit me and I had to do some
other importent stuff :-(
On Thu, Feb 21, 2008 at 11:33:04AM +0100, Simo
Hi Simon,
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 reason (and I can think
of multiple here)
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 reason
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 reason (and I can think of
Am 20.02.2008 20:04 schrieb 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.
It's an enabler for getting a move forwar
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 par
Am 20.02.2008 17:54 schrieb Andi Kleen:
mISDN has two problems, which are of course interrelated:
a) complete lack of documentation for the in-kernel driver interface
(equivalent of Documentation/isdn/INTERFACE)
Most subsystems in the kernel would disqualify under that rule
I beg to diffe
> mISDN has two problems, which are of course interrelated:
>
> a) complete lack of documentation for the in-kernel driver interface
>(equivalent of Documentation/isdn/INTERFACE)
Most subsystems in the kernel would disqualify under that rule
Did you ever look for full documentation on how t
> mISDN has two problems, which are of course interrelated:
>
> a) complete lack of documentation for the in-kernel driver interface
> (equivalent of Documentation/isdn/INTERFACE)
>
> b) still doesn't support all the hardware isdn4linux supports.
>
> As long as those problems aren't solved,
Marcel Holtmann schrieb:
My proposal is to merge mISDN and then see what falls out. My guess it
won't be that bad as everybody thinks and then we go from there. Next
step is to remove ISDN4Linux since that should not be used at all
anymore.
No. Next step is to create the missing documentat
Gregory Nietsky schrieb:
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 mI
Hi Andi,
If noone in the isdn community step up and take some responsibility
for the current isdn drivers in Linux then we should just delete
them.
So you're saying anything that has no active maintainer should
be immediately deleted?
You do not recognize a provocation when you see it?
I w
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 ou
>
> 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.
And Gregory wrote:
> ive been hackin away at mISDN for a while and use it with recent kernels
>
On Tue, 19 Feb 2008, Andi Kleen wrote:
On Tue, Feb 19, 2008 at 10:56:22AM +0100, Sam Ravnborg wrote:
If noone in the isdn community step up and take some responsibility
for the current isdn drivers in Linux then we should just delete them.
So you're saying anything that has no active maintai
On Tue, Feb 19, 2008 at 10:56:22AM +0100, Sam Ravnborg wrote:
> >
> > > If noone in the isdn community step up and take some responsibility
> > > for the current isdn drivers in Linux then we should just delete them.
> >
> > So you're saying anything that has no active maintainer should
> > be i
>
> > If noone in the isdn community step up and take some responsibility
> > for the current isdn drivers in Linux then we should just delete them.
>
> So you're saying anything that has no active maintainer should
> be immediately deleted?
You do not recognize a provocation when you see it?
I
On Tue, Feb 19, 2008 at 11:25:06AM +0200, Gregory Nietsky wrote:
> 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 ker
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 the
On Tue, Feb 19, 2008 at 09:50:33AM +0100, Sam Ravnborg wrote:
> Only issue seems that this large ISDN user base is not very active
> in respect to Linux driver development.
They don't need to because this stuff basically works and there isn't
much new hardware anymore and no new standards and it a
On Mon, Feb 18, 2008 at 01:08:33PM +0100, Andi Kleen wrote:
> Greg KH <[EMAIL PROTECTED]> writes:
> >
> > If Jeff does that, I still can't drop those PCI functions from the PCI
> > core, which I desperatly want to do as they do not play nice with modern
> > systems (meaning hotplug...).
> >
> > So
Jeff Garzik <[EMAIL PROTECTED]> writes:
>> And there is definitely still a large ISDN user base too.
>
> This is what I'm curious about. My personal guess is that there is a
> lot of ISDN hardware available, but not necessarily the telco ISDN
> availability.
At least Germany has about 100% ISD
Andi Kleen wrote:
Merging essentially untested patches does not seem like a good strategy.
Agreed. I don't want my stuff going in without knowing it works.
And there is definitely still a large ISDN user base too.
This is what I'm curious about. My personal guess is that there is a
lot
On Mon, 18 Feb 2008 13:08:33 +0100
Andi Kleen <[EMAIL PROTECTED]> wrote:
> Greg KH <[EMAIL PROTECTED]> writes:
> >
> > If Jeff does that, I still can't drop those PCI functions from the PCI
> > core, which I desperatly want to do as they do not play nice with modern
> > systems (meaning hotplug...
Greg KH <[EMAIL PROTECTED]> writes:
>
> If Jeff does that, I still can't drop those PCI functions from the PCI
> core, which I desperatly want to do as they do not play nice with modern
> systems (meaning hotplug...).
>
> So either way, I think his patches should go in.
Merging essentially unteste
On Sun, Feb 17, 2008 at 08:52:35PM +0100, Sam Ravnborg wrote:
> Hi Karsten et al.
>
> Seeing the work Jeff puts into ISDN I was wondering what are the
> state of mISDN. Will we soon see mISDN hit the tree or has
> development stalled?
>
> I was wondering if Jeff should go for the much simpler pat
Hi Karsten et al.
Seeing the work Jeff puts into ISDN I was wondering what are the
state of mISDN. Will we soon see mISDN hit the tree or has
development stalled?
I was wondering if Jeff should go for the much simpler patch:
diff --git a/drivers/isdn/Kconfig b/drivers/isdn/Kconfig
index 66f946a.
30 matches
Mail list logo
