currently working on a project involving MPC8360 board, and was
handed a patch to the system .dts file that contained the following
snippet for the muram node:
muram@1 {
- #address-cells = <1>;
+ #address-cells = <2>;
Hello Tony,
On 06/09/2014 10:28 AM, Tony wrote:
> Thank Emil.
>
> Where can i find the details about a 'diff' of qman revisions ?
Let me look if someody bothered to write an AN about this
> The code
> i ported doesnt support latest qman revision (REV3).
Ported from what (I suspect) SDK releas
Thank Emil.
Where can i find the details about a 'diff' of qman revisions ? The code i
ported doesnt support latest qman revision (REV3). Can i still work on qman
REV1.1 for all the latest targets ? (read t-series)
Regards
On Mon, Jun 9, 2014 at 8:32 PM, Emil Medve
wrote:
> Hello Tony,
>
>
>
Hello Tony,
On 06/09/2014 06:43 AM, Tony wrote:
> How's the fsl,qman-channel-id value different for different targets ?
Channel ids are assigned in hardware
> Is there any document on how this value is achieved ?
They are described in the RM of each SoC and in the DPAA RM
> Or can it be any v
How's the fsl,qman-channel-id value different for different targets ?
Is there any document on how this value is achieved ?
Or can it be any value ???
Alan.
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/li
eSDHC of T4240 had 1.8v voltage support. Add this node to specify
eSDHC voltage capacity. If this node not specified eSDHC driver
still can read from eSDHC host capacity register.
Signed-off-by: Haijun Zhang
Signed-off-by: Anton Vorontsov
---
changes for v2:
- rewrite the voltage-ranges
On 07/22/2013 09:59:04 PM, Haijun Zhang wrote:
eSDHC of T4240 had 1.8v voltage support. Add this node to specify
eSDHC voltage capacity. If this node not specified eSDHC driver
still can read from eSDHC host capacity register.
Signed-off-by: Haijun Zhang
Signed-off-by: Anton Vorontsov
---
chan
eSDHC of T4240 had 1.8v voltage support. Add this node to specify
eSDHC voltage capacity. If this node not specified eSDHC driver
still can read from eSDHC host capacity register.
Signed-off-by: Haijun Zhang
Signed-off-by: Anton Vorontsov
---
changes for this patch set:
- split from patc
Hi
I'm using the i2c/chips/tsl2550 driver. In the tsl2550_probe() function
the driver checks for platform data to set the operating_mode. I suppose
I can provide this data in my dts file but I don't know how to do that.
Currently my dts looks like this:
tsl2...@39 {
compatible = "taos,tsl2
Currently we have some limitations in the 4xx PCIe driver and can't
support all possible PCIe busses. But the current limits in the
dts file are quite low (only 16 busses per RC). This patch increases
the number to 64 per RC.
Signed-off-by: Stefan Roese <[EMAIL PROTECTED]>
---
arch/powerpc/boot/d
10 matches
Mail list logo