public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Halasa <khc@pm.waw.pl>
To: "Miguel Ángel Álvarez" <gotzoncabanes@gmail.com>
Cc: netdev@vger.kernel.org, linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: ixp4xx_hss MAX_CHAN_DEVICES
Date: Fri, 21 Nov 2008 23:52:57 +0100	[thread overview]
Message-ID: <m3fxlksncm.fsf@maximus.localdomain> (raw)
In-Reply-To: <b0438a630811190317u715f1376j830133591ec497b9@mail.gmail.com> ("Miguel Ángel Álvarez"'s message of "Wed\, 19 Nov 2008 12\:17\:56 +0100")

Hi,

"Miguel Ángel Álvarez" <gotzoncabanes@gmail.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).

> 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.

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

  reply	other threads:[~2008-11-21 22:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-19 11:17 ixp4xx_hss MAX_CHAN_DEVICES Miguel Ángel Álvarez
2008-11-21 22:52 ` Krzysztof Halasa [this message]
2008-11-24 10:03   ` Miguel Ángel Álvarez
2008-11-24 12:15     ` Miguel Ángel Álvarez
2008-11-24 16:14       ` Krzysztof Halasa
2008-11-24 17:12         ` Miguel Ángel Álvarez
2008-11-24 23:52           ` Krzysztof Halasa
2008-11-25 16:51             ` Miguel Ángel Álvarez
2008-11-26  0:09               ` Krzysztof Halasa
2008-11-26 10:02                 ` Miguel Ángel Álvarez
2008-11-26 11:19                   ` Krzysztof Halasa
2008-11-26 12:08                     ` Miguel Ángel Álvarez

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=m3fxlksncm.fsf@maximus.localdomain \
    --to=khc@pm.waw.pl \
    --cc=gotzoncabanes@gmail.com \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --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