Badari Pulavarty writes:
> I am not able to boot my Power5 box with 2.6.27-rc8 (defconfig).
> However, I am able to boot with my own custom config.
>
> Known issue ?
No, and I wasn't able to replicate it on a power5 partition here...
Could you look up what is at 0xc097a02c in your vmlin
Minor nits ...
One is, you add this helper to mm/page_alloc.c, which means that I'll
need some ack from Hugh or Andrew before I can merge that via the
powerpc tree... Unless there's another user, I'd rather keep the
helper function in powerpc code for now, it can be moved to common
code later if s
On Fri, 2008-10-03 at 08:53 -0700, Jesse Barnes wrote:
> Tony and/or Bjorn, do you want to take a look and make sure this is ok? If
> so
> I can take the whole thing into the PCI tree.
Don't take patch 2/2, only 1/2. If/when you do, I'll then get the
powerpc side patch via the powerpc tree, as
Hi All,
Is there any BSP on kernel 2.4 for MPC8360EMDS board?
Thanks,
Mike
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
On Fri, Sep 26, 2008 at 12:19 PM, Timur Tabi <[EMAIL PROTECTED]> wrote:
> The Kconfig files for PowerPC CHRP and PMAC support had "default=y" for some
> Kconfig options, and this caused support for CHRP and PMAC platforms to be
> enabled incorrectly for several platforms. Fix the Kconfigs and the
If there are multiple reserved memory blocks via lmb_reserve() that are
contiguous addresses and on different NUMA nodes we are losing track of which
address ranges to reserve in bootmem on which node. I discovered this
when I only recently got to try 16GB huge pages on a system with more
then
On Mon, Oct 06, 2008 at 03:41:19PM -0500, Matt Sealey wrote:
> There is a simple problem with the patch which is that an "IRQ 0" can and does
> actually exist on a bunch of platforms, at least to the best of my knowledge.
>
> Checking for -1 (which means for definite, no irq at all, because it is
On Mon, 2008-10-06 at 11:05 +1100, Benjamin Herrenschmidt wrote:
> On Fri, 2008-10-03 at 10:40 -0700, Badari Pulavarty wrote:
> > Hi,
> >
> > I am not able to boot my Power5 box with 2.6.27-rc8 (defconfig).
> > However, I am able to boot with my own custom config.
> >
> > Known issue ?
>
> Nope.
Benjamin Herrenschmidt wrote:
This is what we were recommended to use at the time. There is a patch
on www.powerdeveloper.org which tweaks the tree to make it ultra-compliant
with the Linux version of things, which implements every variation. It
also implements a suggested patch which added a "bi
Kumar Gala wrote:
>
> On Oct 6, 2008, at 10:42 AM, Jon Tollefson wrote:
>
>> Kumar Gala wrote:
>>> Out of interest how to do you guys represent NUMA regions of memory in
>>> the device tree?
>>>
>>> - k
>> Looking at the source code in numa.c I see at the start of
>> do_init_bootmem() that parse_nu
There is a simple problem with the patch which is that an "IRQ 0" can and does
actually exist on a bunch of platforms, at least to the best of my knowledge.
Checking for -1 (which means for definite, no irq at all, because it is
totally unambiguous, as a -1 IRQ numbering is "impossible") is more
On Mon, Oct 06, 2008 at 11:31:58AM -0600, Grant Likely wrote:
> On Mon, Oct 06, 2008 at 09:28:31PM +0400, Anton Vorontsov wrote:
> > On Wed, Oct 01, 2008 at 03:39:48PM +0400, Anton Vorontsov wrote:
> > [...]
> > > > > Any issues with this or the second patch? Can we merge them?
> > > >
> > > > I d
On Mon, 2008-10-06 at 11:30 -0500, Scott Wood wrote:
> Remi Machet wrote:
> > After continuing to work on the dma noncoherent code I realized that
> > sync_page is not the best choice of API:
> > -The API should preferably take a dma_addr_t in my opinion
>
> A virtual address will typically be ne
On Mon, Oct 06, 2008 at 09:28:31PM +0400, Anton Vorontsov wrote:
> On Wed, Oct 01, 2008 at 03:39:48PM +0400, Anton Vorontsov wrote:
> [...]
> > > > Any issues with this or the second patch? Can we merge them?
> > >
> > > I do not have the time to review these patches (and, honestly, have no
> > >
On Wed, Oct 01, 2008 at 03:39:48PM +0400, Anton Vorontsov wrote:
[...]
> > > Any issues with this or the second patch? Can we merge them?
> >
> > I do not have the time to review these patches (and, honestly, have no
> > interest in them.) So I will not merge them but I have no objection to
> > th
When no irq specified the pata_of_platform fills the irq_res with -1,
which is wrong to do for two reasons:
1. By definition, 'no irq' should be IRQ 0, not some negative integer;
2. pata_platform checks for irq_res.start > 0, but since irq_res.start
is unsigned type, the check will be true for
In the standalone setup the board's CPLD disables the PCI internal
arbiter, thus any access to the PCI bus will hang the board.
The common way to disable particular devices in the device tree is to
put the "status" property with any value other than "ok" or "okay"
into the device node we want to d
With this API we're able to set a QE pin to the GPIO mode or a dedicated
peripheral function.
The API relies on the fact that QE gpio controllers are registered. If
they aren't, the API won't work (gracefully though).
There is one caveat though: if anybody occupied the node->data before us,
or ov
The helper is factored out of of_get_gpio(). Will be used by the QE
pin multiplexing functions (they need to parse the gpios = <> too).
Signed-off-by: Anton Vorontsov <[EMAIL PROTECTED]>
---
drivers/of/base.c | 111
drivers/of/gpio.c | 77
Hi all,
The API is eveloved from the approach where I tried to put the
qe_set_dedicated() function into the GPIO LIB framework, which
wasn't good idea after all (see http://lkml.org/lkml/2008/9/24/289).
So here is the new version. Since the patchset touches driver/of/
I need Acks from the OF guys
Remi Machet wrote:
After continuing to work on the dma noncoherent code I realized that
sync_page is not the best choice of API:
-The API should preferably take a dma_addr_t in my opinion
A virtual address will typically be needed to perform the flush; why
pass the bus address?
-Scott
On Oct 6, 2008, at 10:42 AM, Jon Tollefson wrote:
Kumar Gala wrote:
Out of interest how to do you guys represent NUMA regions of memory
in
the device tree?
- k
Looking at the source code in numa.c I see at the start of
do_init_bootmem() that parse_numa_properties() is called. It
appears
System log shows a lot of "ehea: Error", see below, during system start up.
Not sure what it is. I'd like to understand this, could someone points me
the direction? My "Machine Type and Model ... ST9146802SS" reported from
lscfg (p6 blade). OS is RHEL 5.2. Kernel level is 2.6.18-92.1.10.el5.
Kumar Gala wrote:
> Out of interest how to do you guys represent NUMA regions of memory in
> the device tree?
>
> - k
Looking at the source code in numa.c I see at the start of
do_init_bootmem() that parse_numa_properties() is called. It appears to
be looking at memory nodes and getting the node i
On Oct 6, 2008, at 8:42 AM, Leon Woestenberg wrote:
Hello all,
can Freescale or any of the powerpc maintainers indicate to what
extend PCI Express support for the MPC8315E processor has been merged
to Linux mainline, or what is still needs review or attention?
I could find u-boot and Linux p
Hello all,
can Freescale or any of the powerpc maintainers indicate to what
extend PCI Express support for the MPC8315E processor has been merged
to Linux mainline, or what is still needs review or attention?
I could find u-boot and Linux patches provided by Freescale in their
open-source patch
On Tue, 30 Sep 2008, Niklaus Giger wrote:
> The patch is against the master git of denx.de. It does not apply cleanly
> against linus' git as I cannot find there any include/asm-ppc subdirectory.
{arch/,include-asm-}ppc/ has been removed, in favor of arch/powerpc/.
With kind regards,
Geert Uytt
27 matches
Mail list logo
