[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b0438a630811250851p18f5feabx7e744978555fa1d1@mail.gmail.com>
Date: Tue, 25 Nov 2008 17:51:10 +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/25 Krzysztof Halasa <khc@...waw.pl>:
> "Miguel Ángel Álvarez" <gotzoncabanes@...il.com> writes:
>
>> I am not quite sure about this. If we do not set the clock_rate as
>> part of the "physical_mode"... where should it be set? As a separate
>> variable?
>
> I think so. In most cases the external clock will be used anyway.
>
OK.
> The truth is the HSS channelized code is quite experimental. It works,
> and I actually use it, but I haven't yet decided about the API and
> this is why it isn't still upstream.
>
I understand.
>> Sure... Let me re-do the question. Do you know how MVIP is set if I
>> detect it is needed? And... good idea with the registering of four
>> devices.
>
> The platform code should provide the "mode" (aka topology) = "4 * E1".
> There is nothing to detect. The driver has to handle 4E1, that's all.
>
I think I do not make me understand myself... The question is: Do you
know which message should I send to the NPE to configure it for MVIP
mode?
I have another question though... It is very basic, but I am mixing things...
- If you have just one source of data, you can use packetized mode
(and it does not care which clock rate you are using...).
- If you have more than one sources of data and are working (for
example) with an E1, you create a channel for each source, and the
driver manages it.
- But... If I want four sources of unstructured data (one for each
"E1" in a 4E1), must I use a channelized mode, or a packetized mode?
Thanks
Miguel Ángel
--
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
Powered by blists - more mailing lists