From: Krzysztof Halasa <khc@pm.waw.pl>
To: "Miguel Ángel Álvarez" <alvarezcabanes@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: ixp4xx_hss: 4E1
Date: Tue, 09 Sep 2008 14:42:42 +0200 [thread overview]
Message-ID: <m3ljy1trr1.fsf@maximus.localdomain> (raw)
In-Reply-To: <4f40a1df0809040045m6c5ff3d7s7d8ca2b624a0a8da@mail.gmail.com> ("Miguel Ángel Álvarez"'s message of "Thu\, 4 Sep 2008 09\:45\:59 +0200")
Hi,
"Miguel Ángel Álvarez" <alvarezcabanes@gmail.com> writes:
> Our main purpose is to use the two HSS of NPE-A in packetized mode, to
> obtain 2x4E1 channels.
>
> Our planned changes are:
> - Change the clock-rate from 2048000 to 8192000 so that we have a 4E1 per
> HSS instead of just an E1.
> - Change the frame_size from 256 to 1024.
> - Assign 4 PKT_NUM_PIPES instead of 1, so that we can have 4HDLC per
> HSS... that is up to 32x64kbps channels per HDLC.
>
> Are we working in the right direction?
I think so.
> We think it could be interesting to modify the driver so that each of the
> channels can be activated or not, and assigned to the different HDLCs...
> Would it be a desired behaviour to he mainstream, or should we leave just
> for our development?
Well... The HSS driver, especially the TDM part, is a real mess.
I plan to push the HDLC part (without TDM) into the official kernel,
the TDM part will stay in my private tree until something happens
(such as release of the firmware docs and/or source so I can remove
the hacks). But, of course, I can include your changes in my tree, if
they aren't way more hackish than mine, of course :-)
--
Krzysztof Halasa
next parent reply other threads:[~2008-09-09 12:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4f40a1df0809040045m6c5ff3d7s7d8ca2b624a0a8da@mail.gmail.com>
2008-09-09 12:42 ` Krzysztof Halasa [this message]
[not found] ` <4f40a1df0809160845g55567209rb0ccc4cc041b0053@mail.gmail.com>
2008-09-16 22:49 ` ixp4xx_hss: 4E1 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=m3ljy1trr1.fsf@maximus.localdomain \
--to=khc@pm.waw.pl \
--cc=alvarezcabanes@gmail.com \
--cc=netdev@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