netdev - Re: ixp4xx_hss MAX_CHAN

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <b0438a630811240203mdc431aev8b1bb9e8c924ac7e@mail.gmail.com>
Date:	Mon, 24 Nov 2008 11:03:29 +0100
From:	"Miguel Ángel Álvarez" <gotzoncabanes@...il.com>
To:	"Krzysztof Halasa" <khc@...waw.pl>
Cc:	netdev@...r.kernel.org, linux-arm-kernel@...ts.arm.linux.org.uk
Subject: Re: ixp4xx_hss MAX_CHAN_DEVICES

Hi

2008/11/21 Krzysztof Halasa <khc@...waw.pl>:
> Hi,
>
> "Miguel Ángel Álvarez" <gotzoncabanes@...il.com> writes:
>
>> I am interested in modifying ixp4xx_hss so that 4*32 channels can be
>> used for each hss device.
>
> I assume you mean 4 multiplexed E1 (with an external multiplexer/framer).
>

Sure. Sorry for not having stated it properly.

>> My first option is to modify the "defines" placed in the driver, but I
>> wonder if it would be useful to modify hss_plat_info to set this kind
>> of info.
>
> I think we should add some "physical mode" parameter - single channel
> (such as E1, T1 etc), 4 * E1, and any other (4 * T1 which is IIRC
> special) when needed.
>

This is a great idea. Lots of parameters are related, so setting this
"physical mode" should be enough to configure the rest. I will try to
prepare a simple patch in order to comment if the ideas are correct.

> It can go into hss_plat_info - a fixed(?) HSS port property.

Yes... I think it could be enough to make it a fixed property at the
moment. Maybe it could be added to sysfs in the future.

Miguel Ángel Álvarez
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html