Hi Linus !
Here's the 3 patches Kumar was complaining I forgot to pull :-)
Two are pretty old patches related to FSL RapidIO stuff, and
one is a bug fix.
Cheers,
Ben.
The following changes since commit dc7acbb2518f250050179c8581a972df3b6a24f1:
Merge branch 'upstream/tidy-xen-mmu-2.6.39' of
All,
This isn't really a Linux PPC question, but this is the smartest mailing
list I know for asking PPC hardware questions, so here goes.
We're using an MPC8308 and want to use the DMA engine to move data in and
out of an FPGA hanging on the local bus. Our bandwidth/local bus burden
calculat
fsl_hypervisor.h includes an ioctl interface, so it should be made available
via "make headers_install".
Signed-off-by: Timur Tabi
---
This adds one change that I forgot to include in my previous patch,
"drivers/misc: introduce Freescale hypervisor management driver".
Kumar, if at all possible,
On Thu, 2011-05-26 at 09:02 -0500, Kumar Gala wrote:
> Ben,
>
> Did you ignore my pull request with a bug fix and two long standing
> RIO patches?
I suppose I did ... oops :-)
I'll send that today.
Cheers,
Ben.
___
Linuxppc-dev mailing list
Linuxppc
On Fri, 20 May 2011 11:36:38 -0500
Meador Inge wrote:
> This binding documents how the message register blocks found in some FSL
> MPIC implementations shall be represented in a device tree.
>
> Signed-off-by: Meador Inge
> Cc: Hollis Blanchard
> Cc: Grant Likely
> Cc: Benjamin Herrenschmidt
On Fri, 20 May 2011 11:36:38 -0500
Meador Inge wrote:
> This binding documents how the message register blocks found in some FSL
> MPIC implementations shall be represented in a device tree.
>
> Signed-off-by: Meador Inge
> Cc: Hollis Blanchard
> Cc: Grant Likely
> Cc: Benjamin Herrenschmidt
From: Dave Carroll
When using 64K pages with a separate cpio rootfs, U-Boot will align
the rootfs on a 4K page boundary. When the memory is reserved, and
subsequent early memblock_alloc is called, it will allocate memory
between the 64K page alignment and reserved memory. When the reserved
memory
Scott, I addressed your feedback in this patch set:
* 1/2 - http://lists.ozlabs.org/pipermail/linuxppc-dev/2011-May/090405.html
* 2/2 - http://lists.ozlabs.org/pipermail/linuxppc-dev/2011-May/090406.html
Ben, my Cc for you didn't go through the first time.
> This patch set defines a bind
On May 26, 2011, at 12:22 AM, Benjamin Herrenschmidt wrote:
> Hi Linus !
>
> This is a bit more than I expected to send you that late in the merge
> window, but hopefully none of it should be problematic. A couple of
> patches were simply delayed due to misunderstandings as to which tree
> they
On Thu, 26 May 2011 about 13:32:33 +1000, Benjamin Herrenschmidt wrote:
> > On Wed, 2011-05-25 at 01:34 -0500, Milton Miller wrote:
> > > The 8xx cpm_cascade was calling irq_eoi for the cascaded irq,
> > > but that will already have been called by the handle_fasteoi_irq
> > > that generic_handle_ir
On Wed, 25 May 2011 about 20:32:42 -0600, Dave Carroll wrote:
> When using 64K pages with a separate cpio rootfs, U-Boot will align
> the rootfs on a 4K page boundary. When the memory is reserved, and
> subsequent early memblock_alloc is called, it will allocate memory
> between the 64K page align
On many platforms (including pSeries), smp_ops->message_pass is always
smp_muxed_ipi_message_pass. This changes arch/powerpc/kernel/smp.c so
that if smp_ops->message_pass is NULL, it calls smp_muxed_ipi_message_pass
directly.
This means that a platform doesn't need to set both .message_pass and
.
* Thomas Gleixner wrote:
> > If anything then that should tell you something that events and
> > seccomp are not just casually related ...
>
> They happen to have the hook at the same point in the source and
> for pure coincidence it works because the problem to solve is
> extremly simplisti
On Thu, May 26, 2011 at 12:33:29PM +0530, Priyanka Jain wrote:
> PT7C4338 chip is being manufactured by Pericom Technology Inc.
> It is a serial real-time clock which provides:
> 1)Low-power clock/calendar.
> 2)Programmable square-wave output.
> It has 56 bytes of nonvolatile RAM.
> Its register s
* Thomas Gleixner wrote:
> > > We do _NOT_ make any decision based on the trace point so
> > > what's the "pre-existing" active role in the syscall entry
> > > code?
> >
> > The seccomp code we are discussing in this thread.
>
> That's proposed code and has absolutely nothing to do with the
* Pavel Machek wrote:
> On Mon 2011-05-16 10:36:05, James Morris wrote:
> > On Fri, 13 May 2011, Ingo Molnar wrote:
> > How do you reason about the behavior of the system as a whole?
> >
> >
> > > I argue that this is the LSM and audit subsystems designed right: in the
> > > long
> > > run
Hi Andrew Morton,
I have added the support for pt7c4338 in Dallas driver rtc-ds1307.c as
suggested by Wolfram Sang
And send the patch "Add support for pt7c4338 (rtc device) in rtc-ds1307 driver"
for the same which will supersede the previous patch.
Please let me know if anything else is require
PT7C4338 chip is being manufactured by Pericom Technology Inc.
It is a serial real-time clock which provides:
1)Low-power clock/calendar.
2)Programmable square-wave output.
It has 56 bytes of nonvolatile RAM.
Its register set is same as that of rtc device: DS1307.
Signed-off-by: Priyanka Jain
---
18 matches
Mail list logo
