mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andreas Mohr <andi@lisas.de>
To: Karsten Keil <isdn@linux-pingi.de>
Cc: Andreas Mohr <andi@lisas.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mISDN GIT: hfcpci cleanup failure on IRQ weirdness
Date: Tue, 2 Jun 2009 17:44:42 +0200	[thread overview]
Message-ID: <20090602154442.GA10941@rhlx01.hs-esslingen.de> (raw)
In-Reply-To: <200906021653.36152.isdn@linux-pingi.de>

Hi,

On Tue, Jun 02, 2009 at 04:53:35PM +0200, Karsten Keil wrote:
> Yes from mISDN side, but I do not see what inside hisax prevent mISDN from
> getting IRQs after hisax was unloaded. And it works here on my test setup, I 
> can load mISDN without an error, after unloading hisax.

Mayyybe it's due to using kernel hisax with non-kernel (GIT) mISDN?

> > misdn_log still acts weird, though...
> >
> What does be weird here ?

See first mail.

> > BTW, could isdnlog be adapted to support mISDN relatively easily?
> > (since adding CAPI support would take longer I guess)
> 
> isdnlog (beside that the isdnlog code is ugly enough) should be not a big 
> issue, mISDN supports logging in parallel to the normal work, look at the
> tools/loghex.c  code how to create a logging socket.
> It should make things easier as with HiSax, since it will get the data as 
> binary and not as hexdump.

Of course one could get "something" out of a socket-based log sink,
but that "something" would likely be much less than the caller-resolving,
application-spawning stuff that isdnlog does - at least initially.


BTW, I'm migrating towards ISDN via KabelBW modem.

Andreas Mohr

  reply	other threads:[~2009-06-02 15:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-02 13:06 Andreas Mohr
2009-06-02 14:02 ` Andreas Mohr
2009-06-02 14:53   ` Karsten Keil
2009-06-02 15:44     ` Andreas Mohr [this message]
2009-06-02 15:29 ` Karsten Keil
2009-06-02 15:46   ` Andreas Mohr

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090602154442.GA10941@rhlx01.hs-esslingen.de \
    --to=andi@lisas.de \
    --cc=isdn@linux-pingi.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®