From: Ben Greear <greearb@candelatech.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Krzysztof Halasa <khc@pm.waw.pl>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Question on HDLC and raw access to T1/E1 serial streams.
Date: Tue, 03 Oct 2006 21:27:58 -0700 [thread overview]
Message-ID: <4523384E.7060806@candelatech.com> (raw)
In-Reply-To: <1159735586.13029.180.camel@localhost.localdomain>
Alan Cox wrote:
> Ar Sul, 2006-10-01 am 11:41 -0700, ysgrifennodd Ben Greear:
>
>> At least some out-of-tree drivers seem to be able to do this. For
>> instance, these guys:
>> http://www.farsite.co.uk/
>>
>
>
> The crazy Zaptel guys can probably do precisely what you need as their
> hardware though aimed at voice work lets software get in at an extremely
> low level.
>
I think you might be right. It will take some more experimenting to see
if they allow
enough control to read/write bitstreams (clear channel groups in their
terminology, I believe) while at
the same time keeping the timing slots in order...
Thanks,
Ben
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2006-10-04 4:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-30 1:24 Question on HDLC and raw access to T1/E1 serial streams Ben Greear
2006-09-30 17:34 ` Krzysztof Halasa
2006-09-30 22:02 ` Ben Greear
2006-10-01 11:54 ` Krzysztof Halasa
2006-10-01 18:41 ` Ben Greear
2006-10-01 20:46 ` Alan Cox
2006-10-04 4:27 ` Ben Greear [this message]
2006-10-04 14:20 ` Lennart Sorensen
2006-10-04 18:03 ` Ben Greear
2006-10-01 22:09 ` Krzysztof Halasa
2006-10-02 16:29 ` Ben Greear
2006-10-03 16:08 ` Krzysztof Halasa
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=4523384E.7060806@candelatech.com \
--to=greearb@candelatech.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=khc@pm.waw.pl \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.