Including: T104xRDB T208xQDS B4QDS
Signed-off-by: Jia Hongtao
---
arch/powerpc/boot/dts/b4qds.dtsi| 11 +++
arch/powerpc/boot/dts/t104xrdb.dtsi | 7 +++
arch/powerpc/boot/dts/t208xqds.dtsi | 11 +++
3 files changed, 29 insertions(+)
diff --git a/arch/powerpc/boot/dts/b4
Including: P3041DS P5020DS P5040DS B4QDS
Signed-off-by: Jia Hongtao
---
arch/powerpc/boot/dts/b4qds.dtsi | 12
arch/powerpc/boot/dts/p3041ds.dts | 20
arch/powerpc/boot/dts/p5020ds.dts | 20
arch/powerpc/boot/dts/p5040ds.dts | 20 ++
On Mon, 2014-11-03 at 21:11 -0800, Guenter Roeck wrote:
> On 11/03/2014 08:47 PM, Michael Ellerman wrote:
> > I've put the pm_power_off patch in a topic branch:
> >
> >
> > https://git.kernel.org/cgit/linux/kernel/git/mpe/linux.git/log/?h=topic/pm-power-off
> Excellent.
>
> Right now all I ca
^
Caused by commit 315786ebbf4a ("iommu: Add iommu_map_sg() function").
Grep is your friend ...
I have used the iommu tree from next-20141104 for today.
--
Cheers,
Stephen Rothwells...@canb.auug.org.au
pgpEwgb8fm1KU.pgp
Des
The hard lockup detector uses a PMU event as a periodic NMI to
detect if we are stuck (where stuck means no timer interrupts have
occurred).
Ben's rework of the ppc64 soft disable code has made ppc64 PMU
exceptions a partial NMI. They can get disabled if an external
interrupt comes in, but otherwi
On Tue, Nov 04, 2014 at 12:02:32PM -0800, Kees Cook wrote:
> > I considered doing that, but didn't want to risk listing too many
> > details of one architecture, and too few of others.
>
> Well, the others only say "memory mapped peripherals", so that's what
> I was suggesting adding the x86 langu
On Tue, Nov 4, 2014 at 11:59 AM, Leif Lindholm wrote:
> On Tue, Nov 04, 2014 at 10:43:00AM -0800, Kees Cook wrote:
>> > diff --git a/drivers/char/Kconfig b/drivers/char/Kconfig
>> > index efefd12..39f7817 100644
>> > --- a/drivers/char/Kconfig
>> > +++ b/drivers/char/Kconfig
>> > @@ -6,6 +6,22 @@
On Tue, Nov 04, 2014 at 10:43:00AM -0800, Kees Cook wrote:
> > diff --git a/drivers/char/Kconfig b/drivers/char/Kconfig
> > index efefd12..39f7817 100644
> > --- a/drivers/char/Kconfig
> > +++ b/drivers/char/Kconfig
> > @@ -6,6 +6,22 @@ menu "Character devices"
> >
> > source "drivers/tty/Kconfig"
On Tue, Nov 4, 2014 at 9:23 AM, Leif Lindholm wrote:
> Most, but not all, architectures supporting CONFIG_STRICT_DEVMEM treat
> it as a debug feature - although its function is pretty much the
> opposite of debug.
>
> This patch deletes all architecture-specific config options and moves
> the opti
Most, but not all, architectures supporting CONFIG_STRICT_DEVMEM treat
it as a debug feature - although its function is pretty much the
opposite of debug.
This patch deletes all architecture-specific config options and moves
the option to core code, as a non-debug option.
Signed-off-by: Leif Lind
On Oct 31, 2014, at 2:24 AM, qiang.z...@freescale.com wrote:
> On Oct 30, 2014, at 9:37 AM, Kumar Gala wrote:
>
>
>> -Original Message-
>> From: Kumar Gala [mailto:ga...@kernel.crashing.org]
>> Sent: Thursday, October 30, 2014 9:37 PM
>> To: Zhao Qiang-B45475
>> Cc: linuxppc-dev@lists.o
On Tue, Nov 04, 2014 at 10:45:20AM +, Grant Likely wrote:
> Currently the devices created by drivers/of/platform.c get created at
> the root of /sys/devices. This goes against the typical pattern for
> sysfs where the top level /sys/devices structure contains categories of
> devices, and the st
On Tue, 2014-11-04 at 10:45 +, Grant Likely wrote:
> Currently the devices created by drivers/of/platform.c get created at
> the root of /sys/devices. This goes against the typical pattern for
> sysfs where the top level /sys/devices structure contains categories of
> devices, and the structure
From: Shaohui Xie
This binding is for FMan MDIO, it covers FMan v2 & FMan v3.
Signed-off-by: Shaohui Xie
---
based on http://patchwork.ozlabs.org/patch/390351/
for 'next' of git://git.kernel.org/pub/scm/linux/kernel/git/scottwood/linux.git
.../devicetree/bindings/powerpc/fsl/fman.txt |
Currently the devices created by drivers/of/platform.c get created at
the root of /sys/devices. This goes against the typical pattern for
sysfs where the top level /sys/devices structure contains categories of
devices, and the structure of devices is placed below that. To fix this,
make the code in
On 11/03/2014 11:18 PM, Scott Wood wrote:
> Is it really necessary for the virqs to be contiguous? How is the
> availability of multiple MSIs communicated to the driver? Is there an
> example of a driver that currently uses multiple MSIs?
I used this in PCI and after enabling 2^x, I allocated an
16 matches
Mail list logo
