On Wed, Dec 07, 2011 at 05:01:57PM -0200, Thiago Jung Bauermann wrote:
On Thu, 2011-12-01 at 15:50 +0530, K.Prasad wrote:
On Mon, Nov 28, 2011 at 02:11:11PM +1100, David Gibson wrote:
[snip]
On Wed, Oct 12, 2011 at 11:09:48PM +0530, K.Prasad wrote:
diff --git
* Matt Evans m...@ozlabs.org wrote:
PPC64 uses long long for u64 in the kernel, but powerpc's asm/types.h
prevents 64-bit userland from seeing this definition, instead defaulting
to u64 == long in userspace. Some user programs (e.g. kvmtool) may actually
want LL64, so this patch adds a
On 08/12/11 06:45, Kumar Gala wrote:
The Freescale serial port's are pretty much a 16550, however there are
some FSL specific bugs and features. Add a fsl,ns16550 compatiable
string to allow code to handle those FSL specific issues.
Signed-off-by: Kumar Gala ga...@kernel.crashing.org
For
于 2011年12月08日 03:11, Scott Wood 写道:
On 12/06/2011 09:55 PM, LiuShuo wrote:
于 2011年12月07日 08:09, Scott Wood 写道:
On 12/03/2011 10:31 PM, shuo@freescale.com wrote:
From: Liu Shuoshuo@freescale.com
Freescale FCM controller has a 2K size limitation of buffer RAM. In
order
to support the
Hi David,
Please find a revised version of the patchset which have
incorporated the various suggestions made by you.
Kindly review the patches and let me know if they look fine.
Changelog - v2
--
v1 posted at
There seems to be something wrong with cpu idle time accounting at least
on G5. The value as reported in the cpu lines in /proc/stat seems to be
stuck in the interval [10,21] for each cpu, jumping back at
random points. Any idea what could be the problem?
Andreas.
--
Andreas Schwab,
PPC_PTRACE_GETHWDBGINFO, PPC_PTRACE_SETHWDEBUG and PPC_PTRACE_DELHWDEBUG are
PowerPC specific ptrace flags that use the watchpoint register. While they are
targeted primarily towards BookE users, user-space applications such as GDB
have started using them for BookS too. This patch enables the use
While PPC_PTRACE_SETHWDEBUG ptrace flag in PowerPC accepts
PPC_BREAKPOINT_MODE_EXACT mode of breakpoint, the same is not intimated to the
user-space debuggers (like GDB) who may want to use it. Hence we introduce a
new PPC_DEBUG_FEATURE_DATA_BP_EXACT flag which will be populated on the
features
On Thu, 8 Dec 2011, Benjamin Herrenschmidt wrote:
On Thu, 2011-12-08 at 15:20 +1100, Benjamin Herrenschmidt wrote:
So basic operations seem to work, I've applied the patch to
powerpc-next.
Then I guess Geert should not push this for 3.3 -- or does it make no
difference?
However, the
Hi Finn,
On Thu, Dec 8, 2011 at 12:26, Finn Thain fth...@telegraphics.com.au wrote:
On Thu, 8 Dec 2011, Benjamin Herrenschmidt wrote:
On Thu, 2011-12-08 at 15:20 +1100, Benjamin Herrenschmidt wrote:
So basic operations seem to work, I've applied the patch to
powerpc-next.
Then I guess
On (Tue) 06 Dec 2011 [09:05:38], Miche Baker-Harvey wrote:
Amit,
Ah, indeed. I am not using MSI-X, so virtio_pci::vp_try_to_find_vqs()
calls vp_request_intx() and sets up an interrupt callback. From
there, when an interrupt occurs, the stack looks something like this:
I hate the idea of having a POWER7 FTR bit. Every loon will (and has
tried to in the past) attach every POWER7 related thing to it, rather
than thinking about what the feature really is for.
What about other processors which could also benefit from this copy
loop? Turning on CPU_FTR_POWER7 for
One idea would be to have a structure of function pointers for each
CPU that gets runtime patched into the right places,
similar to how we do some of the MMU fixups.
Sounds good to me :-)
Except the indirect jump/call is almost certainly
never predicted - so will be slow.
You might
One idea would be to have a structure of function pointers for each
CPU that gets runtime patched into the right places,
similar to how we do some of the MMU fixups.
Sounds good to me :-)
Except the indirect jump/call is almost certainly
never predicted - so will be slow.
What indirect
Just a quick question,
For Core 1 I am booting kernel using NFS. When I boot kernel on Core 1 it fails
at following point. Attached are my DTS files for both cores. My NFS server is
configured properly as I am booting Core 0 with the same server. I have used
packet sniffer on my NFS server and
On 12/07/2011 07:05 PM, Tabi Timur-B04825 wrote:
Scott Wood wrote:
+ interrupts =8 8 0 0;
+ };
It's not new to this patch, but... what does 8 mean in the second cell
of an mpic interrupt specifier?
I have no idea.
Valid values are 0 through 3.
And why does the
On 12/07/2011 09:36 PM, Liu Shengzhou-B36685 wrote:
-Original Message-
From: Wood Scott-B07421
Sent: Thursday, December 08, 2011 1:17 AM
To: Liu Shengzhou-B36685
Cc: Wood Scott-B07421; linuxppc-dev@lists.ozlabs.org; linux-
m...@lists.infradead.org; dw...@infradead.org; Gala
On 12/08/2011 04:44 AM, LiuShuo wrote:
于 2011年12月08日 03:11, Scott Wood 写道:
And if we do want to make such assumptions, we could rip out all usage
of index/column here, and just handle oob and full page cases.
The function nand_do_write_ops() in nandbase.c is a Nand internal
interface.
It
Hello,
While compiling linux-3.2-rc4 on PPC64, i get the following set of
warning series. I wanted to know if they are expected, or, they need to
be fixed:
LD arch/powerpc/sysdev/xics/built-in.o
WARNING: arch/powerpc/sysdev/xics/built-in.o(.text+0x136c): Section
mismatch in reference from
On Thu, 2011-12-08 at 17:04 +1100, Anton Blanchard wrote:
Hi,
I hate the idea of having a POWER7 FTR bit. Every loon will (and has
tried to in the past) attach every POWER7 related thing to it, rather
than thinking about what the feature really is for.
What about other processors
On Thu, 2011-12-08 at 22:26 +1100, Finn Thain wrote:
Maybe the modem wants a transition on DTR or similar, but it hasn't had
time to initialise when that happens during SCC resumption.
If so, calling pmz_shutdown() then pmz_startup() from the tail of
pmz_resume() without delay should
On 12/8/11, Andreas Schwab sch...@linux-m68k.org wrote:
There seems to be something wrong with cpu idle time accounting at least
on G5. The value as reported in the cpu lines in /proc/stat seems to be
stuck in the interval [10,21] for each cpu, jumping back at
random points. Any idea
Create a 32-bit address space version of p1022ds.dts. To avoid confusion,
p1022ds.dts is renamed to p1022ds_36b.dts. We also create p1022ds.dtsi
to store some common nodes.
Signed-off-by: Timur Tabi ti...@freescale.com
---
fix pixis interrupt property and added tbi node
On Fri, Dec 09, 2011 at 12:40:32AM +0530, Subrata Modak wrote:
Hello,
While compiling linux-3.2-rc4 on PPC64, i get the following set of
warning series. I wanted to know if they are expected, or, they need to
be fixed:
If you have time they should be fixed.
Yours Tony
pgpLJnfmz0SFz.pgp
On Thu, Dec 8, 2011 at 3:33 AM, Benjamin Herrenschmidt
b...@kernel.crashing.org wrote:
On Wed, 2011-12-07 at 13:35 +0530, Prashant Bhole wrote:
Still couldn't find anything like fifo overflow...
I noticed one more thing, this problem happens only when mtu size on
the initiator (the other
On Fri, 9 Dec 2011, Subrata Modak wrote:
WARNING: vmlinux.o(.text+0x4c760): Section mismatch in reference from
the function .mark_reserved_regions_for_nid() to the
function .meminit.text:.early_pfn_to_nid()
The function .mark_reserved_regions_for_nid() references
the function __meminit
read_n_cells() cannot be marked as .devinit.text since it is referenced
from two functions that are not in that section: of_get_lmb_size() and
hot_add_drconf_scn_to_nid().
Signed-off-by: David Rientjes rient...@google.com
---
arch/powerpc/mm/numa.c |2 +-
1 files changed, 1 insertions(+),
On Thu, 2011-12-08 at 18:31 +0530, Prashant Bhole wrote:
I checked RX descriptor status and TX descriptor status and ethtool
output.
However I don't know about pause packet/frame, how do I check if pause
frames are properly negotiated on both sides?
I need to try changing pause and FIFO
Hi Ben,
-Original Message-
From: Benjamin Herrenschmidt [mailto:b...@kernel.crashing.org]
Sent: Thursday, December 08, 2011 2:59 PM
To: Prashant Bhole
Cc: linuxppc-...@ozlabs.org; Tirumala Marri
Subject: Re: ibm_newemac tx problem with jumbo frame enabled
On Thu, 2011-12-08 at 18:31
Commit 4f5ca836bef3 (HID: hid-input: add support for HID devices
reporting Battery Strength) went into linux-next on Dec 1st since then a
ppc6xx_defconfig has been failing with:
---
drivers/built-in.o: In function `hidinput_cleanup_battery':
/scratch/tony/working/drivers/hid/hid-input.c:351:
Hi Josh,
Today's linux-next merge of the 4xx tree got a conflict in
arch/powerpc/platforms/40x/ppc40x_simple.c between commit 11eab297f57b
(powerpc: Add support for OpenBlockS 600) from the powerpc tree and
commit d5b9ee7b514e (powerpc/40x: Add APM8018X SOC support) from the
4xx tree.
I fixed it
Current linux-next compiled with mpc85xx_defconfig causes this:
arch/powerpc/platforms/85xx/p1010rdb.c:41:14: error: 'np' undeclared (first use
in this function)
arch/powerpc/platforms/85xx/p1023_rds.c:102:14: error: 'np' undeclared (first
use in this function)
Introduced in:
commit
On Thu, Dec 8, 2011 at 8:38 PM, Stephen Rothwell s...@canb.auug.org.au wrote:
Hi Josh,
Today's linux-next merge of the 4xx tree got a conflict in
arch/powerpc/platforms/40x/ppc40x_simple.c between commit 11eab297f57b
(powerpc: Add support for OpenBlockS 600) from the powerpc tree and
commit
Hi Josh,
On Thu, 8 Dec 2011 20:46:39 -0500 Josh Boyer jwbo...@gmail.com wrote:
I blame BenH. I sent him a pull request with d5b9ee7b514e in it
before he went and updated his tree. Still not pulled afaik. Guess
I'll be rebasing my next branch tomorrow to pick up a series from Tony
Breeds,
On Thu, 2011-12-08 at 20:46 -0500, Josh Boyer wrote:
On Thu, Dec 8, 2011 at 8:38 PM, Stephen Rothwell s...@canb.auug.org.au
wrote:
Hi Josh,
Today's linux-next merge of the 4xx tree got a conflict in
arch/powerpc/platforms/40x/ppc40x_simple.c between commit 11eab297f57b
(powerpc: Add
On 12/08/2011 05:27 PM, Tony Breeds wrote:
Commit 4f5ca836bef3 (HID: hid-input: add support for HID devices
reporting Battery Strength) went into linux-next on Dec 1st since then a
ppc6xx_defconfig has been failing with:
---
drivers/built-in.o: In function `hidinput_cleanup_battery':
36 matches
Mail list logo
