From: Jerry Huang
Signed-off-by: Jerry Huang
---
changes for v2:
- remove the lable "read-only" for DTB and kernel partition
- remove the word "RO" or "RW" from the "lable" option
arch/powerpc/boot/dts/p1020utm-pc.dtsi| 140 +
arch/powerpc/boot/
From: Jerry Huang
Signed-off-by: Jerry Huang
---
changes for v2:
- remove the lable "read-only" for DTB and kernel partition
- remove the word "RO" or "RW" from the "lable" option
arch/powerpc/boot/dts/p1020mbg-pc.dtsi| 151 +
arch/powerpc/boot/
> >> That is interesting! Are those patches published or otherwise available
> >> somewhere? We are also very interested in enabling Canyonlands
> >> with Radeon KMS!
> >
> > You will run into additional problems with 460 due to the fact that it's
> > not cache coherent for DMA. Tony patches don't
Hi Ben,
After merging the pci tree, today's linux-next build (powerpc ppc64_defconfig)
failed like this:
powerpc64-linux-ld: section .text loaded at [00e0,00e0721b]
overlaps section .kernel:dtb loaded at [00e0,00e0066f]
I have applied this patch for today
This TDM controller is available in various Freescale SOCs like MPC8315, P1020,
P1022, P1010.
Signed-off-by: Sandeep Singh
Signed-off-by: Poonam Aggrwal
---
Changes in v2:
- Incorporated Scott's Review comments
Documentation/devicetree/bindings/tdm/fsl-tdm.txt | 67 +++
Stephen Rothwell wrote:
>Hi Jesse,
>
>On Fri, 9 Mar 2012 10:28:46 -0800 Jesse Barnes
> wrote:
>>
>> On Fri, 9 Mar 2012 14:46:45 +1100
>> Anton Blanchard wrote:
>>
>> > > Looks like something that got fixed but the new patches from
>Bjorn
>> > > aren't in next yet. I'll fwd you the patch separat
From: Paul Gortmaker
Date: Sun, 18 Mar 2012 17:39:17 -0400
> The following changes since commit cdf485be3a63d1f34293740fb726088c6840ceea:
>
> ixgbe: dcb: use DCB config values for FCoE traffic class on open
> (2012-03-14 00:49:10 -0700)
>
> are available in the git repository at:
>
> git:
Grant Likely wrote:
> The problem is that you want to create devices for grandchildren
> nodes when the bus ids passed in don't match any of the child nodes so
> the of_platform_bus_probe() doesn't iterate down to that level. This
> is correct and expected behaviour.
Well, I'm not still not 100%
On 03/19/2012 12:32 PM, Timur Tabi wrote:
> Scott Wood wrote:
Scott, are you suggesting that Poonam put a non-zero number in the DTS
for clock-frequency? If so, then I don't think that's a good idea, if
U-Boot will always override it.
>
>> This is a device tree binding document, no
Scott Wood wrote:
>> > Scott, are you suggesting that Poonam put a non-zero number in the DTS
>> > for clock-frequency? If so, then I don't think that's a good idea, if
>> > U-Boot will always override it.
> This is a device tree binding document, not U-Boot specific. It
> describes what Linux (
On 03/17/2012 02:33 AM, Aggrwal Poonam-B10812 wrote:
>>> + - compatible
>>> + Usage: required
>>> + Value type:
>>> + Definition: Should contain "fsl,mpc8315-tdm".
>>> + So mpc8313 will have compatible = "fsl,mpc8315-tdm";
>>> + p1010 will have compatible "fsl,p1010-tdm", "
On 03/17/2012 11:07 AM, Tabi Timur-B04825 wrote:
> On Sat, Mar 17, 2012 at 2:33 AM, Aggrwal Poonam-B10812
> wrote:
>>
+ compatible = "fsl,p1010-tdm", "fsl,mpc8315-tdm";
+ reg = <0x16000 0x200 0x2c000 0x2000>;
+ clock-frequency = <0>;
>>>
>>> Show a real
On Mon, Mar 19, 2012 at 11:06:39AM -0500, Timur Tabi wrote:
> Remove the check for CONFIG_PPC_85xx and CONFIG_PPC_86xx from fsl_guts.h.
> The check was originally intended to allow the same header file to
> be used on 85xx and 86xx systems, even though the Global Utilities
> register could be diffe
Remove the check for CONFIG_PPC_85xx and CONFIG_PPC_86xx from fsl_guts.h.
The check was originally intended to allow the same header file to
be used on 85xx and 86xx systems, even though the Global Utilities
register could be different. It turns out that they're not actually
different, and so the
On Fri, 16 Mar 2012 15:50:44 -0500, Timur Tabi wrote:
> Kumar Gala wrote:
>
> > This seems like paper taping over the real issue. We should be able to
> > call of_platform_bus_probe() multiple times.
>
> I tried debugging it, but I couldn't figure it out. My guess is that the
> nodes probed b
On Mon, Mar 19, 2012 at 12:49 AM, Benjamin Herrenschmidt
wrote:
> On Sun, 2012-03-18 at 18:04 +0400, Dmitry Eremin-Solenikov wrote:
>> On Sun, Mar 18, 2012 at 4:46 AM, Benjamin Herrenschmidt
>> wrote:
>> > On Sat, 2012-03-17 at 20:04 +0400, Dmitry Eremin-Solenikov wrote:
>> >> Hello,
>> >>
>> >>
On Tue, 2012-03-13 at 20:08 +0530, Vinod Koul wrote:
> On Tue, 2012-03-13 at 12:31 +, Russell King - ARM Linux wrote:
> > On Tue, Mar 13, 2012 at 02:10:36PM +0530, Vinod Koul wrote:
> > > Please see if the below patch is the right fix for build failures in
> > > addition to one suggested by Jas
Hi all,
I am developing on a custom mpc5125 board.
The hardware people designed the board so that the console serial port (PSC1 as
ttyPSC0) is "shared" with a 74HC595 shift register (!!),
which drivers some leds.
In other words: when I want to drive the leds I have to "switch" the port in
spi mo
Hi Wolfram,
On Mon, 19 Mar 2012 09:37:24 +0100
Wolfram Sang wrote:
...
> > Applied slightly modified patch to mpc5xxx next.
>
> Given that the patch was sent nearly one year ago and it even got
> modified, could please resend it to the list before applying?
Yes, done.
Thanks,
Anatolij
From: Heiko Schocher
If firmware does not setup the "GPS Port Configuration Register"
and the "CDM 48MHz Fractional Divider Configuration Register",
it can be corrected by additional properties in the device tree.
Add appropriate code to utility functions and document used
bindings.
Signed-off-b
On Mon, Mar 19, 2012 at 12:25:07AM +0100, Anatolij Gustschin wrote:
> Hi Heiko,
>
> On Tue, 19 Apr 2011 08:04:05 +0200
> Heiko Schocher wrote:
>
> > If firmware does not setup the "GPS Port Configuration Register"
> > and the "CDM 48MHz Fractional Divider Configuration Register",
> > it can be c
21 matches
Mail list logo
