Hi Ben,
> > When we're using CONFIG_ARM_DEVTREE, we need to postpone machine
> > detection until later in setup_arch. Because ARM_DEVTREE depends on
> > !DEBUG_LL, we don't need the mdesc this early anyway.
> >
> > We'll add support for ARM_DEVTREE && DEBUG_LL later.
>
> Why not add a specific ma
John Schmoller wrote:
Hello all,
I'm currently working with U-Boot to pass POST results to Linux in an
FDT. To do this, I'm intending to use the "status" property, as
documented in ePAPR 1.0 (I'm using PowerPC). My question involves the
"fail-sss" property value. What is the intention of "sss
Hello Wolfgang,
> We only support MPC512x Rev. 2 (and later). This is also true for
> other parts of the mainline kernel code - see for example trhe NAND
> driver.
Okay, good to know there are differences in NAND as well. As said before, it
makes sense to me to skip V1. It just should be document
Dear Wolfram,
in message <20100104162441.ga4...@pengutronix.de> you wrote:
>
> One further note: I couldn't spot any code handling Rev1 of the MPC5121? Do
> you
> plan to add such code? If not, we should at least put a comment that it is
> missing. The binding documentation should be updated as
Wolfram Sang wrote:
>> Nice. Just for curiosity, what clock and frequency does it select on
>> your board? It should be listed when the driver is loaded.
>
> Using this simple dts-snipplet
>
> ms...@1300 {
> compatible = "fsl,mpc5121-mscan";
>
> Nice. Just for curiosity, what clock and frequency does it select on
> your board? It should be listed when the driver is loaded.
Using this simple dts-snipplet
ms...@1300 {
compatible = "fsl,mpc5121-mscan";
cell-index = <0>;
Hi Wolfram,
Wolfram Sang wrote:
> Hello Wolfgang,
>
> first the good news: Your patches also work with our MPC5121-board.
Nice. Just for curiosity, what clock and frequency does it select on
your board? It should be listed when the driver is loaded.
+#else /* !CONFIG_PPC_MPC5200 */
+s
Hello Wolfgang,
first the good news: Your patches also work with our MPC5121-board.
> >> +#else /* !CONFIG_PPC_MPC5200 */
> >> +static u32 __devinit mpc52xx_can_get_clock(struct of_device *ofdev,
> >> + const char *clock_name,
> >> +
> -Original Message-
> From:
> devicetree-discuss-bounces+stuart.yoder=freescale@lists.oz
labs.org [mailto:devicetree-discuss->
bounces+stuart.yoder=freescale@lists.ozlabs.org] On
> Behalf Of John Schmoller
> Sent: Wednesday, December 30, 2009 10:58 AM
> To: devicetree-discuss@
Wolfgang Grandegger wrote:
> Wolfram Sang wrote:
>> On Sat, Jan 02, 2010 at 09:17:53AM +0100, Wolfgang Grandegger wrote:
>>> From: Wolfgang Grandegger
>>>
>>> The main differences compared to the MSCAN on the MPC5200 are:
>>>
>>> - More flexibility in choosing the CAN source clock and frequency:
>
10 matches
Mail list logo
