From: Krzysztof Halasa <khc@pm.waw.pl>
To: Adam Anthony <AAnthony@sbs.com>
Cc: Francois Romieu <romieu@fr.zoreil.com>, linux-kernel@vger.kernel.org
Subject: Re: Linux HDLC Stack - N2 module
Date: Fri, 14 Jan 2005 02:53:37 +0100 [thread overview]
Message-ID: <m3vfa0ojxa.fsf@defiant.pm.waw.pl> (raw)
In-Reply-To: <4F23E557A0317D45864097982DE907941A38A8@pilotmail.sbscorp.sbs.com> (Adam Anthony's message of "Thu, 13 Jan 2005 09:02:20 -0700")
Adam Anthony <AAnthony@sbs.com> writes:
> Krzysztof and Ueimor,
> Following the advice prescribed below, I've had a look at existing
> HDLC work in the kernel. I tried firing up a Riscom/N2 adapter with the
> 2.4.28 N2 module and HDLC support but was faced with a number of problems.
> It seems like the transmit buffers aren't getting emptied after transmit,
> because I can only transmit a few frames before traffic halts. Transmit
> statistics don't increment either, but I am seeing frames on the remote end.
Looks like IRQ problem. Can you see IRQ handler being called?
I.e. doesn the counter in /proc/interrupts increment?
> Has the N2 module been tested with recent kernels? Is it useable?
It should be, though I haven't used N2 card for a year maybe.
Still, other cards (c101 and pci200syn) share the same low-level
driver core, I know people with c101 (not sure about their kernel
versions) and I personally use pci200syn with latest 2.6 kernels.
There are some issues wrt Frame-Relay code (no PVC list locking,
there is some small possibility of kernel panic etc. while removing
a PVC on live interface - will fix when time permits, problem never
reported).
--
Krzysztof Halasa
prev parent reply other threads:[~2005-01-14 1:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-13 16:02 Adam Anthony
2005-01-13 22:41 ` Francois Romieu
2005-01-14 1:53 ` Krzysztof Halasa [this message]
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=m3vfa0ojxa.fsf@defiant.pm.waw.pl \
--to=khc@pm.waw.pl \
--cc=AAnthony@sbs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=romieu@fr.zoreil.com \
/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
Powered by JetHome