The PTRACE_SETREGS request was only recently added on powerpc,
and gdb does not use it. So it slipped through without getting
all the testing it should have had.
The user_regset changes had a simple bug in storing to all of
the 32-bit general registers block on 64-bit kernels. This bug
only
Hi Tony,
On Thu, Mar 13, 2008 at 08:20:05AM +1100, Tony Breeds wrote:
[..snip..]
where pmu_sys_suspended is referenced and I'm having difficulty
understanding how CONFIG_HIBERNATION is affecting that.
I mangled the filenames and didn't notice that you fixed the header file
instead of via-pmu.c.
Define the copy_siginfo_from_user32 entry point for powerpc, so
that generic CONFIG_COMPAT code can call it. We already had the
code rolled into compat_sys_rt_sigqueueinfo, this just moves it
out into the canonical function that other arch's define.
Signed-off-by: Roland McGrath [EMAIL
This adds support for PTRACE_GETSIGINFO and PTRACE_SETSIGINFO in
compat_ptrace_request. It relies on existing arch definitions for
copy_siginfo_to_user32 and copy_siginfo_from_user32.
On powerpc, this fixes a longstanding regression of 32-bit ptrace
calls on 64-bit kernels vs native calls
This removes the special-case handling for PTRACE_GETSIGINFO
and PTRACE_SETSIGINFO from x86_64's sys32_ptrace. The generic
compat_ptrace_request code handles these.
Signed-off-by: Roland McGrath [EMAIL PROTECTED]
---
arch/x86/kernel/ptrace.c | 30 +-
1 files
Now that there are no more special cases in sys32_ptrace, we
can convert to using the generic compat_sys_ptrace entry point.
The sys32_ptrace function gets simpler and becomes compat_arch_ptrace.
Signed-off-by: Roland McGrath [EMAIL PROTECTED]
---
arch/x86/ia32/ia32entry.S |2 +-
On Tue, Mar 11, 2008 at 10:44:06PM -0400, Theodore Ts'o wrote:
Stephen Rothwell discovered this issue in the linux-next tree:
Today's powerpc allmodconfig build of linux-next failed with:
ERROR: empty_zero_page [fs/ext4/ext4dev.ko] undefined!
This is because commit
On Wed, 12 Mar 2008, York Sun wrote:
The following patches are for Freescale DIU. The first patch is a DIU driver.
The second patch is the platform code to support the driver. It is a frame
buffer driver for DIU. Descriptions can be found in the patches.
It is a new feature targeting 2.6.26
Matthew Wilcox wrote:
On Thu, Mar 13, 2008 at 09:26:09AM +1100, Michael Ellerman wrote:
down() looks OK, but there's still a spin_lock_irq() in __down_common(),
although I don't know if it makes sense for us to be in __down() at that
stage.
The spin_lock_irq in __down_common is correct.
On Wed, 2008-03-12 at 23:30 +0100, Jens Osterkamp wrote:
Just to make sure, i tested the binary against the 2.6.25-rc4 kernel. It
still fails. So this is really an open bug for PPC.
On a Cell- or 970-based machine ?
Gruß,
Jens
On a 970-based machine.
Regards,
--
Luis Machado
Hi Michael,
On Wednesday 12 March 2008 01:51, Michael Ellerman wrote:
On Tue, 2008-03-11 at 11:58 +0100, Laurent Pinchart wrote:
Hi everybody,
is there any documentation describing interrupt handling for the powerpc
architecture ? I'm writing a driver for a cascaded interrupt controller
Hi Dave,
On Tuesday 11 March 2008 23:54, David Gibson wrote:
On Tue, Mar 11, 2008 at 03:27:26PM +0100, Laurent Pinchart wrote:
Hi everybody,
the migration process from ARCH=ppc to ARCH=powerpc is easier than I
thought in some parts, but a few devices are still giving me
headaches. This
On Thu, Mar 13, 2008 at 01:32:43AM -0700, Roland McGrath wrote:
On powerpc, this fixes a longstanding regression of 32-bit ptrace
calls on 64-bit kernels vs native calls (64-bit calls or 32-bit
kernels). This can be seen in a 32-bit call using PTRACE_GETSIGINFO
to examine e.g.
On Friday 22 February 2008, Valentine Barshak wrote:
Move the skb-ip_summed == CHECKSUM_PARTIAL part out of
emac_has_feature parameters.
Signed-off-by: Valentine Barshak [EMAIL PROTECTED]
Acked-by: Stefan Roese [EMAIL PROTECTED]
I think this is 2.6.25 material. I just stumbled over this
Add ibm,tah to the compatible matching table of the ibm_newemac
tah driver. The type tah is still preserved for compatibility reasons.
New dts files should use the compatible property though.
Signed-off-by: Stefan Roese [EMAIL PROTECTED]
---
drivers/net/ibm_newemac/tah.c |4
1 files
This patch adds TAH (TCP/IP Acceleration Hardware) support to the
taishan 440GX dts. It depends on the NEWEMAC/tah patch that adds the
compatible ibm,tah property to the matching table.
Signed-off-by: Stefan Roese [EMAIL PROTECTED]
---
arch/powerpc/boot/dts/taishan.dts | 13 +
1
Hi LinuxPPC Guru's
I am sending these leads your way on behalf of Cisco's Embedded system
software manager.
Please send responses to [EMAIL PROTECTED]
Cisco has 3 positions which are very similar 2 Technical lead positions
and 1 Sr. Software Engineer position(Linux, Power PC, Bring up and
On Tue, Mar 11, 2008 at 10:04:11AM -0700, Dan Williams wrote:
I notice that the driver does not handle callbacks in its descriptor
cleanup path. This could be ok if your intent is only to support the
net_dma style polled operations, but this will not work for the
raid-offload async_tx case.
A couple of places are duplicating the function of
of_device_is_available; convert them to use it.
Signed-off-by: Nathan Lynch [EMAIL PROTECTED]
---
This depends on Josh Boyer's patch [OF] Add of_device_is_available
function:
http://patchwork.ozlabs.org/linuxppc/patch?id=17100
Problems.
Subject: [PATCH -mm 1/4] powerpc copy_siginfo_from_user32
This is advertised as a -mm patch but afacit it isn't against -mm. And it
doesn't seem to be against mainline either? At least, the fourth patch
fails to apply.
When trying to apply the fourth patch to -mm I hit a reject
On Wed, Mar 12, 2008 at 12:57 PM, René Bürgel [EMAIL PROTECTED] wrote:
Here is a patch for the lite5200 to get the FEC working again for kernel
=2.6.24. It was created against Linux 2.6.24.
The FEC driver is also compatible with the MPC5200, not only with the
MPC5200B, so an according
AFAICT the DABRX register just has two global bits that enable paying
attention to the DABR register.
It has four bits:
01 match in user mode
02 match in supervisor mode
04 match in hypervisor mode
08 ignore translation field in DABR
If the
On Thu, Mar 13, 2008 at 12:54 PM, Olof Johansson [EMAIL PROTECTED] wrote:
On Tue, Mar 11, 2008 at 10:04:11AM -0700, Dan Williams wrote:
I notice that the driver does not handle callbacks in its descriptor
cleanup path. This could be ok if your intent is only to support the
net_dma
Since the 970 kernel never sets DABRX currently, #8 cannot explain
_intermittent_ problems: either it always works, or never does.
That's kind of what I thought, but I couldn't make enough sense of
the #8 text to be very sure.
You could be happening upon #5, if the non-triggering data
On Thu, Mar 13, 2008 at 03:29:29PM -0700, Dan Williams wrote:
On Thu, Mar 13, 2008 at 12:54 PM, Olof Johansson [EMAIL PROTECTED] wrote:
On Tue, Mar 11, 2008 at 10:04:11AM -0700, Dan Williams wrote:
I notice that the driver does not handle callbacks in its descriptor
cleanup path.
This is advertised as a -mm patch but afacit it isn't against -mm. And it
doesn't seem to be against mainline either? At least, the fourth patch
fails to apply.
Oops, sorry for the bad labeling. The baseline I used was actually x86/mm.
(This was originally going to be just some x86_64
From: John Linn [EMAIL PROTECTED]
This change to the OF serial driver causes it to setup a console
which then gets the OF data and sets up the 8250 console. Prior to
this the uart was not setup in time for the 8250 console initialization
to work correct.
It appears that the kernel console uart
On Thu, Mar 13, 2008 at 4:14 PM, Olof Johansson [EMAIL PROTECTED] wrote:
Dummy descriptors that do nothing but cause an interrupt is the intent.
Well, it'd be slightly more efficient to do add the interrupt attribute
to the last issued descriptor when it's known in advance. If the
The pointer to the test case was given here before.
Oh, I missed that. Anyway, I wanted to see the asm, and who knows,
with different compiler versions and all that.
0x1984 child_thread+52: bl 0x10001750 sleep
0x1988 child_thread+56: lis r9,4097
---
Manish Ahuja writes:
If Mike and Paul are okay, then I will leave this bit as is and fix all
other issues and comments.
Well, part of the problem is the semantic dissonance caused by having
a static variable called global. Please change the name
phyp_dump_global to phyp_dump_vars or
30 matches
Mail list logo