* Please pull powerpc.git merge branch
From: Paul Mackerras @ 2007-11-20 8:38 UTC (permalink / raw)
To: torvalds; +Cc: linuxppc-dev
Linus,
Please do
git pull \
git://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git merge
to get another batch of fixes for powerpc, as listed below.
Thanks,
Paul.
Documentation/powerpc/booting-without-of.txt | 5 +
arch/powerpc/boot/dts/mpc832x_mds.dts | 9 +-
arch/powerpc/boot/dts/mpc8544ds.dts | 20 ++--
arch/powerpc/boot/dts/mpc8572ds.dts | 108 ++++++++++++++++++---
arch/powerpc/boot/dts/mpc8641_hpcn.dts | 126 ++++++++++++++++++++----
arch/powerpc/kernel/asm-offsets.c | 4 +
arch/powerpc/kernel/rtas.c | 111 ++++++++++++---------
arch/powerpc/kernel/time.c | 5 +
arch/powerpc/kernel/vdso.c | 11 ++
arch/powerpc/kernel/vdso32/cacheflush.S | 41 ++++++--
arch/powerpc/kernel/vdso64/cacheflush.S | 41 ++++++--
arch/powerpc/mm/mem.c | 2
arch/powerpc/mm/mmu_decl.h | 2
arch/powerpc/mm/stab.c | 1
arch/powerpc/platforms/40x/walnut.c | 3 -
arch/powerpc/platforms/44x/bamboo.c | 3 -
arch/powerpc/platforms/44x/ebony.c | 3 -
arch/powerpc/platforms/44x/sequoia.c | 3 -
arch/powerpc/platforms/83xx/mpc832x_mds.c | 7 +
arch/powerpc/platforms/83xx/mpc836x_mds.c | 31 +++++-
arch/powerpc/platforms/83xx/usb.c | 8 +-
arch/powerpc/platforms/cell/spufs/inode.c | 1
arch/powerpc/platforms/embedded6xx/prpmc2800.c | 1
arch/powerpc/platforms/pasemi/setup.c | 2
arch/powerpc/platforms/pseries/Kconfig | 2
arch/powerpc/platforms/pseries/setup.c | 3 -
arch/powerpc/sysdev/uic.c | 18 +++
arch/ppc/kernel/setup.c | 7 +
arch/ppc/mm/init.c | 2
arch/ppc/mm/mmu_decl.h | 2
arch/ppc/platforms/4xx/yucca.c | 1
arch/ppc/syslib/virtex_devices.c | 31 ++++++
include/asm-powerpc/page_32.h | 4 +
include/asm-powerpc/pci-bridge.h | 5 +
include/asm-powerpc/rtas.h | 3 -
include/asm-powerpc/vdso_datapage.h | 8 ++
36 files changed, 486 insertions(+), 148 deletions(-)
Benjamin Herrenschmidt (3):
[POWERPC] Fix declaration of pcibios_free_controller
[POWERPC] Fix kmalloc alignment on non-coherent DMA platforms
[POWERPC] Fix 8xx build breakage due to _tlbie changes
Cyrill Gorcunov (1):
[POWERPC] Fix potential NULL dereference
Jeremy Kerr (1):
[POWERPC] spufs: Fix context destroy vs /spu readdir race
Joachim Foerster (1):
[POWERPC] Xilinx: Register AC97 Controller Reference with the platform bus
Jon Loeliger (1):
[POWERPC] 4xx: Replace #includes of asm/of_platform.h with linux/of_platform.h.
Josh Boyer (1):
[POWERPC] 4xx: Use virtual PVR value to init FPU on arch/ppc 440EP
Kamalesh Babulal (1):
[POWERPC] Fix build failure on legacy iSeries
Kim Phillips (4):
[POWERPC] 83xx: mpc832x mds: Fix board PHY reset code
[POWERPC] 83xx: Fix 2nd UCC entry in mpc832x_mds.dts
[POWERPC] Document rgmii-rxid and rgmii-txid phy-connection-types
[POWERPC] 83xx: Handle mpc8360 rev. 2.1 RGMII timing erratum
Kumar Gala (1):
[POWERPC] Fix device tree interrupt map for Freescale ULI1575 boards
Linas Vepstas (1):
[POWERPC] Fix RTAS os-term usage on kernel panic
Mark A. Greer (1):
[POWERPC] prpmc2800: Enable L2 cache
Michael Neuling (1):
[POWERPC] Fix possible division by zero in scaled time accounting
Nathan Lynch (1):
[POWERPC] Fix multiple bugs in rtas_ibm_suspend_me code
Olof Johansson (2):
[POWERPC] pasemi: Don't reset mpic at boot
[POWERPC] vdso: Fixes for cache block sizes
Roel Kluin (1):
[POWERPC] 4xx: balance ioremap/ioumap calls for Yucca
Stephen Rothwell (1):
[POWERPC] pSeries: make pseries_defconfig minus PCI build again
Valentine Barshak (1):
[POWERPC] 4xx: UIC add mask_ack callback
^ permalink raw reply
* [PATCH] ppc: 4xx: Fix TLB 0 problem with CONFIG_SERIAL_TEXT_DEBUG
From: Stefan Roese @ 2007-11-20 10:19 UTC (permalink / raw)
To: linuxppc-dev
Right now TLB entry 0 ist used as UART0 mapping for the early debug
output (via CONFIG_SERIAL_TEXT_DEBUG). This causes problems when many
TLB's get used upon Linux bootup (e.g. while PCIe scanning behind
bridges and/or switches on 440SPe platforms). This will overwrite the
TLB 0 entry and further debug output's may crash/hang the system.
This patch moves the early debug UART0 TLB entry from 0 to 62 as done
in arch/powerpc. This way it is in the "pinned" area and will not get
overwritten. Also the arch/ppc/mm/44x_mmu.c code is now synced with the
newer code from arch/powerpc.
Signed-off-by: Stefan Roese <sr@denx.de>
---
arch/ppc/kernel/head_44x.S | 2 +-
arch/ppc/mm/44x_mmu.c | 51 +++++++++++++------------------------------
include/asm-ppc/mmu.h | 6 +++++
3 files changed, 23 insertions(+), 36 deletions(-)
diff --git a/arch/ppc/kernel/head_44x.S b/arch/ppc/kernel/head_44x.S
index 75bbc93..ebb5a40 100644
--- a/arch/ppc/kernel/head_44x.S
+++ b/arch/ppc/kernel/head_44x.S
@@ -195,7 +195,7 @@ skpinv: addi r4,r4,1 /* Increment */
li r5,0
ori r5,r5,(PPC44x_TLB_SW | PPC44x_TLB_SR | PPC44x_TLB_I | PPC44x_TLB_G)
- li r0,0 /* TLB slot 0 */
+ li r0,62 /* TLB slot 62 */
tlbwe r3,r0,PPC44x_TLB_PAGEID /* Load the pageid fields */
tlbwe r4,r0,PPC44x_TLB_XLAT /* Load the translation fields */
diff --git a/arch/ppc/mm/44x_mmu.c b/arch/ppc/mm/44x_mmu.c
index 6536a25..fbb577a 100644
--- a/arch/ppc/mm/44x_mmu.c
+++ b/arch/ppc/mm/44x_mmu.c
@@ -60,38 +60,28 @@ extern char etext[], _stext[];
* Just needed it declared someplace.
*/
unsigned int tlb_44x_index = 0;
-unsigned int tlb_44x_hwater = 62;
+unsigned int tlb_44x_hwater = PPC4XX_TLB_SIZE - 1 - PPC44x_EARLY_TLBS;
int icache_44x_need_flush;
/*
* "Pins" a 256MB TLB entry in AS0 for kernel lowmem
*/
-static void __init
-ppc44x_pin_tlb(int slot, unsigned int virt, unsigned int phys)
+static void __init ppc44x_pin_tlb(unsigned int virt, unsigned int phys)
{
- unsigned long attrib = 0;
-
- __asm__ __volatile__("\
- clrrwi %2,%2,10\n\
- ori %2,%2,%4\n\
- clrrwi %1,%1,10\n\
- li %0,0\n\
- ori %0,%0,%5\n\
- tlbwe %2,%3,%6\n\
- tlbwe %1,%3,%7\n\
- tlbwe %0,%3,%8"
+ __asm__ __volatile__(
+ "tlbwe %2,%3,%4\n"
+ "tlbwe %1,%3,%5\n"
+ "tlbwe %0,%3,%6\n"
:
- : "r" (attrib), "r" (phys), "r" (virt), "r" (slot),
- "i" (PPC44x_TLB_VALID | PPC44x_TLB_256M),
- "i" (PPC44x_TLB_SW | PPC44x_TLB_SR | PPC44x_TLB_SX | PPC44x_TLB_G),
+ : "r" (PPC44x_TLB_SW | PPC44x_TLB_SR | PPC44x_TLB_SX | PPC44x_TLB_G),
+ "r" (phys),
+ "r" (virt | PPC44x_TLB_VALID | PPC44x_TLB_256M),
+ "r" (tlb_44x_hwater--), /* slot for this TLB entry */
"i" (PPC44x_TLB_PAGEID),
"i" (PPC44x_TLB_XLAT),
"i" (PPC44x_TLB_ATTRIB));
}
-/*
- * MMU_init_hw does the chip-specific initialization of the MMU hardware.
- */
void __init MMU_init_hw(void)
{
flush_instruction_cache();
@@ -99,22 +89,13 @@ void __init MMU_init_hw(void)
unsigned long __init mmu_mapin_ram(void)
{
- unsigned int pinned_tlbs = 1;
- int i;
-
- /* Determine number of entries necessary to cover lowmem */
- pinned_tlbs = (unsigned int)
- (_ALIGN(total_lowmem, PPC_PIN_SIZE) >> PPC44x_PIN_SHIFT);
-
- /* Write upper watermark to save location */
- tlb_44x_hwater = PPC44x_LOW_SLOT - pinned_tlbs;
+ unsigned long addr;
- /* If necessary, set additional pinned TLBs */
- if (pinned_tlbs > 1)
- for (i = (PPC44x_LOW_SLOT-(pinned_tlbs-1)); i < PPC44x_LOW_SLOT; i++) {
- unsigned int phys_addr = (PPC44x_LOW_SLOT-i) * PPC_PIN_SIZE;
- ppc44x_pin_tlb(i, phys_addr+PAGE_OFFSET, phys_addr);
- }
+ /* Pin in enough TLBs to cover any lowmem not covered by the
+ * initial 256M mapping established in head_44x.S */
+ for (addr = PPC_PIN_SIZE; addr < total_lowmem;
+ addr += PPC_PIN_SIZE)
+ ppc44x_pin_tlb(addr + PAGE_OFFSET, addr);
return total_lowmem;
}
diff --git a/include/asm-ppc/mmu.h b/include/asm-ppc/mmu.h
index 14584e5..d46b57b 100644
--- a/include/asm-ppc/mmu.h
+++ b/include/asm-ppc/mmu.h
@@ -383,6 +383,12 @@ typedef struct _P601_BAT {
#define BOOKE_PAGESZ_256GB 14
#define BOOKE_PAGESZ_1TB 15
+#ifndef CONFIG_SERIAL_TEXT_DEBUG
+#define PPC44x_EARLY_TLBS 1
+#else
+#define PPC44x_EARLY_TLBS 2
+#endif
+
/*
* Freescale Book-E MMU support
*/
--
1.5.3.5.788.gea559
^ permalink raw reply related
* Re: Oops: of_platform_serial_probe
From: Clemens Koller @ 2007-11-20 10:52 UTC (permalink / raw)
To: Arnd Bergmann; +Cc: linuxppc-embedded
In-Reply-To: <200711191756.55165.arnd@arndb.de>
[-- Attachment #1: Type: text/plain, Size: 3872 bytes --]
Hi, Arnd!
Arnd Bergmann schrieb:
> On Monday 19 November 2007, Clemens Koller wrote:
>> Unable to handle kernel paging request for data at address 0x00000000
>> Faulting instruction address: 0xc018f03c
>> Oops: Kernel access of bad area, sig: 11 [#1]
>> MPC85xx ADS
>> Modules linked in:
>> NIP: c018f03c LR: c018f00c CTR: c00127b4
>> REGS: c0821cf0 TRAP: 0300 Not tainted (2.6.24-rc2-ge6a5c27f)
>> MSR: 00029000 <EE,ME> CR: 42022088 XER: 20000000
>> DEAR: 00000000, ESR: 00000000
>> TASK = c081e000[1] 'swapper' THREAD: c0820000
>> GPR00: b1000000 c0821da0 c081e000 c0833e10 00000004 c0821d80 c03d3064 c05eea80
>> GPR08: 00000200 00000002 0000002a 13ab6680 82022042 00000000 c03318a4 c033188c
>> GPR16: c0331908 c03318f0 c03a0e30 c0331930 c033191c 007fff00 0ffeccbc c03a0000
>> GPR24: c0821dc4 00000000 00000003 c0934cf8 cffffba8 00000000 c0833e00 c07fdc6c
>> NIP [c018f03c] of_platform_serial_probe+0x118/0x1e4
>> LR [c018f00c] of_platform_serial_probe+0xe8/0x1e4
>> Call Trace:
>
> Ok, that is a NULL pointer access, probably somewhere in the
> of_platform_serial_setup that can be inlined. Please post the
> device tree entries for your serial ports so we can see what
> goes wrong there.
The device tree is the default one which comes with the kernel:
paulus.git/arch/powerpc/boot/dts/mpc8540ads.dts
which contains:
serial@4500 {
device_type = "serial";
compatible = "ns16550";
reg = <4500 100>; // reg base, size
clock-frequency = <0>; // should we fill in in uboot?
interrupts = <2a 2>;
interrupt-parent = <&mpic>;
};
serial@4600 {
device_type = "serial";
compatible = "ns16550";
reg = <4600 100>; // reg base, size
clock-frequency = <0>; // should we fill in in uboot?
interrupts = <2a 2>;
interrupt-parent = <&mpic>;
};
> One potential problem that I can see is a missing 'current-speed'
> property in your tree, which would cause this behavior.
That's correct. Should be fixed in all .dts' ?
> It looks
> like many device trees set this, but it is not required by all
> bindings.
How should someone know, when it's really needed and when not?
> If that's the case, the patch below should fix your
> problem, but you probably want to set the current-speed anyway,
> according to your boot loader settings.
I think there was no need to set it again, because of: console=ttyS0,115200
But I'll verify...
> --- a/drivers/serial/of_serial.c
> +++ b/drivers/serial/of_serial.c
> @@ -56,7 +56,8 @@ static int __devinit of_platform_serial_setup(struct of_device *ofdev,
> port->flags = UPF_SHARE_IRQ | UPF_BOOT_AUTOCONF | UPF_IOREMAP
> | UPF_FIXED_PORT;
> port->dev = &ofdev->dev;
> - port->custom_divisor = *clk / (16 * (*spd));
> + if (spd)
> + port->custom_divisor = *clk / (16 * (*spd));
>
> return 0;
> }
>
Ack! However, I changed it similar to the available code.
No idea what's better here. At least it should tell the user:
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
serial8250.0: ttyS0 at MMIO 0xe0004500 (irq = 42) is a 16550A
console [ttyS0] enabled
serial8250.0: ttyS1 at MMIO 0xe0004600 (irq = 42) is a 16550A
of_serial e0004500.serial: no current-speed property set
of_serial e0004600.serial: no current-speed property set
Patch attached.
Regards,
--
Clemens Koller
__________________________________
R&D Imaging Devices
Anagramm GmbH
Rupert-Mayer-Straße 45/1
Linhof Werksgelände
D-81379 München
Tel.089-741518-50
Fax 089-741518-19
http://www.anagramm-technology.com
[-- Attachment #2: of_serial-check-current-speed.patch --]
[-- Type: text/plain, Size: 741 bytes --]
Warn user when current-speed property isn't set and exit.
Signed-off-by: Clemens Koller <clemens.koller@anagramm.de>
CC: Arnd Bergmann <arnd@arndb.de>
diff --git a/drivers/serial/of_serial.c b/drivers/serial/of_serial.c
index a64d858..e035cb2 100644
--- a/drivers/serial/of_serial.c
+++ b/drivers/serial/of_serial.c
@@ -36,6 +36,10 @@ static int __devinit of_platform_serial_setup(struct of_device *ofdev,
memset(port, 0, sizeof *port);
spd = of_get_property(np, "current-speed", NULL);
clk = of_get_property(np, "clock-frequency", NULL);
+ if (!spd) {
+ dev_warn(&ofdev->dev, "no current-speed property set\n");
+ return -ENODEV;
+ }
if (!clk) {
dev_warn(&ofdev->dev, "no clock-frequency property set\n");
return -ENODEV;
^ permalink raw reply related
* Re: 2.6 kernel hangs after loading device tree
From: Clemens Koller @ 2007-11-20 11:08 UTC (permalink / raw)
To: abhi_linux; +Cc: linuxppc-embedded
In-Reply-To: <13848328.post@talk.nabble.com>
> charanya venkatraman wrote:
>> Hi all
>> Sorry about the previous mail.Got sent by mistake.
>>
>> Iam using the 2.6.22.5 kernel on MPC 8560 and MPC8540 on my custom
>> board.Mykernel hangs after loading the device tree in both the
>> processors. There is
>> no output on the serial port after loading the device tree.
>> I have tried the following console arguments:
>> MPC8540: bootargs root=/dev/ram rw console=ttyS0,115200
>> MPC8560:bootargs root=/dev/ram rw console=ttyCPM0,115200
>>
>> Any help on this issue??
Maybe your problem is related to... See the thread at:
http://ozlabs.org/pipermail/linuxppc-embedded/2007-November/028968.html
(I use Paulus' git tree.)
Regards,
Clemens Koller
__________________________________
R&D Imaging Devices
Anagramm GmbH
Rupert-Mayer-Straße 45/1
Linhof Werksgelände
D-81379 München
Tel.089-741518-50
Fax 089-741518-19
http://www.anagramm-technology.com
^ permalink raw reply
* RE: [PATCH 0/5] fixups for mpc8360 rev. 2.1 erratum #2 (RGMII Timing)
From: Li Yang @ 2007-11-20 11:08 UTC (permalink / raw)
To: jgarzik, Phillips Kim, Kumar Gala, netdev, linuxppc-dev; +Cc: paulus
In-Reply-To: <20071105121530.5c38fbb7.kim.phillips@freescale.com>
> -----Original Message-----
> From: Phillips Kim=20
> Sent: Tuesday, November 06, 2007 2:16 AM
> To: Li Yang-r58472; Kumar Gala; netdev@vger.kernel.org;=20
> linuxppc-dev@ozlabs.org
> Cc: jgarzik@pobox.com; paulus@samba.org
> Subject: [PATCH 0/5] fixups for mpc8360 rev. 2.1 erratum #2=20
> (RGMII Timing)
>=20
> Hello all,
>=20
> the following patches fix RGMII timing for rev. 2.1 of the=20
> mpc8360, according to erratum #2 (erratum text included=20
> below). Basically the most intrusive part is the addition of=20
> two new RGMII Internal Delay modes; one for TX delay only,=20
> and the other for RX delay only (i.e, not both at the same time).
>=20
> Please review, and since this affects both netdev and powerpc=20
> trees, one maintainer should ack them for the other to push=20
> upstream (i.e, Kumar acks them, and Leo picks them up to go=20
> through netdev or the other way around; either way is fine=20
> with me). I'm hoping they're trivial enough to go in 2.6.24.
>=20
> Depending on how the review goes, a follow-on patch to u-boot=20
> will be sent out that fixes up the phy-connection-type in the=20
> device tree (from "rgmii-id" to "rgmii-rxid" iff on mpc8360rev2.1).
>=20
2-4
Acked-by: Li Yang <leoli@freescale.com>
^ permalink raw reply
* dtc: Don't use env(1) in testsuite
From: David Gibson @ 2007-11-20 11:14 UTC (permalink / raw)
To: Jon Loeliger; +Cc: linuxppc-dev
The run_tests.sh script currently invokes the testcase binaries via
env(1). This behaviour is inherited from the libhugetlbfs testsuite
which uses this approach to easily set various configuration
environment variables in testcases.
We don't use that for dtc, and are unlikely to ever want to.
Therefore this patch removes that technique, which substantially
speeds up the testsuite.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Index: dtc/tests/run_tests.sh
===================================================================
--- dtc.orig/tests/run_tests.sh 2007-11-20 22:06:12.000000000 +1100
+++ dtc/tests/run_tests.sh 2007-11-20 22:06:22.000000000 +1100
@@ -2,8 +2,6 @@
export QUIET_TEST=1
-ENV=/usr/bin/env
-
tot_tests=0
tot_pass=0
tot_fail=0
@@ -13,7 +11,7 @@
run_test () {
tot_tests=$[tot_tests + 1]
echo -n "$@: "
- if PATH=".:$PATH" $ENV "$@"; then
+ if "./$@"; then
tot_pass=$[tot_pass + 1]
else
ret="$?"
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
^ permalink raw reply
* RE: [PATCH] powerpc: mpc832x mds: Fix board PHY reset code
From: Li Yang @ 2007-11-20 11:30 UTC (permalink / raw)
To: Phillips Kim, Kumar Gala, linuxppc-dev; +Cc: Van Ackeren Peter
In-Reply-To: <20071119190443.7c04ae6b.kim.phillips@freescale.com>
> -----Original Message-----
> From: Phillips Kim=20
> Sent: Tuesday, November 20, 2007 9:05 AM
> To: Kumar Gala; linuxppc-dev@ozlabs.org
> Cc: Van Ackeren Peter; Li Yang
> Subject: [PATCH] powerpc: mpc832x mds: Fix board PHY reset code
>=20
> currently the board-level PHY reset code for the mpc832x MDS=20
> messes with reset configuration words source settings which=20
> is plain wrong (it looks like this board code was=20
> cut-n-pasted from the mpc8360 mds code, which has the PHY=20
> reset bits in a different BCSR); this patch points the PHY=20
> reset code to the proper mpc832x mds PHY reset bits in the BCSR.
>=20
> Signed-off-by: Peter Van Ackeren <peter.vanackeren@freescale.com>
> Signed-off-by: Kim Phillips <kim.phillips@freescale.com>
Acked-by: Li Yang <leoli@freescale.com>
> ---
> arch/powerpc/platforms/83xx/mpc832x_mds.c | 7 ++++---
> 1 files changed, 4 insertions(+), 3 deletions(-)
>=20
> diff --git a/arch/powerpc/platforms/83xx/mpc832x_mds.c=20
> b/arch/powerpc/platforms/83xx/mpc832x_mds.c
> index 972fa85..9e3bfcc 100644
> --- a/arch/powerpc/platforms/83xx/mpc832x_mds.c
> +++ b/arch/powerpc/platforms/83xx/mpc832x_mds.c
> @@ -90,10 +90,11 @@ static void __init mpc832x_sys_setup_arch(void)
> =20
> if ((np =3D of_find_compatible_node(NULL, "network", "ucc_geth"))
> !=3D NULL){
> - /* Reset the Ethernet PHY */
> - bcsr_regs[9] &=3D ~0x20;
> + /* Reset the Ethernet PHYs */
> +#define BCSR8_FETH_RST 0x50
> + bcsr_regs[8] &=3D ~BCSR8_FETH_RST;
> udelay(1000);
> - bcsr_regs[9] |=3D 0x20;
> + bcsr_regs[8] |=3D BCSR8_FETH_RST;
> iounmap(bcsr_regs);
> of_node_put(np);
> }
> --
> 1.5.2.2
>=20
>=20
^ permalink raw reply
* Re: Oops: of_platform_serial_probe
From: Arnd Bergmann @ 2007-11-20 12:05 UTC (permalink / raw)
To: linuxppc-embedded
In-Reply-To: <4742BC57.7020305@anagramm.de>
On Tuesday 20 November 2007, Clemens Koller wrote:
> The device tree is the default one which comes with the kernel:
> paulus.git/arch/powerpc/boot/dts/mpc8540ads.dts
> which contains:
>=20
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0serial@4500 {
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0device_type =3D "seria=
l";
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0compatible =3D "ns1655=
0";
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0reg =3D <4500 100>; =
=A0 =A0 =A0 // reg base, size
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0clock-frequency =3D <0=
>; =A0// should we fill in in uboot?
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0interrupts =3D <2a 2>;
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0interrupt-parent =3D <=
&mpic>;
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0};
>=20
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0serial@4600 {
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0device_type =3D "seria=
l";
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0compatible =3D "ns1655=
0";
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0reg =3D <4600 100>; =
=A0 =A0 =A0 // reg base, size
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0clock-frequency =3D <0=
>; =A0// should we fill in in uboot?
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0interrupts =3D <2a 2>;
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0interrupt-parent =3D <=
&mpic>;
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0};
>=20
> =A0> One potential problem that I can see is a missing 'current-speed'
> =A0> property in your tree, which would cause this behavior.
>=20
> That's correct. Should be fixed in all .dts' ?
=20
It depends a lot on how the systems are used. current-speed only makes
sense if there is a boot loader that also does some serial I/O at a
speed it sets up itself.
> =A0> It looks
> =A0> like many device trees set this, but it is not required by all
> =A0> bindings.
>=20
> How should someone know, when it's really needed and when not?
The point of current-speed is that the kernel can tell what bitrate
was used by the boot loader and set up the same speed so that your
terminal emulation does not get garbled output when changing from
boot loader messages to kernel messages.
> =A0> If that's the case, the patch below should fix your
> =A0> problem, but you probably want to set the current-speed anyway,
> =A0> according to your boot loader settings.
>=20
> I think there was no need to set it again, because of: console=3DttyS0,11=
5200
> But I'll verify...
When current-speed is set, you don't need to override the speed at the
command line.
> @@ -36,6 +36,10 @@ static int __devinit of_platform_serial_setup(struct o=
f_device *ofdev,
> =A0=A0=A0=A0=A0=A0=A0=A0memset(port, 0, sizeof *port);
> =A0=A0=A0=A0=A0=A0=A0=A0spd =3D of_get_property(np, "current-speed", NULL=
);
> =A0=A0=A0=A0=A0=A0=A0=A0clk =3D of_get_property(np, "clock-frequency", NU=
LL);
> +=A0=A0=A0=A0=A0=A0=A0if (!spd) {
> +=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0dev_warn(&ofdev->dev, "no c=
urrent-speed property set\n");
> +=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0return -ENODEV;
> +=A0=A0=A0=A0=A0=A0=A0}
> =A0=A0=A0=A0=A0=A0=A0=A0if (!clk) {
> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0dev_warn(&ofdev->dev, "no=
clock-frequency property set\n");
> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0return -ENODEV;
This looks wrong. Since the current-speed property is not mandated by open =
firmware,
we should not error out here, but simply use the setting from the command l=
ine
or whatever other defaults can be used. Not setting port->custom_divisor at=
all
should do the job.
Arnd <><
^ permalink raw reply
* Re: Problem with uboot on lite5200
From: Clemens Koller @ 2007-11-20 12:18 UTC (permalink / raw)
To: Wolfgang Denk; +Cc: Leo Hendrawan, linuxppc-embedded
In-Reply-To: <20071119211347.575522479C@gemini.denx.de>
Hello, Wolfgang!
Wolfgang Denk schrieb:
> In message <47403C73.9040506@anagramm.de> you wrote:
>> How should people get a glue what's current, when in the section
>> "Latest News" at http://sourceforge.net/projects/u-boot/ the people
>> still find a more or less official looking "u-boot-1.1.5" release.
>
> Maybe by reading the very first two lines on the SF page:
>
> ...
> NOTE: current source code is available from DENX git
> repository and FTP server; see http://www.denx.de/en/Software/GIT
I tried to convince you to point them to the releases... and _not_
to any repository.
> The problem is that you cannot really "shut down" a SourceForge
> project (please correct me if I'm wrong).
I don't like SourceForge for some reasons... now, if that's true,
I got one more. But anyway, there should be a way to update the
"Latest News"... in a way it points to current stuff.
>>> Current U-Boot is 1.3.0-rc4. Please wake up.
>> Well... maybe it's better to remove all references to the old
>> releases at sourceforge and point them to ftp://ftp.denx.de/pub/u-boot/
>
> Can you please teach me how to do that?
I would expect that one of the project admins (i.e. you) is able
to update the site information.
You could update the SF project as you did since u-boot-0.2.0.
If you don't want to continue with SF, propably an update to
a "last SF version" with nothing more than an README should
suffice.
Well, I know you expect people to read...
I'm just wondering why so many people use ancient versions. (-:
> And 1.3.0 will be out in less than 2 hours from now :-)
Well... that's great... thank you all!
Regards,
--
Clemens Koller
__________________________________
R&D Imaging Devices
Anagramm GmbH
Rupert-Mayer-Straße 45/1
Linhof Werksgelände
D-81379 München
Tel.089-741518-50
Fax 089-741518-19
http://www.anagramm-technology.com
^ permalink raw reply
* NULL dereference in clockevents_program_event
From: Johannes Berg @ 2007-11-19 20:06 UTC (permalink / raw)
To: Thomas Gleixner
Cc: linuxppc-dev list, Ingo Molnar, Paul Mackerras, Linux Kernel list
[-- Attachment #1: Type: text/plain, Size: 750 bytes --]
Hi,
During a hibernate cycle on my G5, while machine was powering down after
saving the image, I just had a NULL dereference in
clockevents_program_event when accessing dev->mode, dev was NULL.
Unfortunately the machine rebooted before I was able to write down more
than the fact that it was called from tick_program_event(); the problem
doesn't seem to be easily reproducible.
From what I can see when doing the same thing, the shutdown attempts to
offline all CPUs. Because the snapshot was actually saved to disk and
the machine was shutting down I guess that the it happened at that time,
but I have no idea what else to do to debug this.
I have
| CONFIG_HIGH_RES_TIMERS=y
| CONFIG_NO_HZ=y
in this config.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
^ permalink raw reply
* Re: Oops: of_platform_serial_probe
From: Clemens Koller @ 2007-11-20 12:49 UTC (permalink / raw)
To: Arnd Bergmann; +Cc: linuxppc-embedded
In-Reply-To: <200711201305.47753.arnd@arndb.de>
>> @@ -36,6 +36,10 @@ static int __devinit of_platform_serial_setup(struct of_device *ofdev,
>> memset(port, 0, sizeof *port);
>> spd = of_get_property(np, "current-speed", NULL);
>> clk = of_get_property(np, "clock-frequency", NULL);
>> + if (!spd) {
>> + dev_warn(&ofdev->dev, "no current-speed property set\n");
>> + return -ENODEV;
>> + }
>> if (!clk) {
>> dev_warn(&ofdev->dev, "no clock-frequency property set\n");
>> return -ENODEV;
>
> This looks wrong. Since the current-speed property is not mandated by open firmware,
> we should not error out here, but simply use the setting from the command line
> or whatever other defaults can be used. Not setting port->custom_divisor at all
> should do the job.
Understood... but then, my console just stops / gets reinitialized to some unknown
baudrate when I get to of_serial.c. :-(
Regards,
Clemens Koller
__________________________________
R&D Imaging Devices
Anagramm GmbH
Rupert-Mayer-Straße 45/1
Linhof Werksgelände
D-81379 München
Tel.089-741518-50
Fax 089-741518-19
http://www.anagramm-technology.com
^ permalink raw reply
* Re: libfdt: Abolish fdt_offset_ptr_typed()
From: Jon Loeliger @ 2007-11-20 15:06 UTC (permalink / raw)
To: David Gibson; +Cc: linuxppc-dev
In-Reply-To: <20071119062622.GL20794@localhost.localdomain>
So, like, the other day David Gibson mumbled:
> The fdt_offset_ptr_typed() macro seemed like a good idea at the time.
> However, it's not actually used all that often, it can silently throw
> away const qualifications and it uses a gcc extension (typeof) which
> I'd prefer to avoid for portability.
>
> Therefore, this patch gets rid of it (and the fdt_offset_ptr_typed_w()
> variant which was never used at all). It also makes a few variables
> const in testcases, which always should have been const, but weren't
> caught before because of the aforementioned silent discards.
>
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Applied.
jdl
^ permalink raw reply
* Re: libfdt: Abolish _typed() variants, add _cell() variants
From: Jon Loeliger @ 2007-11-20 15:06 UTC (permalink / raw)
To: David Gibson; +Cc: linuxppc-dev
In-Reply-To: <20071120023546.GA4356@localhost.localdomain>
So, like, the other day David Gibson mumbled:
> In a number of places through libfdt and its tests, we have *_typed()
> macro variants on functions which use gcc's typeof and statement
> expression extensions to allow passing literals where the underlying
> function takes a buffer and size.
>
> These seemed like a good idea at the time, but in fact they have some
> problems. They use typeof and statement expressions, extensions I'd
> prefer to avoid for portability. Plus, they have potential gotchas -
> although they'll deal with the size of the thing passed, they won't
> deal with other representation issues (like endianness) and results
> could be very strange if the type of the expression passed isn't what
> you think it is.
>
> In fact, the only users of these _typed() macros were when the value
> passed is a single cell (32-bit integer). Therefore, this patch
> removes all these _typed() macros and replaces them with explicit
> _cell() variants which handle a single 32-bit integer, and which also
> perform endian convesions as appropriate.
>
> With this in place, it now becomes easy to use standardized big-endian
> representation for integer valued properties in the testcases,
> regardless of the platform we're running on. We therefore do that,
> which has the additional advantage that all the example trees created
> during a test run are now byte-for-byte identical regardless of
> platform.
>
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Applied.
jdl
^ permalink raw reply
* Re: dtc: Add testcases for tree checks
From: Jon Loeliger @ 2007-11-20 15:09 UTC (permalink / raw)
To: David Gibson; +Cc: linuxppc-dev
In-Reply-To: <20071120052423.GC4356@localhost.localdomain>
So, like, the other day David Gibson mumbled:
> This patch adds a group of testcases to check that dtc correctly
> rejects trees with various structural errors.
>
> To make things easier to test, we change dtc so that failing checks
> (as opposed to other errors) result in exit code 2.
>
> This patch also fixes an embarrasing bug uncovered by these new tests:
> check_phandles() worked out if the tree's phandles were valid, then
> throws that information away and returns success always.
>
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
>
> NOTE! jdl, you'll need to chmod +x tests/dtc-checkfails.sh before you
> git commit this - it's a new shell script and patch can't encode the
> permissions info.
>
> Index: dtc/tests/dup-nodename.dts
> ===================================================================
> --- /dev/null 1970-01-01 00:00:00.000000000 +0000
> +++ dtc/tests/dup-nodename.dts 2007-11-20 16:02:22.000000000 +1100
Actually, this is the official third time now that it would have
been significantly nicer had you been using git for patches as
it does correctly handle excute permissions properly in patches.
And, it allows for side-band commentary such as your NOTE!, above,
to be included in the patch mail, but not in the patch log itself
such that it too doesn't have to be "git commit --amend"'ed out
as well.
In any event, Applied and Adjusted.
jdl
^ permalink raw reply
* Re: dtc: Don't use env(1) in testsuite
From: Jon Loeliger @ 2007-11-20 15:09 UTC (permalink / raw)
To: David Gibson; +Cc: linuxppc-dev
In-Reply-To: <20071120111412.GA13156@localhost.localdomain>
So, like, the other day David Gibson mumbled:
> The run_tests.sh script currently invokes the testcase binaries via
> env(1). This behaviour is inherited from the libhugetlbfs testsuite
> which uses this approach to easily set various configuration
> environment variables in testcases.
>
> We don't use that for dtc, and are unlikely to ever want to.
> Therefore this patch removes that technique, which substantially
> speeds up the testsuite.
>
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Applied.
jdl
^ permalink raw reply
* ML403 USB driver
From: Lorenz Kolb @ 2007-11-20 15:21 UTC (permalink / raw)
To: linuxppc-embedded
Hi,
we just tried the USB driver (from Peter Korsgaard) from Grant's virtex
tree.
Nevertheless we could not get the peripheral ports work as gadgets.
Has anyone tried (and probably fixed) that before?
Anyway, only one of the two peripheral ports seems to be active.
We use kernel 2.6.22 (as some usb related stuff has recently changed and the
driver would have to be changed), usb host works (usb-storage, cdc_ether,
some more stuff we tested)
Regards,
Lorenz Kolb
--
View this message in context: http://www.nabble.com/ML403-USB-driver-tf4844098.html#a13858912
Sent from the linuxppc-embedded mailing list archive at Nabble.com.
^ permalink raw reply
* Re: [PATCH 0/5] fixups for mpc8360 rev. 2.1 erratum #2 (RGMII Timing)
From: Kumar Gala @ 2007-11-20 15:27 UTC (permalink / raw)
To: Jeff Garzik; +Cc: netdev, paulus, Li Yang, linuxppc-dev
In-Reply-To: <4742389E.5080700@pobox.com>
On Nov 19, 2007, at 7:30 PM, Jeff Garzik wrote:
> Kim Phillips wrote:
>> On Mon, 5 Nov 2007 12:15:30 -0600
>> Kim Phillips <kim.phillips@freescale.com> wrote:
>>> Hello all,
>>>
>>> the following patches fix RGMII timing for rev. 2.1 of the mpc8360,
>>> according to erratum #2 (erratum text included below). Basically
>>> the
>>> most intrusive part is the addition of two new RGMII Internal Delay
>>> modes; one for TX delay only, and the other for RX delay only
>>> (i.e, not
>>> both at the same time).
>>>
>>> Please review, and since this affects both netdev and powerpc trees,
>>> one maintainer should ack them for the other to push upstream (i.e,
>>> Kumar acks them, and Leo picks them up to go through netdev or the
>>> other way around; either way is fine with me). I'm hoping they're
>>> trivial enough to go in 2.6.24.
>>>
>> Kumar, Leo, re-ping due to (a) it's been 2 weeks and (b) Anton
>> Vorontsov has since
>> issued his Tested-by.
>> Might I suggest Kumar ack the powerpc patches, and Leo/Jeff apply 5/5
>> to go through netdev?
>
> FWIW I just got back from vacation... I'm grabbing what DaveM has
> collected into davem/netdev-2.6.git, and then going from there...
Jeff,
I've pulled and pushed the arch/powepc bits of these fixes. I leave
the PHYY and driver bits to you.
- k
^ permalink raw reply
* Re: ML403 USB driver
From: Grant Likely @ 2007-11-20 15:31 UTC (permalink / raw)
To: Lorenz Kolb; +Cc: linuxppc-embedded
In-Reply-To: <13858912.post@talk.nabble.com>
On 11/20/07, Lorenz Kolb <linuxppcemb@lkmail.de> wrote:
>
> Hi,
>
> we just tried the USB driver (from Peter Korsgaard) from Grant's virtex
> tree.
>
> Nevertheless we could not get the peripheral ports work as gadgets.
> Has anyone tried (and probably fixed) that before?
That driver does not work for gadget ports.
>
> Anyway, only one of the two peripheral ports seems to be active.
Yes, I've got that problem here too. I haven't yet solved it. Any
help would be appreciated.
> We use kernel 2.6.22 (as some usb related stuff has recently changed and the
> driver would have to be changed), usb host works (usb-storage, cdc_ether,
> some more stuff we tested)
Cheers,
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195
^ permalink raw reply
* Re: Please pull from 'for-2.6.24' branch
From: Kim Phillips @ 2007-11-20 15:52 UTC (permalink / raw)
To: Kumar Gala; +Cc: linuxppc-dev, Paul Mackerras
In-Reply-To: <Pine.LNX.4.64.0711192355460.1265@blarg.am.freescale.net>
On Mon, 19 Nov 2007 23:56:23 -0600 (CST)
Kumar Gala <galak@kernel.crashing.org> wrote:
> Kim Phillips (4):
> [POWERPC] 83xx: mpc832x mds: Fix board PHY reset code
> [POWERPC] 83xx: Fix 2nd UCC entry in mpc832x_mds.dts
> [POWERPC] Document rgmii-rxid and rgmii-txid phy-connection-types
> [POWERPC] 83xx: Handle mpc8360 rev. 2.1 RGMII timing erratum
>
Hi Kumar,
thanks for applying these, here's one you missed:
http://patchwork.ozlabs.org/linuxppc/patch?id=14651
Kim
^ permalink raw reply
* [PATCH try2] powerpc: Add support for PORTA and PORTB odr registers
From: Jochen Friedrich @ 2007-11-20 17:17 UTC (permalink / raw)
To: linuxppc-embedded; +Cc: paulus, linux-kernel
PORTA and PORTB have odr registers, as well. However, the PORTB odr
register is only 16bit.
Signed-off-by: Jochen Friedrich <jochen@scram.de>
---
arch/powerpc/sysdev/commproc.c | 19 ++++++++++++++++---
1 files changed, 16 insertions(+), 3 deletions(-)
diff --git a/arch/powerpc/sysdev/commproc.c b/arch/powerpc/sysdev/commproc.c
index d5a0dcf..c0d00c2 100644
--- a/arch/powerpc/sysdev/commproc.c
+++ b/arch/powerpc/sysdev/commproc.c
@@ -411,7 +411,7 @@ EXPORT_SYMBOL(cpm_dpram_phys);
#endif /* !CONFIG_PPC_CPM_NEW_BINDING */
struct cpm_ioport16 {
- __be16 dir, par, sor, dat, intr;
+ __be16 dir, par, odr_sor, dat, intr;
__be16 res[3];
};
@@ -441,6 +441,13 @@ static void cpm1_set_pin32(int port, int pin, int flags)
else
clrbits32(&iop->par, pin);
+ if (port == CPM_PORTB) {
+ if (flags & CPM_PIN_OPENDRAIN)
+ setbits16(&mpc8xx_immr->im_cpm.cp_pbodr, pin);
+ else
+ clrbits16(&mpc8xx_immr->im_cpm.cp_pbodr, pin);
+ }
+
if (port == CPM_PORTE) {
if (flags & CPM_PIN_SECONDARY)
setbits32(&iop->sor, pin);
@@ -474,11 +481,17 @@ static void cpm1_set_pin16(int port, int pin, int flags)
else
clrbits16(&iop->par, pin);
+ if (port == CPM_PORTA) {
+ if (flags & CPM_PIN_OPENDRAIN)
+ setbits16(&iop->odr_sor, pin);
+ else
+ clrbits16(&iop->odr_sor, pin);
+ }
if (port == CPM_PORTC) {
if (flags & CPM_PIN_SECONDARY)
- setbits16(&iop->sor, pin);
+ setbits16(&iop->odr_sor, pin);
else
- clrbits16(&iop->sor, pin);
+ clrbits16(&iop->odr_sor, pin);
}
}
--
1.5.3.4
^ permalink raw reply related
* [PATCH] powerpc: Change _tlbie arguments to reflect new API
From: Jochen Friedrich @ 2007-11-20 17:21 UTC (permalink / raw)
To: linuxppc-embedded; +Cc: paulus, linux-kernel
A new pid argument has been added to _tlbie for 4xx platforms.
Add this argument to the 8xx path in mem.c, as well. As 8xx
does not need th epid information, this argument can always be 0.
Signed-off-by: Jochen Friedrich <jochen@scram.de>
CC arch/powerpc/mm/mem.o
arch/powerpc/mm/mem.c: In function 'update_mmu_cache':
arch/powerpc/mm/mem.c:467: error: too few arguments to function '_tlbie'
make[1]: *** [arch/powerpc/mm/mem.o] Error 1
make: *** [arch/powerpc/mm] Error 2
---
arch/powerpc/mm/mem.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/powerpc/mm/mem.c b/arch/powerpc/mm/mem.c
index 81eb96e..e07852e 100644
--- a/arch/powerpc/mm/mem.c
+++ b/arch/powerpc/mm/mem.c
@@ -464,7 +464,7 @@ void update_mmu_cache(struct vm_area_struct *vma, unsigned long address,
* we invalidate the TLB here, thus avoiding dcbst
* misbehaviour.
*/
- _tlbie(address);
+ _tlbie(address, 0);
#endif
if (!PageReserved(page)
&& !test_bit(PG_arch_1, &page->flags)) {
--
1.5.3.4
^ permalink raw reply related
* Re: [PATCH] powerpc: Change _tlbie arguments to reflect new API
From: Josh Boyer @ 2007-11-20 18:14 UTC (permalink / raw)
To: Jochen Friedrich; +Cc: paulus, linux-kernel, linuxppc-embedded
In-Reply-To: <47431799.6010802@scram.de>
On Tue, 20 Nov 2007 18:21:29 +0100
Jochen Friedrich <jochen@scram.de> wrote:
> A new pid argument has been added to _tlbie for 4xx platforms.
> Add this argument to the 8xx path in mem.c, as well. As 8xx
> does not need th epid information, this argument can always be 0.
This is already fixed in Paul's tree.
josh
^ permalink raw reply
* Re: 2.6 kernel hangs after loading device tree
From: charanya venkatraman @ 2007-11-20 18:59 UTC (permalink / raw)
To: linuxppc-embedded
Hi,
I got a solution to this.The problem was with the current speed
parameter in the DTS,as stated.You need to explicity specify the
speed.It doesnot get filled in from U-boot.You can also probabaly
check the kernel log buf to see what values are set for these
parameters.Anyways,changing the current speed made it work me and my
2.6 kernel is now up.
Thanks.
Charanya.
> Date: Mon, 19 Nov 2007 16:08:03 -0800 (PST)
> From: abhi_linux <seema.pm@gmail.com>
> Subject: Re: 2.6 kernel hangs after loading device tree
> To: linuxppc-embedded@ozlabs.org
> Message-ID: <13848328.post@talk.nabble.com>
> Content-Type: text/plain; charset=us-ascii
>
>
> Hello
> Did u get a solution to this? I have similar issues. How do u enable
> debugging in UBoot?
> Thanks
>
> charanya venkatraman wrote:
> >
> > Hi all
> > Sorry about the previous mail.Got sent by mistake.
> >
> > Iam using the 2.6.22.5 kernel on MPC 8560 and MPC8540 on my custom
> > board.Mykernel hangs after loading the device tree in both the
> > processors .There is
> > no output on the serial port after loading the device tree.Am using U-boot
> > 1.2.0 as the bootloader.After enabling debug in u-boot i could see that
> > the
> > control is getting transferred to the kernel after which it hangs.Earlier
> > i
> > tried using 2.6.21 which also hangs at the same point.The config files
> > used
> > were MPC8540ADS_defconfig and MPC8560ADS_defconfig under powerpc
> > directory.
> > The changes that were made to the device tree are:
> > 1.The reg and ranges properties of the soc node have been changed to
> > account
> > for the change in CCSRBAR of my board.
> > 2.Removed the PCI,mdio nodes and ethernet nodes since i dont need support
> > for these as of now.
> >
> > I have tried the following console arguments:
> > MPC8540: bootargs root=/dev/ram rw console=ttyS0,115200
> > MPC8560:bootargs root=/dev/ram rw console=ttyCPM0,115200
> >
> > Any help on this issue??
> >
> > Thanks.
> > Charanya.
^ permalink raw reply
* Re: [PATCH] [POWERPC] Emulate isel (Integer Select) instruction
From: Scott Wood @ 2007-11-20 17:54 UTC (permalink / raw)
To: Kumar Gala; +Cc: linuxppc-dev
In-Reply-To: <Pine.LNX.4.64.0711192135460.24923@blarg.am.freescale.net>
On Mon, Nov 19, 2007 at 09:36:57PM -0600, Kumar Gala wrote:
> isel (Integer Select) is a new user space instruction in the
> PowerISA 2.04 spec. Not all processors implement it so lets emulate
> to ensure code built with isel will run everywhere.
Given that the instruction is meant to be a performance enhancement,
we should probably warn the first few times it's emulated, so the user
knows they should change their toolchain setup if possible.
-Scott
^ permalink raw reply
* Xilinx EDK BSP generation of device trees for microblaze and PowerPC
From: Stephen Neuendorffer @ 2007-11-20 19:44 UTC (permalink / raw)
To: microblaze-uclinux, linuxppc-dev, Grant Likely, Michal Simek
=09
I've updated some code from Michel Simek to generate Flat Device Trees
from Xilinx EDK projects. This code is now hosted at:
git://git.xilinx.com/gen-mhs-devtree.git
This has one major advantage over the gen-mhs-devtree.py approach:
default IP core parameters that are not specified in the mhs file can
now be generated, since EDK pulls these in from the core .mpd file.
I've also managed to incorporate a few more improvements from the
previous review, so the BSP generator should include at least as much
information as gen-mhs-devtree.py
The next major order of business is to represent the DMA engines in the
MPMC and locallink connections to the lltemac.
Steve
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox