From: Grant Likely grant.lik...@secretlab.ca
PPC_OF is always selected for arch/powerpc. This patch removes the stale
#defines
Signed-off-by: Grant Likely grant.lik...@secretlab.ca
Acked-by: Stephen Rothwell s...@canb.auug.org.au
Acked-by: Kumar Gala ga...@kernel.crashing.org
---
From: Grant Likely grant.lik...@secretlab.ca
The PCI device tree scanning code in pci_64.c is some useful functionality.
It allows PCI devices to be described in the device tree instead of being
probed for, which in turn allows pci devices to use all of the device tree
facilities to describe
From: Grant Likely grant.lik...@secretlab.ca
The two versions are doing almost exactly the same thing. No need to
maintain them as separate files. This patch also has the side effect
of making the PCI device tree scanning code available to 32 bit powerpc
machines, but no board ports actually
Hi guys
Here's v2 of the PCI device tree scanning code. This is tested and
working on 32bit. It needs to be tested on 64 bit, but there shouldn't
be any behavioural changes. It's mostly just a code move with a little
bit of fixups to merge code. I'd like to see this go into .32 when the
merge
Hi guys
Here's v2 of the PCI device tree scanning code. This is tested and
working on 32bit. It needs to be tested on 64 bit, but there shouldn't
be any behavioural changes. It's mostly just a code move with a little
bit of fixups to merge code. I'd like to see this go into .32 when the
merge
Hi,
Cpuidle is a CPU Power Management infrastrusture which helps manage
idle CPUs in a clean and efficient manner. The architecture can register
its driver (in this case, pseries_idle driver) so that it subscribes for
cpuidle feature. Cpuidle has a set of governors (ladder and menu),
which will
* Arun R Bharadwaj a...@linux.vnet.ibm.com [2009-08-26 16:37:21]:
This patch enables the cpuidle option in Kconfig for pSeries.
Currently cpuidle infrastructure is enabled only for x86.
This code is almost completely borrowed from x86 to enable
cpuidle for pSeries.
Signed-off-by: Arun R
* Arun R Bharadwaj a...@linux.vnet.ibm.com [2009-08-26 16:37:21]:
This patch creates arch/powerpc/platforms/pseries/processor_idle.c,
which implements the cpuidle infrastructure for pseries.
It implements a pseries_cpuidle_loop() which would be the main idle loop
called from cpu_idle(). It makes
* Peter Zijlstra a.p.zijls...@chello.nl [2009-08-26 13:27:18]:
On Wed, 2009-08-26 at 16:40 +0530, Arun R Bharadwaj wrote:
+void (*pm_idle)(void);
+EXPORT_SYMBOL_GPL(pm_idle);
Seriously.. this caused plenty problems over on x86 and you're doing the
exact same dumb thing?
Hi Peter,
On Wed, 2009-08-26 at 16:40 +0530, Arun R Bharadwaj wrote:
+void (*pm_idle)(void);
+EXPORT_SYMBOL_GPL(pm_idle);
Seriously.. this caused plenty problems over on x86 and you're doing the
exact same dumb thing?
___
Linuxppc-dev mailing list
The old code used a lot of hardcoded values, which might not be valid in all
environments (especially routed fabrics or partitioned subnets). Copy as
much information as possible from the incoming request to prevent that.
Signed-off-by: Joachim Fenkes fen...@de.ibm.com
---
Hal, Jason -- here's
On Wed, 2009-08-26 at 17:02 +0530, Arun R Bharadwaj wrote:
* Peter Zijlstra a.p.zijls...@chello.nl [2009-08-26 13:27:18]:
On Wed, 2009-08-26 at 16:40 +0530, Arun R Bharadwaj wrote:
+void (*pm_idle)(void);
+EXPORT_SYMBOL_GPL(pm_idle);
Seriously.. this caused plenty problems over on
On Mon, 2009-08-24 at 21:48 +0200, Christoph Hellwig wrote:
On Mon, Aug 24, 2009 at 11:17:14AM -0500, Becky Bruce wrote:
Previously, this was specified as a void *, but that's not
large enough on 32-bit systems with 36-bit physical
addressing support. Change the type to dma_addr_t so it
On Aug 26, 2009, at 1:07 AM, Grant Likely wrote:
From: Grant Likely grant.lik...@secretlab.ca
The PCI device tree scanning code in pci_64.c is some useful
functionality.
It allows PCI devices to be described in the device tree instead of
being
probed for, which in turn allows pci devices
Hi all,
Im trying to develop a driver for my device, and its data bus can be 8, 16
or 32 bits. This information is passed through the device tree source.
My code is like this:
struct device_info_t {
void (*read)();
void (*write)();
};
static int __devinit device_probe()
{
On Wed, 2009-08-26 at 10:25 -0300, Alemao wrote:
Hi all,
Im trying to develop a driver for my device, and its data bus can be 8, 16
or 32 bits. This information is passed through the device tree source.
My code is like this:
struct device_info_t {
void (*read)();
void
On Wed, 2009-08-26 at 22:29 +1000, Benjamin Herrenschmidt wrote:
On Mon, 2009-08-24 at 21:48 +0200, Christoph Hellwig wrote:
On Mon, Aug 24, 2009 at 11:17:14AM -0500, Becky Bruce wrote:
Previously, this was specified as a void *, but that's not
large enough on 32-bit systems with 36-bit
In an assemblely code , I invalided all the TLB entries except for
the entry we are executed in.
After that , I setuped a 1:1 TLB entry mapping of 1GB .
At last , I wrote value 30 into the physical address 0x0400, (also
the virtual address because of my 1:1 mapping).
However, it seemed
On 8/26/09, Joachim Fenkes fen...@de.ibm.com wrote:
The old code used a lot of hardcoded values, which might not be valid in
all
environments (especially routed fabrics or partitioned subnets). Copy as
much information as possible from the incoming request to prevent that.
Signed-off-by:
[cc'ing some people who have made some commits in hvc_console.c]
On (Wed) Aug 26 2009 [16:57:18], Amit Shah wrote:
On (Tue) Aug 25 2009 [11:47:20], Amit Shah wrote:
Hello all,
Here is a new iteration of the patch series that implements a
transport for guest and host communications.
On Wed, Aug 26, 2009 at 7:29 AM, Kumar Galaga...@kernel.crashing.org wrote:
On Aug 26, 2009, at 1:07 AM, Grant Likely wrote:
+/**
+ * pci_scan_phb - Given a pci_controller, setup and scan the PCI bus
+ * @hose: Pointer to the PCI host controller instance structure
+ * @data: value to use
On Wed, Aug 26, 2009 at 10:39:24PM +0800, wilbur.chan wrote:
In an assemblely code , I invalided all the TLB entries except for
the entry we are executed in.
After that , I setuped a 1:1 TLB entry mapping of 1GB .
What is it you're trying to do?
At last , I wrote value 30 into the
On Aug 26, 2009, at 9:08 AM, Michael Ellerman wrote:
On Wed, 2009-08-26 at 22:29 +1000, Benjamin Herrenschmidt wrote:
On Mon, 2009-08-24 at 21:48 +0200, Christoph Hellwig wrote:
On Mon, Aug 24, 2009 at 11:17:14AM -0500, Becky Bruce wrote:
Previously, this was specified as a void *, but
On Thu, 27 Aug 2009 00:22:45 +1000 Michael Ellerman mich...@ellerman.id.au
wrote:
struct device_info_t {
void (*read)();
void (*write)();
These are not prototypes because there is no parameter list (use void for
empty).
};
static int __devinit device_probe()
This isn't a
On Wed, 2009-08-26 at 15:20 -0500, Becky Bruce wrote:
On Aug 26, 2009, at 9:08 AM, Michael Ellerman wrote:
On Wed, 2009-08-26 at 22:29 +1000, Benjamin Herrenschmidt wrote:
On Mon, 2009-08-24 at 21:48 +0200, Christoph Hellwig wrote:
On Mon, Aug 24, 2009 at 11:17:14AM -0500, Becky Bruce
On Thu, 2009-08-13 at 10:55 +0200, Ingo Molnar wrote:
Ok! We could also stage it a bit (one or two weeks) in a separate
branch and allow a rebase, should you find any bugs during testing?
Allright so after various delays and sidetracking on my side, the
patches have been in my -test branch
On Thu, 2009-08-27 at 13:12 +1000, Benjamin Herrenschmidt wrote:
On Thu, 2009-08-13 at 10:55 +0200, Ingo Molnar wrote:
Ok! We could also stage it a bit (one or two weeks) in a separate
branch and allow a rebase, should you find any bugs during testing?
Allright so after various delays
Hi Linus !
Here are a couple of last minute patches for 2.6.31. One is a regression fix
(afaik) where a PS3 driver gets incorrectly loaded on other platforms and
crashes, along with a PS3 defconfig update.
The following changes since commit f415c413f458837bd0c27086b79aca889f9435e4:
Linus
On Wed, 2009-08-26 at 13:27 +0200, Peter Zijlstra wrote:
On Wed, 2009-08-26 at 16:40 +0530, Arun R Bharadwaj wrote:
+void (*pm_idle)(void);
+EXPORT_SYMBOL_GPL(pm_idle);
Seriously.. this caused plenty problems over on x86 and you're doing the
exact same dumb thing?
I already said I didn't
On Mon, 2009-08-24 at 08:42 +0530, M. Mohan Kumar wrote:
Invoke kdump for system reset exception
Dump restart operation from HMC raises system reset exception
(0x100) and xmon is invoked(even if kdump kernel is loaded). User has to
exit from xmon by saying 'Don't recover' to invoke kdump.
On Wed, 2009-08-26 at 21:15 +0530, Amit Shah wrote:
- Convert hvc's usage of spinlocks to mutexes. I've no idea how this
will play out; I'm no expert here. But I did try doing this and so far
it all looks OK. No lockups, lockdep warnings, nothing. I have full
debugging enabled.
On Tue, 2009-08-18 at 14:21 +1000, Benjamin Herrenschmidt wrote:
So here's a followup to my discussion about the clock API.
Really nobody has a comment here ? :-) Not even Mitch ?
Cheers,
Ben.
I'm cooking up a patch that replace our current primitive implementation
in
On Tue, 2009-08-25 at 00:08 -0600, Grant Likely wrote:
From: Grant Likely grant.lik...@secretlab.ca
This patch allows the Xilinx intc interrupt controller to be cascaded
instead of being the master irqhost. Useful when attaching an FPGA
to an SoC that has its own interrupt controller.
On POWER6 systems RA needs to be the base and RB the index.
If they are reversed you take a misdirect hit.
Signed-off-by: Mike Wolf mjw...@us.ibm.com
Looks good thanks Mike!
Acked-by: Michael Neuling mi...@neuling.org
--- altivec.orig/arch/powerpc/include/asm/ppc_asm.h
Hi ~
I found the code in the linux kernel.
static __inline__ void clear_page(void *addr)
{
unsigned long lines, line_size;
line_size = cpu_caches.dline_size;
lines = cpu_caches.dlines_per_page;
__asm__ __volatile__(
mtctr %1 # clear_page\n\
1: dcbz
On Wed, 2009-08-26 at 21:15 +0530, Amit Shah wrote:
[cc'ing some people who have made some commits in hvc_console.c]
On (Wed) Aug 26 2009 [16:57:18], Amit Shah wrote:
On (Tue) Aug 25 2009 [11:47:20], Amit Shah wrote:
Hello all,
Here is a new iteration of the patch series that
On Wed, Aug 26, 2009 at 10:09 PM, Benjamin
Herrenschmidtb...@kernel.crashing.org wrote:
On Tue, 2009-08-18 at 14:21 +1000, Benjamin Herrenschmidt wrote:
So here's a followup to my discussion about the clock API.
Really nobody has a comment here ? :-) Not even Mitch ?
Been wanting too.. a
On Wed, 2009-08-26 at 00:07 -0600, Grant Likely wrote:
From: Grant Likely grant.lik...@secretlab.ca
The two versions are doing almost exactly the same thing. No need to
maintain them as separate files. This patch also has the side effect
of making the PCI device tree scanning code
38 matches
Mail list logo
