pr_debug() can now result in code being generated even when #DEBUG
is not defined. That's not really desirable in the ftrace code
which we want to be snappy.
With CONFIG_DYNAMIC_DEBUG=y:
size before:
textdata bss dec hex filename
3334 672 44010 faa
On Thu, Jan 08, 2009 at 11:53:10PM -0600, Matt Sealey wrote:
Lennert Buytenhek wrote:
On Thu, Jan 08, 2009 at 11:38:33PM -0600, Matt Sealey wrote:
On this topic, I sent a patch to linuxppc-dev@ some time ago that moves
the mv643xx_eth SRAM window programming code from the Pegasos platform
Hi All,
I have a custom board similar to MPC8560ADS board with 1GB DDR SDRAM. The DDR
SDRAM Make
is MT18VDDF12872DG-335D3. In U-BOOT (2009.01) config file I have enabled
CONFIG_SPD_EEPROM
so U-boot configures MPC8560ADS DDR controller with the values read from
SPD_EEPROM (i2c
address 0x51)
On Wed, 13 May 2009, Andrew Morton wrote:
On Tue, 28 Apr 2009 09:24:53 +0200 (CEST)
Geert Uytterhoeven geert.uytterhoe...@sonycom.com wrote:
On Tue, 28 Apr 2009, Stephen Rothwell wrote:
On Mon, 27 Apr 2009 14:50:31 -0700 Andrew Morton
a...@linux-foundation.org wrote:
powerpc
This fixes MAL (arbitration lost) bug caused by illegal use of
RSTA (repeated START) after STOP condition generated after last byte
of reads.
Signed-off-by: Esben Haabendal e...@doredevelopment.dk
---
drivers/i2c/busses/i2c-mpc.c |9 +++--
1 files changed, 7 insertions(+), 2
Nick Piggin wrote:
This one possibly looks like a problem with remote memory allocation
or memory hotplug or something like that. I'll do a bit of code
review
Removed linux-scsi from the cc list.
I can recreate this issue with today's next tree. Nick let me know if
you need any other
On Thu, May 14, 2009 at 10:10:03AM +0200, Esben Haabendal wrote:
This fixes MAL (arbitration lost) bug caused by illegal use of
RSTA (repeated START) after STOP condition generated after last byte
of reads.
Could you elaborate a bit, please? Like an example when the original bug
occured (so I
Wolfram Sang wrote:
On Thu, May 14, 2009 at 10:10:03AM +0200, Esben Haabendal wrote:
This fixes MAL (arbitration lost) bug caused by illegal use of
RSTA (repeated START) after STOP condition generated after last byte
of reads.
Could you elaborate a bit, please? Like an example when
Hi Sachin,
On Thu, 2009-05-14 at 14:00 +0530, Sachin Sant wrote:
Nick Piggin wrote:
This one possibly looks like a problem with remote memory allocation
or memory hotplug or something like that. I'll do a bit of code
review
Removed linux-scsi from the cc list.
I can recreate this
Hi,
I just tried upgrading my PegasosII to 2.6.29, and found that the Marvell
driver shows two Ethernet ports now, one with a MAC address ending in
...:de:ad:01 (which is the port that is not wired to the outside), and the
other one with 00:00:00:00:00:00.
I think some sort of Pegasos specific
On Thu, May 14, 2009 at 10:59:02AM +0200, Simon Richter wrote:
Hi,
I just tried upgrading my PegasosII to 2.6.29, and found that the Marvell
driver shows two Ethernet ports now, one with a MAC address ending in
...:de:ad:01 (which is the port that is not wired to the outside), and the
other
Wolfram Sang wrote:
On Thu, May 14, 2009 at 10:10:03AM +0200, Esben Haabendal wrote:
This fixes MAL (arbitration lost) bug caused by illegal use of
RSTA (repeated START) after STOP condition generated after last byte
of reads.
Could you elaborate a bit, please? Like an example
On Thu, 2009-05-14 at 15:24 +0530, Sachin Sant wrote:
Pekka Enberg wrote:
I wasn't able to find your .config in this thread. Can you please post
it?
Config attached.
Thanks! Can you please enable CONFIG_DEBUG_VM, CONFIG_DEBUG_LIST, and
decrease CONFIG_NR_CPUS=1024 to, say, 32 and
Hi Sachin,
On Thu, 2009-05-14 at 12:59 +0300, Pekka Enberg wrote:
On Thu, 2009-05-14 at 15:24 +0530, Sachin Sant wrote:
Pekka Enberg wrote:
I wasn't able to find your .config in this thread. Can you please post
it?
Config attached.
Thanks! Can you please enable
ramdisk...
ramdisk loaded 007b9f91 @ 02f0
OF stdout device is: /vdevice/v...@3000
Preparing to boot Linux version 2.6.30-rc5-autotest-next-20090514
(r...@mpower6lp5) (gcc version 4.3.2 [gcc-4_3-branch revision 141291] (SUSE
Linux) ) #2 SMP Thu May 14 16:36:26 IST 2009
Calling ibm,client
The i2c_device_name() macro is used only once and doesn't have much
value, it hurts redability more than it helps. Get rid of it.
Signed-off-by: Jean Delvare kh...@linux-fr.org
Cc: Benjamin Herrenschmidt b...@kernel.crashing.org
---
sound/ppc/keywest.c |6 +-
1 file changed, 1
Thursday 07 May 2009 00:39:25 Grant Likely napisał(a):
512x are enabled in the same kernel?
Hm... both architectures look sufficiently different to me that I
don't see sense in trying such a thing. Do you think that needs to be
supported?
Yes! :-) It's not hard to do and it keeps the
At Thu, 14 May 2009 14:37:21 +0200,
Jean Delvare wrote:
The i2c_device_name() macro is used only once and doesn't have much
value, it hurts redability more than it helps. Get rid of it.
Signed-off-by: Jean Delvare kh...@linux-fr.org
Cc: Benjamin Herrenschmidt b...@kernel.crashing.org
David Gibson wrote:
It is not THE dtb, it is A dtb. Our systems support and typically use
multiple FPGA bit streams.
Ah, ok. And those multiple bitstreams all inhabit the same NOR flash?
From what I read below I'm guessing not..
In my work they virtually always do, but in
Hi All,
Please find a revised patchset that implement hardware breakpoint
interfaces for PPC64 architecture. The changes over the previous patchset
posted here: http://ozlabs.org/pipermail/linuxppc-dev/2009-May/071942.html
are given below.
Kindly let me know your comments about the same.
Prepare the PowerPC code for HW Breakpoint infrastructure patches by including
relevant constant definitions and function declarations.
Signed-off-by: K.Prasad pra...@linux.vnet.ibm.com
---
arch/powerpc/include/asm/hw_breakpoint.h | 49 +
arch/powerpc/include/asm/processor.h |1
Introduce PPC64 implementation for the generic hardware breakpoint interfaces
defined in kernel/hw_breakpoint.c. Enable the HAVE_HW_BREAKPOINT flag and the
Makefile.
Signed-off-by: K.Prasad pra...@linux.vnet.ibm.com
---
arch/powerpc/Kconfig|1
arch/powerpc/kernel/Makefile
Modify the ptrace code to use the hardware breakpoint interfaces for user-space.
Signed-off-by: K.Prasad pra...@linux.vnet.ibm.com
---
arch/powerpc/kernel/ptrace.c | 48 +
Index: linux-2.6-tip.hbkpt/arch/powerpc/kernel/ptrace.c
Modify process handling code to recognise hardware debug registers during copy
and flush operations. Introduce a new TIF_DEBUG task flag to indicate a
process's use of debug register.
Signed-off-by: K.Prasad pra...@linux.vnet.ibm.com
---
arch/powerpc/include/asm/thread_info.h |2
Modify Data storage exception code to first lookout for a DABR match before
recognising a kprobe or xmon exception.
Signed-off-by: K.Prasad pra...@linux.vnet.ibm.com
---
arch/powerpc/mm/fault.c | 14 -
Index: linux-2.6-tip.hbkpt/arch/powerpc/mm/fault.c
Modify kexec code to disable DABR registers before a reboot. Adapt the samples
code to populate PPC64-arch specific fields.
Signed-off-by: K.Prasad pra...@linux.vnet.ibm.com
---
arch/powerpc/kernel/machine_kexec_64.c |6
samples/hw_breakpoint/data_breakpoint.c |4
Index:
On Thu, 14 May 2009, K.Prasad wrote:
Modify kexec code to disable DABR registers before a reboot. Adapt the samples
code to populate PPC64-arch specific fields.
Signed-off-by: K.Prasad pra...@linux.vnet.ibm.com
---
arch/powerpc/kernel/machine_kexec_64.c |6
2009/5/14 Piotr Zięcik ko...@semihalf.com:
Thursday 07 May 2009 00:39:25 Grant Likely napisał(a):
512x are enabled in the same kernel?
Hm... both architectures look sufficiently different to me that I
don't see sense in trying such a thing. Do you think that needs to be
supported?
On Thu, 2009-05-14 at 15:59 +0200, Geert Uytterhoeven wrote:
On Thu, 14 May 2009, K.Prasad wrote:
Modify kexec code to disable DABR registers before a reboot. Adapt the
samples
code to populate PPC64-arch specific fields.
Signed-off-by: K.Prasad pra...@linux.vnet.ibm.com
---
On Fri, 15 May 2009, Michael Ellerman wrote:
On Thu, 2009-05-14 at 15:59 +0200, Geert Uytterhoeven wrote:
On Thu, 14 May 2009, K.Prasad wrote:
Modify kexec code to disable DABR registers before a reboot. Adapt the
samples
code to populate PPC64-arch specific fields.
On Thu, 2009-05-14 at 19:14 +0530, K.Prasad wrote:
plain text document attachment (ppc64_arch_hwbkpt_implementation_02)
Introduce PPC64 implementation for the generic hardware breakpoint interfaces
defined in kernel/hw_breakpoint.c. Enable the HAVE_HW_BREAKPOINT flag and the
Makefile.
Hi,
From: Dave Liu dave...@freescale.com
The bit 11 of command description is reserved bit in Freescale
SATA controller and needs to be set to '1'. This is needed to
make sure the last write from the controller to the buffer
descriptor is seen before an interrupt is raised.
Signed-off-by: Dave Liu
On Thu, 2009-05-14 at 19:15 +0530, K.Prasad wrote:
plain text document attachment (ppc64_modify_process_handling_04)
Index: linux-2.6-tip.hbkpt/arch/powerpc/kernel/process.c
===
---
On Thu, 2009-05-14 at 16:18 +0200, Geert Uytterhoeven wrote:
On Fri, 15 May 2009, Michael Ellerman wrote:
On Thu, 2009-05-14 at 15:59 +0200, Geert Uytterhoeven wrote:
On Thu, 14 May 2009, K.Prasad wrote:
Modify kexec code to disable DABR registers before a reboot. Adapt the
samples
On Tue, May 5, 2009 at 3:53 PM, Timur Tabi ti...@freescale.com wrote:
The macro spin_event_timeout() takes a condition and timeout value
(in microseconds) as parameters. It spins until either the condition is true
or the timeout expires. It returns the result of the condition when the loop
I'm fine with this patch, but it should go via the PPC tree.
Acked-by: Steven Rostedt rost...@goodmis.org
-- Steve
On Thu, 14 May 2009, Michael Ellerman wrote:
pr_debug() can now result in code being generated even when #DEBUG
is not defined. That's not really desirable in the ftrace code
Grant Likely wrote:
This version looks good to me. Who's the first user? (I'd like to see
that something is ready to use this before merging it)
I was going to do it the other way around - wait until this patch is merged,
and then update some code to use it. After all, it's easier to use a
Hello all.
I'm working on a driver for a custom board (based heavily on the
MPC8349EMDS board) to dump data out of onboard FPGA's. I need to use the
onboard DMA controller for this, mostly due to data transfer rate and
timing requirements.
Of course, I'd like to play nice with the existing Linux
On Thu, 2009-05-14 at 09:13 -0700, Ira Snyder wrote:
Hello all.
I'm working on a driver for a custom board (based heavily on the
MPC8349EMDS board) to dump data out of onboard FPGA's. I need to use the
onboard DMA controller for this, mostly due to data transfer rate and
timing
Hi Ben,
Here are some more commits which got missed in the last merge cycle.
I've based this on top of Kumar's pull request from yesterday to
minimize merge commits.
Note: This pull request replaces my previous pull request. I rebased
the series since some of the commits in my previous request
Esben Haabendal esbenhaaben...@gmail.com wrote on 14/05/2009 12:17:48:
On Thu, May 14, 2009 at 11:58 AM, Joakim Tjernlund
joakim.tjernl...@transmode.se wrote:
The problem is that after the STOP condition, the following i2c_msg will be
attempted with a repeated START, which according to
On Thu, May 14, 2009 at 09:27:17AM -0700, Dan Williams wrote:
On Thu, 2009-05-14 at 09:13 -0700, Ira Snyder wrote:
Hello all.
I'm working on a driver for a custom board (based heavily on the
MPC8349EMDS board) to dump data out of onboard FPGA's. I need to use the
onboard DMA controller
On Wed, May 13, 2009 at 12:57:17PM +1000, David Gibson wrote:
On Wed, May 13, 2009 at 01:55:45AM +0530, K.Prasad wrote:
On Tue, May 12, 2009 at 07:51:49AM -0400, Josh Boyer wrote:
On Tue, May 12, 2009 at 01:33:55AM +0530, K.Prasad wrote:
[snip]
It seems to me that a kind of minimal
On Thu, May 14, 2009 at 03:59:45PM +0200, Geert Uytterhoeven wrote:
On Thu, 14 May 2009, K.Prasad wrote:
Modify kexec code to disable DABR registers before a reboot. Adapt the
samples
code to populate PPC64-arch specific fields.
Signed-off-by: K.Prasad pra...@linux.vnet.ibm.com
---
On Fri, May 15, 2009 at 12:50:11AM +1000, Michael Ellerman wrote:
On Thu, 2009-05-14 at 19:14 +0530, K.Prasad wrote:
plain text document attachment (ppc64_arch_hwbkpt_implementation_02)
Introduce PPC64 implementation for the generic hardware breakpoint
interfaces
defined in
On Fri, 15 May 2009, K.Prasad wrote:
I see that you're referring to this code in __switch_to() :
if (unlikely(__get_cpu_var(current_dabr) != new-thread.dabr))
set_dabr(new-thread.dabr);
arch_install_thread_hw_breakpoint()--switch_to_thread_hw_breakpoint()
On Thu, 14 May 2009, K.Prasad wrote:
Index: linux-2.6-tip.hbkpt/samples/hw_breakpoint/data_breakpoint.c
===
--- linux-2.6-tip.hbkpt.orig/samples/hw_breakpoint/data_breakpoint.c
2009-05-14 00:17:24.0 +0530
+++
Previouslly we just always set the inbound window to 2G. This was
broken for systems with 2G. If a system has =4G we will need
SWIOTLB support to handle that case.
We now allocate PCICSRBAR/PEXCSRBAR right below the lowest PCI outbound
address for MMIO or the 4G boundary (if the lowest PCI
On Wed, May 13, 2009 at 08:27:07AM +0200, Heiko Schocher wrote:
Hello Wolfgang,
The current device tree for the MPC8272ADS assumes a mapping of 32 MB
of NOR flash at 0xFE00., while there are actually only 8 MB on
the boards, mapped at 0xFF80.. When booting an uImage with such a
Currently, the 32-bit code uses sg-length instead of sg-dma_lentgh
to report sg_dma_len. However, since the default dma code for 32-bit
(the dma_direct case) sets dma_length and length to the same thing,
we should be able to use dma_length there as well. This gets rid of
some 32-vs-64-bit
This is the final bit of code to allow enabling swiotlb on
mpc86xx. The platform-specific code is very small and consists
of enabling SWIOTLB in the config file, registering the
swiotlb_setup_bus_notifier initcall, and setting pci_dma_ops
to point to swiotlb_pci_dma_ops if we have more memory
I have a custom board similar to MPC8560ADS board with 1GB
DDR SDRAM. The DDR SDRAM Make
is MT18VDDF12872DG-335D3. In U-BOOT (2009.01) config file I
have enabled CONFIG_SPD_EEPROM
so U-boot configures MPC8560ADS DDR controller with the
values read from SPD_EEPROM (i2c
address 0x51)
Hi, friends,
I move the u-boot patched from http://www.evidence.eu.com/content/view/104/169/
to my IXP460 board. There are some difference between ixdp465 board and my
ixp460 board. The cpu part number is different, my ixp460 board have 128MB ddr
memory(MT46V32M16-6T ), and 16MB flash
My previous pach for fixing the oprofile CPU type got somewhat mismerged
(by my fault) when it collided with another related patch. This should
finally (fingers crossed) fix the whole thing.
We make sure we keep the -old- oprofile type and CPU type whenever
one of them was specified in the first
On Thu, 2009-05-14 at 10:41 -0600, Grant Likely wrote:
Hi Ben,
Here are some more commits which got missed in the last merge cycle.
I've based this on top of Kumar's pull request from yesterday to
minimize merge commits.
Note: This pull request replaces my previous pull request. I
On May 14, 2009, at 5:42 PM, Becky Bruce wrote:
This patch includes the basic infrastructure to use swiotlb
bounce buffering on 32-bit powerpc. It is not yet enabled on
any platforms. Probably the most interesting bit is the
addition of addr_needs_map to dma_ops - we need this as
a dma_op
Add the platform-specific code for enabling SWIOTLB if needed on P2020DS,
MPC85xx DS, and MPC85xx MDS boards as they are capable of having 4G of
memory.
We determine if we need to enable swiotlb based on how much memory is in
the board and if it exceeds 4G or what we can map via PCI inbound
57 matches
Mail list logo
