Re: ixp4xx_hss: 4E1

Re: ixp4xx_hss: 4E1

[Krzysztof Halasa]

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

Re: ixp4xx_hss: 4E1

[Krzysztof Halasa]

"Miguel Ángel Álvarez" <alvarezcabanes@gmail.com> writes:

> Another question related with ixp4xx_hss... Why do you create network
> interfaces instead of character devices? Would it not be more general to
> use these lasts (ppp over these could create the network interfaces)?

Well, I guess I just need network interfaces, not char devices.
PPP can of course create network interfaces, but it supports only PPP
protocol (and interface to generic PPP is in the works). Now the thing
supports Cisco HDLC, PPP, Frame-Relay, Ethernet-in-HDLC and X.25/LAPB.
-- 
Krzysztof Halasa