>> Can you paste the whole log from the u-boot prompt?
>
> In the previous run the ramdisk image was corrupted because the single
> image was loaded at 0x80. But the boot message showed that the
> initrd image was at 0x0066c000-0x009ae825. So it was over the 8MB
> area.
>
> However after the lo
> -Original Message-
> From:
> linuxppc-dev-bounces+tiejun.chen=windriver@lists.ozlabs.or
> g
> [mailto:linuxppc-dev-bounces+tiejun.chen=windriver@lists.o
zlabs.org] On Behalf Of david.hag...@gmail.com
> Sent: Wednesday, September 22, 2010 11:56 PM
> To: linuxppc-...@ozlabs.org
>
On Wed, 22 Sep 2010 12:32:20 +0200
Maria Johansen wrote:
> I am working on an MPC8308rdb, and have needed to add support for spi
> and an lm75 thermal sensor on the i2c-bus. Is it possible to upload my
> changes to the "official" mpc8308rdb.dts, or should I just keep
> modifying it locally and ho
>> I have a large ramdisk image. The size of the image itself (i.e. the
>> *.gz) is about 4MB. When the ramdisk was being decompressed
>
> Did you try to change link_address on the file, arch/powerpc/boot/wrapper?
No. I don't have to. Right? The link_address is still 0x40.
> Did you try boot
Sorry for the late reply, but I was on vacation when you sent this, and
I missed it while going through email.
Do you still have this issue?
-- Steve
On Sat, 2010-08-07 at 01:31 +0200, Jörg Sommer wrote:
> Hi,
>
> I've built my 2.6.35 with tracing support and now, I'm getting
> continuously oo
On Wed, 2010-09-22 at 13:40 -0500, Nathan Fontenot wrote:
> On 09/22/2010 10:20 AM, Dave Hansen wrote:
> >and phys_index's calculation needs to be:
> >
> > mem->start_phys_index * SECTION_SIZE / memory_block_size_bytes()
>
> I'm not sure if I follow where you sugg
On 09/22/2010 10:20 AM, Dave Hansen wrote:
> On Wed, 2010-09-22 at 09:15 -0500, Nathan Fontenot wrote:
>> For architectures that define their own version of this routine,
>> as is done for powerpc in this patchset, the view in userspace
>> would change such that each memoryXXX directory would span
I am trying to get the PCIe interfaces of a Freescale MPC8641D working in
endpoint mode (i.e. as a PCI device rather than a PCI root complex host).
I can get the device to show up on the host's PCI bus, I can program the
inbound ATMUs such that the BARS are updated when the host (re-)scans
them, b
Firstly you should make sure which interrupt level is used to trigger
the external interrupt. High level, low level, rising edge or falling
edge?
--
0 = low to high edge sensitive type enabled
1 = active low level sensitive type enabled
2 = active high level sensitive type enabled
3 = high
On Wed, 2010-09-22 at 09:15 -0500, Nathan Fontenot wrote:
> For architectures that define their own version of this routine,
> as is done for powerpc in this patchset, the view in userspace
> would change such that each memoryXXX directory would span
> multiple memory sections. The number of secti
Update the memory hotplug documentation to reflect the new behaviors of
memory blocks reflected in sysfs.
Signed-off-by: Nathan Fontenot
---
Documentation/memory-hotplug.txt | 46 +--
1 file changed, 30 insertions(+), 16 deletions(-)
Index: linux-next/Docu
Define a version of memory_block_size_bytes() for powerpc/pseries such that
a memory block spans an entire lmb.
Signed-off-by: Nathan Fontenot
---
arch/powerpc/platforms/pseries/hotplug-memory.c | 66 +++-
1 file changed, 53 insertions(+), 13 deletions(-)
Index: linux-nex
Update the node sysfs code to be aware of the new capability for a memory
block to span multiple memory sections. This requires an additional
parameter to unregister_mem_sect_under_nodes so that we know which memory
section of the memory block to unregister.
Signed-off-by: Nathan Fontenot
---
Update the memory sysfs code such that each sysfs memory directory is now
considered a memory block that can span multiple memory sections per
memory block. The default size of each memory block is SECTION_SIZE_BITS
to maintain the current behavior of having a single memory section per
memory bloc
Add a new mutex for use in adding and removing of memory blocks. This
is needed to avoid any race conditions in which the same memory block could
be added and removed at the same time.
Signed-off-by: Nathan Fontenot
---
drivers/base/memory.c |7 +++
1 file changed, 7 insertions(+)
Ind
Add a section count property to the memory_block struct to track the number
of memory sections that have been added/removed from a memory block. This
allows us to know when the last memory section of a memory block has been
removed so we can remove the memory block.
Signed-off-by: Nathan Fontenot
Update the 'phys_index' properties of a memory block to include a
'start_phys_index' which is the same as the current 'phys_index' property.
The property still appears as 'phys_index' in sysfs but the memory_block
struct name is updated to indicate the start and end values.
This also adds an 'end_p
Move the find_memory_block() routine up to avoid needing a forward
declaration in subsequent patches.
Signed-off-by: Nathan Fontenot
---
drivers/base/memory.c | 62 +-
1 file changed, 31 insertions(+), 31 deletions(-)
Index: linux-next/drivers/
> -Original Message-
> From: Shawn Jin [mailto:shawnx...@gmail.com]
> Sent: Wednesday, September 22, 2010 1:43 PM
> To: Chen, Tiejun
> Cc: Scott Wood; ppcdev; uboot
> Subject: Re: [U-Boot] cuImage and multi image?
>
> >> > > A follow up question. With this method, the total image size
> >
This set of patches decouples the concept that a single memory
section corresponds to a single directory in
/sys/devices/system/memory/. On systems
with large amounts of memory (1+ TB) there are performance issues
related to creating the large number of sysfs directories. For
a powerpc machine w
Hi Ralf,
> On Tue, Sep 21, 2010 at 06:29:16PM -0700, Justin P. Mattock wrote:
> > Date: Tue, 21 Sep 2010 18:29:16 -0700
> > From: "Justin P. Mattock"
> > To: triv...@kernel.org
> > Cc: linux-arm-ker...@lists.infradead.org, linux-ker...@vger.kernel.org,
> > linux-o...@vger.kernel.org, linux-m..
On Tue, Sep 21, 2010 at 06:29:16PM -0700, Justin P. Mattock wrote:
> Date: Tue, 21 Sep 2010 18:29:16 -0700
> From: "Justin P. Mattock"
> To: triv...@kernel.org
> Cc: linux-arm-ker...@lists.infradead.org, linux-ker...@vger.kernel.org,
> linux-o...@vger.kernel.org, linux-m...@ml.linux-m32r.org,
>
Hi,
I am working on an MPC8308rdb, and have needed to add support for spi
and an lm75 thermal sensor on the i2c-bus. Is it possible to upload my
changes to the "official" mpc8308rdb.dts, or should I just keep
modifying it locally and hope the maintainers of the file will add
support for more devic
On Tue, Sep 21, 2010 at 04:47:45PM -0400, Kyle Moffett wrote:
> Well how about something much more straightforward:
I am about to post another patch set for discussion, so please comment
on it when it appears.
Thanks,
Richard
___
Linuxppc-dev mailing li
Hi
i have a FPGA called mcmc which is connected to the powerpc mpc8572 on the
local bus. It provides 2 interrupts which are connected to the
external interupts IRQ1 and IRQ3 of the mpc8572.
the fpga is memory mapped on the local bus at address 0xc000
I am able to register the interrupt and obt
Signed-off-by: Lennert Buytenhek
diff --git a/Documentation/powerpc/booting-without-of.txt
b/Documentation/powerpc/booting-without-of.txt
index 302db5d..3272ed5 100644
--- a/Documentation/powerpc/booting-without-of.txt
+++ b/Documentation/powerpc/booting-without-of.txt
@@ -131,7 +131,7 @@ order
26 matches
Mail list logo
