* Re: GCC4 fun.
From: Joerg Dorchain @ 2005-03-03 12:44 UTC (permalink / raw)
To: linuxppc-dev
[-- Attachment #1: Type: text/plain, Size: 2109 bytes --]
Hi list,
I just booted a self-compiled 2.6.11 on my iBook G4.
The dmesg shows a hickup, where I am wondering what's the cause.
Total memory = 768MB; using 2048kB for hash table (at c0400000)
Linux version 2.6.11 (root@whisker) (gcc version 3.3.5 (Debian 1:3.3.5-8)) #29 Wed Mar 2 20:15:15 CET 2005
Found UniNorth memory controller & host bridge, revision: 210
Mapped at 0xfdf00000
Found a Intrepid mac-io controller, rev: 0, mapped at 0xfde80000
Processor NAP mode on idle enabled.
PowerMac motherboard: iBook G4
Found UniNorth PCI host bridge at 0xf0000000. Firmware bus number: 0->0
Found UniNorth PCI host bridge at 0xf2000000. Firmware bus number: 0->0
Found UniNorth PCI host bridge at 0xf4000000. Firmware bus number: 0->0
via-pmu: Server Mode is disabled
PMU driver 2 initialized for Core99, firmware: 0c
On node 0 totalpages: 196608
DMA zone: 196608 pages, LIFO batch:16
Normal zone: 0 pages, LIFO batch:1
HighMem zone: 0 pages, LIFO batch:1
Built 1 zonelists
Kernel command line: root=/dev/hda5 ro
PowerMac using OpenPIC irq controller at 0x80040000
OpenPIC Version 1.2 (4 CPUs and 64 IRQ sources) at fc633000
OpenPIC timer frequency is 4.166666 MHz
PID hash table entries: 4096 (order: 12, 65536 bytes)
time_init: decrementer frequency = 18.432000 MHz
Console: colour dummy device 80x25
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 773632k available (1928k kernel code, 1044k data, 144k init, 0k highmem)
AGP special page: 0xeffff000
Calibrating delay loop... 663.55 BogoMIPS (lpj=331776)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
scheduling while atomic: swapper/0x00000002/0
Call trace:
[c0007620] dump_stack+0x18/0x28
[c01de704] schedule+0x678/0x67c
[c0004500] syscall_exit_work+0x108/0x10c
[c02a97b4] proc_root_init+0x168/0x174
[ff847288] 0xff847288
[c02945e8] start_kernel+0x144/0x170
[00003a30] 0x3a30
Anyone an idea where this comes from? (Or, what else is needed for a
qualified statement about it?)
TIA,
Joerg
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply
* Re: PowerPC4xx Watchdog
From: Takeharu KATO @ 2005-03-03 12:13 UTC (permalink / raw)
To: Takeharu KATO; +Cc: ppcembed
In-Reply-To: <4226FA13.6020203@jp.fujitsu.com>
Matt and Kurmar:
Sorry to typo:
> Because the incidence of the problem is very low,
> it is important to the generation part such a problem when generated.
>
I was going to have written the following things, to make sure though
it is likely already to have understood:
Because the incidence of the problem is very low,
WDT is important to find the generation part such a problem when generated.
--
Takeharu KATO
Fujitsu Limited
Email:kato.takeharu at jp.fujitsu.com
^ permalink raw reply
* Re: [PATCH 3/3] PowerPC4xx/E500 WatchDogTimerDriver(exception handler part)
From: Takeharu KATO @ 2005-03-03 12:07 UTC (permalink / raw)
To: Takeharu KATO; +Cc: ppcembed
In-Reply-To: <42231C26.7020508@jp.fujitsu.com>
Dear all:
I fix PowerPC405 exception handling part.
This patch corrects the problem of having not stopped WDT
when the WDT exception is generated.
This patch also stop WDT when the system fall in panic.
Signed-off-by: Takeharu KATO <kato.takeharu@jp.fujitsu.com>
--- linux-2.6.11-rc5-ppc4xx/arch/ppc/kernel/head_44x.S 2005-02-27 15:27:46.000000000 +0900
+++ linux-2.6.11-rc5/arch/ppc/kernel/head_44x.S 2005-03-03 18:09:03.000000000 +0900
@@ -444,8 +444,11 @@ interrupt_base:
EXCEPTION(0x1010, FixedIntervalTimer, UnknownException, EXC_XFER_EE)
/* Watchdog Timer Interrupt */
- /* TODO: Add watchdog support */
+#if defined(CONFIG_PPC4xx_WATCHDOG)
+ CRITICAL_EXCEPTION(0x1020, WatchdogTimer, ppc4xx_wdt_exception)
+#else
CRITICAL_EXCEPTION(0x1020, WatchdogTimer, UnknownException)
+#endif
/* Data TLB Error Interrupt */
START_EXCEPTION(DataTLBError)
diff -uprN linux-2.6.11-rc5-ppc4xx/arch/ppc/kernel/head_4xx.S
linux-2.6.11-rc5/arch/ppc/kernel/head_4xx.S
--- linux-2.6.11-rc5-ppc4xx/arch/ppc/kernel/head_4xx.S 2005-03-03 18:30:12.000000000 +0900
+++ linux-2.6.11-rc5/arch/ppc/kernel/head_4xx.S 2005-03-03 18:09:04.000000000 +0900
@@ -477,17 +477,21 @@ label:
#if 0
/* NOTE:
- * FIT and WDT handlers are not implemented yet.
+ * FIT handler is not implemented yet.
*/
/* 0x1010 - Fixed Interval Timer (FIT) Exception
*/
STND_EXCEPTION(0x1010, FITException, UnknownException)
+#endif
+
/* 0x1020 - Watchdog Timer (WDT) Exception
*/
-
- CRITICAL_EXCEPTION(0x1020, WDTException, UnknownException)
+#if defined(CONFIG_PPC4xx_WATCHDOG)
+ CRITICAL_EXCEPTION(0x1020, WDTException, ppc4xx_wdt_exception)
+#else
+ CRITICAL_EXCEPTION(0x1020, WDTException, UnknownException)
#endif
/* 0x1100 - Data TLB Miss Exception
diff -uprN linux-2.6.11-rc5-ppc4xx/arch/ppc/kernel/head_e500.S
linux-2.6.11-rc5/arch/ppc/kernel/head_e500.S
--- linux-2.6.11-rc5-ppc4xx/arch/ppc/kernel/head_e500.S 2005-02-27 15:29:39.000000000 +0900
+++ linux-2.6.11-rc5/arch/ppc/kernel/head_e500.S 2005-03-03 18:09:04.000000000 +0900
@@ -494,8 +494,12 @@ interrupt_base:
EXCEPTION(0x3100, FixedIntervalTimer, UnknownException, EXC_XFER_EE)
/* Watchdog Timer Interrupt */
- /* TODO: Add watchdog support */
+#if defined(CONFIG_PPC4xx_WATCHDOG)
+ CRITICAL_EXCEPTION(0x3200, WatchdogTimer, ppc4xx_wdt_exception)
+#else
CRITICAL_EXCEPTION(0x3200, WatchdogTimer, UnknownException)
+#endif
+
/* Data TLB Error Interrupt */
START_EXCEPTION(DataTLBError)
diff -uprN linux-2.6.11-rc5-ppc4xx/drivers/char/watchdog/ppc4xx_wdt.c
linux-2.6.11-rc5/drivers/char/watchdog/ppc4xx_wdt.c
--- linux-2.6.11-rc5-ppc4xx/drivers/char/watchdog/ppc4xx_wdt.c 2005-03-03 18:28:33.000000000 +0900
+++ linux-2.6.11-rc5/drivers/char/watchdog/ppc4xx_wdt.c 2005-03-03 20:29:16.946286104 +0900
@@ -66,12 +66,18 @@ static struct watchdog_info ident = {
.firmware_version = 0, /* This is filled with PVR in initialization. */
.identity = "PPC4xx WDT",
};
-
+/*
+ * PowerPC Linux common exception handler
+ */
+extern void _exception(int signr, struct pt_regs *regs, int code, unsigned long addr);
+/* Panic notifier */
+extern struct notifier_block *panic_notifier_list;
/*
* External linkage functions
*/
void ppc4xx_wdt_heartbeat(void);
void ppc4xx_wdt_setup_options(char *cmd_line);
+void ppc4xx_wdt_exception(struct pt_regs *regs);
/*
* Internal linkage functions
*/
@@ -243,7 +249,7 @@ ppc4xx_wdt_heartbeat(void)
if (!wdt_enable)
goto out;
-
+
if (wdt_heartbeat_count > 0)
wdt_heartbeat_count--;
else
@@ -255,6 +261,20 @@ ppc4xx_wdt_heartbeat(void)
/* Reset count */
ppc_md.heartbeat_count = 0;
}
+/**
+ * ppc4xx_wdt_exception:
+ * WatchDog Exception
+ */
+void
+ppc4xx_wdt_exception(struct pt_regs *regs)
+{
+ wdt_enable=0;
+
+ __ppc4xx_wdt_disable();
+ printk("WDT Exception at PC: %lx, MSR: %lx, vector=%lx %s\n",
+ regs->nip, regs->msr, regs->trap, print_tainted());
+ panic(ppc4xx_mkmsg("Initiating system reboot.\n"));
+}
\f
/*
* Driver Logic functions
@@ -526,10 +546,9 @@ static int
ppc4xx_wdt_notify_sys(struct notifier_block *this, unsigned long code,
void *unused)
{
- if(code==SYS_DOWN || code==SYS_HALT) {
- /* Turn the card off */
+ if (code != SYS_POWER_OFF) /* Turn the card off */
ppc4xx_wdt_stop();
- }
+
return NOTIFY_DONE;
}
@@ -572,6 +591,7 @@ ppc4xx_wdt_exit(void)
{
misc_deregister(&ppc4xx_wdt_miscdev);
unregister_reboot_notifier(&ppc4xx_wdt_notifier);
+ notifier_chain_unregister(&panic_notifier_list,&ppc4xx_wdt_notifier);
}
/**
@@ -592,6 +612,14 @@ ppc4xx_wdt_init(void)
return ret;
}
+ /* Register panic notifier */
+ ret = notifier_chain_register(&panic_notifier_list,&ppc4xx_wdt_notifier);
+ if(ret) {
+ ppc4xx_wdt_err("Cannot register panic notifier (err=%d)\n", ret);
+ unregister_reboot_notifier(&ppc4xx_wdt_notifier);
+ return ret;
+ }
+
ret = 0;
ppc4xx_wdt_init_device();
/* Check that the heartbeat value is within it's range ; if not reset to the default */
--
Takeharu KATO
Fujitsu Limited
Email:kato.takeharu at jp.fujitsu.com
^ permalink raw reply
* Re: PowerPC4xx Watchdog
From: Takeharu KATO @ 2005-03-03 11:50 UTC (permalink / raw)
To: Matt Porter; +Cc: ppcembed
In-Reply-To: <20050302161530.D31614@cox.net>
Matt and Kurmar,
Thank you for your response.
>>>What do you see as the advantage to having a watchdog driver
>>> that uses the booke hardware watchdog facility over a generic
>>> timebase driven driver?
>>
I do not think that there is especially an important
reason to use the hardware watchdog as your saying
though it noticed by thinking later.
Therefore, I agrees the shortest way of implementing
the driver is fixing minor things of a old ppc405 driver.
However, I posted the new driver for the following reasons.
1) The old driver depends on HZ value (10ms).
2) The old driver doesn't support e500.
3) When the last mail was sent, it had finished
writing the driver to certain extent.
So, we are
> That's the only thing I can think of. I guess my question then
> is whether people think this is important enough in practice
> to have the hardware watchdog as an alternative. My guess is yes,
> but I don't have a strong opinion.
>
I also thought like that before.
Certainly, this case doesn't become a big problem
while it is developing on the evaluation boards.
However, a lot of users think that they install
Linux on the custom board, and ships the product.
When the problem of causing hanging up with the interruption disabled
occurs on the custom board, pursuing the cause becomes very
difficult.
In the case that we experienced, it kept operating with the device
driver became an interruption prohibition, and hanging up was caused
very unusually occasionally.
To solve this problem, we are consuming time of about half a year.
Because the incidence of the problem is very low,
it is important to the generation part such a problem when generated.
In this case, WDT driver may be good help.
Regards,
--
Takeharu KATO
Fujitsu Limited
Email:kato.takeharu at jp.fujitsu.com
^ permalink raw reply
* Adding machine types to the kernel tree...
From: Jakob Viketoft @ 2005-03-03 11:46 UTC (permalink / raw)
To: Linux PPC Embedded list
Hi!
Are there any certain policys or religious issues about adding machine
types to the (ppc40x) kernel tree, and who's responsible for kicking
stuff like this up the main tree?
Specifically, I would like to replace the PowerPC405 support for the
Xilinx ML 300 (development board) with generic Xilinx Virtex-II Pro and
Virtex4 support (FPGAs). In my opinion, the end target isn't the
development boards, but the custom configuration it all will run on in
the end, and so things would benefit from a more general support. Do
anyone have any insightful views/opinions on this or comments of any kind?
Clearly, there seem to be some demand for this lately according to
traffic on the list...
Cheers!
/Jakob
^ permalink raw reply
* uclibc with gcc-2.95
From: Wojciech Kromer @ 2005-03-03 10:21 UTC (permalink / raw)
To: Embedded PPC Linux Mailing List
-anyone have compiled powerpc cross-gcc-2.95 with uclibc ?
^ permalink raw reply
* port linux to xc2vp4
From: T T @ 2005-03-03 10:19 UTC (permalink / raw)
To: Linuxppc-embedded
[-- Attachment #1: Type: text/plain, Size: 793 bytes --]
Hi all,
Can any show me step by step to port linux kernel to the custom board. this board has xc2vp4 (xilinx fpga) that contains a powerpc 405, and I have used EDK software from Xilinx to add spi controller, uartlite, and sdram controller, no ethernet on this board. Do I need to build the toolchain for powerpc; if it need the toolchains, then where to get it. Beside I don't know how to configure the linux kernel (for example I download linux-2.4.18.tar.gz) then do "make menuconfigure" some of selection like "MTD" I don't know if I need to select it as a yet or not because on my custom board I have serial flash from ST M32P80.
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
[-- Attachment #2: Type: text/html, Size: 861 bytes --]
^ permalink raw reply
* BCM5421 PHY on TSEC on MPC8560
From: Jaka Močnik @ 2005-03-03 9:31 UTC (permalink / raw)
To: Embedded PPC Linux Mailing List
hello!
I am currently attempting to boot linux (kernel 2.6.11) on an
MPC8560-based board: I have successfully fixed U-Boot to work and am now
attempting to get the kernel up - I have managed to get as far as I can
without mounting the root fs, adding a few fixes on the way. I attempt
to mount root fs via NFS and this is where I've been stuck for a few
days (I used 2.6.10 before, I just ported my board-specific changes over
to 2.6.11, hence the "few days").
I have a BroadCom BCM5421 PHY attached to MPC8560 TSEC. I have added
support for its aux status register and its initialization (via another
phy_info entry) to gianfar_phy.c and configured the kernel with Gianfar
driver without NAPI support. It seems that the link is established OK
(at least the switch that the board is connected to suggests so) and the
gfar_transmit() gets called, signalling that the buffers are being sent.
however, no packets seem to be thrown on the wire (nothing ever gets to
the other side).
Ethernet works perfectly in U-Boot. I have also compared the code and it
seems - apart from the architectural differences between U-Boot and
Linux kernel - that U-Boot does roughly the same thing as the kernel
does.
If anyone has any idea or hint whatsoever about what I could look into,
I'd appreciate it very much. Thanks!
regards,
jaKa
--
w3: http://fish.homeunix.org/people/jaka
email: jaka@activetools.si
^ permalink raw reply
* Re: [PATCH 3/3] PowerPC4xx/E500 WatchDogTimerDriver(exception handler part)
From: Kumar Gala @ 2005-03-03 7:14 UTC (permalink / raw)
To: Takeharu KATO; +Cc: ppcembed
In-Reply-To: <42231C26.7020508@jp.fujitsu.com>
I've sent the part of this that was a bug fix to head_booke.h up stream=20=
to andrew.
- kumar
On Feb 28, 2005, at 7:27 AM, Takeharu KATO wrote:
> Dear Matt and all:
>
> This is PowerPC405 exception handling part.
> This patch consist of two parts.
>
> I create this just in case, if you think that this is not needed,
> please ignore them.
>
> 1) WatchDogException vector routine for ppc4xx.
> =A0=A0=A0 It cause Oops with MachineCheckException as other PPC4xx =
do.
> 2) Trivial bug fix in head_booke.h
> =A0=A0=A0 Trivial bug fix of CRITICAL_EXCEPTION macro.
>
> Signed-off-by: Takeharu KATO <kato.takeharu@jp.fujitsu.com>
>
>
>
> diff -uprN linux-2.6.11-rc5.orig/arch/ppc/kernel/head_4xx.S
> linux-2.6.11-rc5-ppc4xx/arch/ppc/kernel/head_4xx.S
> --- linux-2.6.11-rc5.orig/arch/ppc/kernel/head_4xx.S=A0=A0=A0 =
2005-02-27=20
> 15:30:39.000000000 +0900
> +++ linux-2.6.11-rc5-ppc4xx/arch/ppc/kernel/head_4xx.S=A0 2005-02-28=20=
> 21:47:42.531317912 +0900
> @@ -484,11 +484,11 @@ label:
> =A0 */
> =A0 =A0=A0=A0=A0=A0 STND_EXCEPTION(0x1010,=A0 FITException,=A0=A0 =
=A0=A0=A0=A0=A0=A0=A0=20
> UnknownException)
>
> +#endif
> =A0 /* 0x1020 - Watchdog Timer (WDT) Exception
> =A0 */
>
> =A0 =A0=A0=A0=A0=A0 CRITICAL_EXCEPTION(0x1020, WDTException, =
UnknownException)
> -#endif
>
> =A0 /* 0x1100 - Data TLB Miss Exception
> =A0=A0 * As the name implies, translation is not in the MMU, so =
search the
> diff -uprN linux-2.6.11-rc5.orig/arch/ppc/kernel/head_booke.h
> linux-2.6.11-rc5-ppc4xx/arch/ppc/kernel/head_booke.h
> --- linux-2.6.11-rc5.orig/arch/ppc/kernel/head_booke.h=A0 2005-02-27=20=
> 15:27:12.000000000 +0900
> +++ linux-2.6.11-rc5-ppc4xx/arch/ppc/kernel/head_booke.h=A0=A0=A0=A0=A0=
=A0=A0=20
> 2005-02-28 21:50:05.060650160 +0900
> @@ -194,8 +194,8 @@ label:
> =A0 =A0=A0=A0=A0=A0 CRITICAL_EXCEPTION_PROLOG;=A0=A0=A0=A0=A0 =A0=A0=A0=
=A0=A0=A0=A0 =A0=A0=A0=A0=A0=A0=A0 =A0=A0=A0=A0=A0=A0=A0 \
> =A0 =A0=A0=A0=A0=A0 addi=A0=A0=A0 r3,r1,STACK_FRAME_OVERHEAD;=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0 =A0=A0=A0=A0=A0=A0=A0 \
> =A0 =A0=A0=A0=A0=A0 EXC_XFER_TEMPLATE(hdlr, n+2, (MSR_KERNEL &=20
> ~(MSR_ME|MSR_DE|MSR_CE)), \
> -=A0=A0=A0=A0=A0=A0 =A0=A0=A0=A0=A0=A0=A0 =A0=A0=A0=A0=A0=A0=A0 =A0 =
NOCOPY, transfer_to_handler_full, \
> -=A0=A0=A0=A0=A0=A0 =A0=A0=A0=A0=A0=A0=A0 =A0=A0=A0=A0=A0=A0=A0 =A0 =
ret_from_except_full)
> +=A0=A0=A0=A0=A0=A0 =A0=A0=A0=A0=A0=A0=A0 =A0=A0=A0=A0=A0=A0=A0 =A0 =
NOCOPY, crit_transfer_to_handler, \
> +=A0=A0=A0=A0=A0=A0 =A0=A0=A0=A0=A0=A0=A0 =A0=A0=A0=A0=A0=A0=A0 =A0 =
ret_from_crit_exc)
>
> =A0 #define MCHECK_EXCEPTION(n, label, hdlr)=A0=A0=A0=A0=A0 =A0=A0=A0=A0=
=A0=A0=A0 =A0=A0=A0=A0=A0=A0=A0 \
> =A0 =A0=A0=A0=A0=A0 START_EXCEPTION(label); =A0=A0=A0=A0=A0=A0=A0 =
=A0=A0=A0=A0=A0=A0=A0 =A0=A0=A0=A0=A0=A0=A0 =A0=A0=A0=A0=A0=A0=A0 \
>
>
>
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
^ permalink raw reply
* linux on xc2vp4
From: T T @ 2005-03-03 8:56 UTC (permalink / raw)
To: Linuxppc-embedded
[-- Attachment #1: Type: text/plain, Size: 419 bytes --]
Hi all,
I would like to port linux kernel to a custom board that contains xc2vp4 (xilinx fpga) which it include powerpc 405 hard core, uartlite, spi controller, sdram controller. I don't how to start because I am new to linux os. Any help is welcome.
Thanks.
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
[-- Attachment #2: Type: text/html, Size: 504 bytes --]
^ permalink raw reply
* [PATCH] Include support for physmap driver in mpc8xx setup...
From: David Jander @ 2005-03-03 8:38 UTC (permalink / raw)
To: linuxppc-embedded
Hi,
I'd like to hear comments about this.
I am working with a fairly recent denx kernel tree (linuxppc_2_4_devel) and=
=20
have noticed that apparently support for physmap MTD mapping driver is=20
missing. Since physmap.c version 1.29 on, flash start address, size and=20
buswidth have to be setup by the board support package, but mpc8xx uses a=20
centralized .c file (arch/ppc/m8xx_setup.c) and include-files from=20
arch/platforms/*, so there is no way of specifying flash geometry.
I suggest something like this to solve the problem. If there is a better pl=
ace=20
to put this, please let me know.
=2D------------------------ begin patch --------------------------
=2D--=A0arch/ppc/kernel/m8xx_setup.c.orig
+++=A0arch/ppc/kernel/m8xx_setup.c
@@=A0-35,6=A0+35,9=A0@@
=A0#include=A0<linux/ioport.h>
=A0#include=A0<linux/bootmem.h>
=A0#include=A0<linux/seq_file.h>
+#if=A0defined(CONFIG_MTD_PHYSMAP)=A0&&=A0defined(CONFIG_MTD)=20
+#include=A0<linux/mtd/physmap.h>=20
+#endif=20
=A0
=A0#include=A0<asm/mmu.h>
=A0#include=A0<asm/processor.h>
@@=A0-510,4=A0+513,8=A0@@
=A0#if=A0defined(CONFIG_IDE_8xx_PCCARD)=A0||=A0defined(CONFIG_IDE_8xx_DIREC=
T)
=A0=A0=A0=A0 m8xx_ide_init();
=A0#endif
+#if=A0defined(CONFIG_MTD_PHYSMAP)=A0&&=A0defined(CONFIG_MTD)=20
+ /*=A0we=A0use=A0generic=A0physmap=A0mapping=A0driver=A0and=A0we=A0use=A0p=
artitions=A0*/
+ physmap_configure(CONFIG_MTD_PHYSMAP_START,=A0CONFIG_MTD_PHYSMAP_LEN,=A0
CONFIG_MTD_PHYSMAP_BUSWIDTH,=A0NULL);
+#endif=20
=A0}
=2D------------------------- end patch -------------------------------
Greetings,
=2D-=20
David Jander
Protonic Holland.
^ permalink raw reply
* Re: Building a Kernel for the AMCC PPC440EP Bamboo Board
From: Gerhard Jaeger @ 2005-03-03 8:23 UTC (permalink / raw)
To: Jörn Engel; +Cc: linuxppc-embedded
In-Reply-To: <20050302215308.GA6511@wohnheim.fh-wedel.de>
On Wednesday 02 March 2005 22:53, J=F6rn Engel wrote:
> On Tue, 1 March 2005 17:37:22 +0100, Gerhard Jaeger wrote:
> > On Tuesday 01 March 2005 17:14, Zeighami, Roy wrote:
> > >=20
> > > When I select 44x as the CPU type, I don't see "Bamboo" under machine
> > > type. =20
> >=20
> > This won't work, as Bamboo BSP stuff is currently not added.
>=20
> Correct.
>=20
> > > Any suggestions?
> >=20
> > try to use ebony_defconfig
>=20
> Doesn't work, neither does ocotea. Both are able to display "TUX!" on
> the dot-matrix display, but panic before writing any serial output.
>=20
> /me has one of these beauties as well and will try to hack up support
> for it. If anyone has patches or suggestions, help is always
> appreciated.
>=20
Could not confirm that so far! Ebony and Ocotea are working out of the
box, using these defconfig files! (pristine kernel 2.6.11)
Gerhard
=2D-=20
Gerhard Jaeger <gjaeger@sysgo.com> =20
SYSGO AG Embedded and Real-Time Software
www.sysgo.com | www.elinos.com | www.pikeos.com | www.osek.de=20
^ permalink raw reply
* Re: [PATCH 3/3] PowerPC4xx/E500 WatchDogTimerDriver(exception handler part)
From: Takeharu KATO @ 2005-03-03 7:31 UTC (permalink / raw)
To: Kumar Gala; +Cc: ppcembed
In-Reply-To: <fb51aa4f2ef8274e05a26ed098918ffc@freescale.com>
Hi
Kumar Gala wrote:
> I've sent the part of this that was a bug fix to head_booke.h up stream
> to andrew.
>
> - kumar
>
Thank you, I confirmed your mail to akpm.
--
Takeharu KATO
Fujitsu Limited
Email:kato.takeharu at jp.fujitsu.com
^ permalink raw reply
* [PATCH] ppc32: Trivial bug fix in CRITICAL_EXCEPTION macro
From: Kumar Gala @ 2005-03-03 4:34 UTC (permalink / raw)
To: akpm; +Cc: linuxppc-embedded
Andrew,
This patch fixes a trival bug in the CRITICAL_EXCEPTION macro
Signed-off-by: Takeharu KATO <kato.takeharu@jp.fujitsu.com>
Signed-off-by: Kumar Gala <kumar.gala@freescale.com>
---
diff -Nru a/arch/ppc/kernel/head_booke.h b/arch/ppc/kernel/head_booke.h
--- a/arch/ppc/kernel/head_booke.h 2005-03-02 22:20:28 -06:00
+++ b/arch/ppc/kernel/head_booke.h 2005-03-02 22:20:28 -06:00
@@ -194,8 +194,8 @@
CRITICAL_EXCEPTION_PROLOG; \
addi r3,r1,STACK_FRAME_OVERHEAD; \
EXC_XFER_TEMPLATE(hdlr, n+2, (MSR_KERNEL & ~(MSR_ME|MSR_DE|MSR_CE)), \
- NOCOPY, transfer_to_handler_full, \
- ret_from_except_full)
+ NOCOPY, crit_transfer_to_handler, \
+ ret_from_crit_exc)
#define MCHECK_EXCEPTION(n, label, hdlr) \
START_EXCEPTION(label); \
^ permalink raw reply
* [PATCH] ppc32: Add support to use the DS1553 RTC/NVRAM on MPC8555 CDS system
From: Kumar Gala @ 2005-03-03 4:31 UTC (permalink / raw)
To: akpm; +Cc: linuxppc-embedded
Andrew,
This patch makes the MPC8555 CDS system utilize the DS1553 RTC/NVRAM.
Signed-off-by: Kumar Gala <kumar.gala@freescale.com>
---
diff -Nru a/arch/ppc/platforms/85xx/mpc85xx_cds_common.c b/arch/ppc/platforms/85xx/mpc85xx_cds_common.c
--- a/arch/ppc/platforms/85xx/mpc85xx_cds_common.c 2005-03-02 22:11:56 -06:00
+++ b/arch/ppc/platforms/85xx/mpc85xx_cds_common.c 2005-03-02 22:11:56 -06:00
@@ -39,6 +39,7 @@
#include <asm/page.h>
#include <asm/atomic.h>
#include <asm/time.h>
+#include <asm/todc.h>
#include <asm/io.h>
#include <asm/machdep.h>
#include <asm/prom.h>
@@ -304,6 +305,8 @@
}
#endif /* CONFIG_PCI */
+TODC_ALLOC();
+
/* ************************************************************************
*
* Setup the architecture
@@ -329,6 +332,13 @@
cds_pci_slot = ((cadmus[CM_CSR] >> 6) & 0x3) + 1;
printk("CDS Version = %x in PCI slot %d\n", cadmus[CM_VER], cds_pci_slot);
+ /* Setup TODC access */
+ TODC_INIT(TODC_TYPE_DS1743,
+ 0,
+ 0,
+ ioremap(CDS_RTC_ADDR, CDS_RTC_SIZE),
+ 8);
+
/* Set loops_per_jiffy to a half-way reasonable value,
for use until calibrate_delay gets called. */
loops_per_jiffy = freq / HZ;
@@ -453,10 +463,14 @@
ppc_md.find_end_of_memory = mpc85xx_find_end_of_memory;
- ppc_md.time_init = NULL;
- ppc_md.set_rtc_time = NULL;
- ppc_md.get_rtc_time = NULL;
ppc_md.calibrate_decr = mpc85xx_calibrate_decr;
+
+ ppc_md.time_init = todc_time_init;
+ ppc_md.set_rtc_time = todc_set_rtc_time;
+ ppc_md.get_rtc_time = todc_get_rtc_time;
+
+ ppc_md.nvram_read_val = todc_direct_read_val;
+ ppc_md.nvram_write_val = todc_direct_write_val;
#if defined(CONFIG_SERIAL_8250) && defined(CONFIG_SERIAL_TEXT_DEBUG)
ppc_md.progress = gen550_progress;
diff -Nru a/arch/ppc/platforms/85xx/mpc85xx_cds_common.h b/arch/ppc/platforms/85xx/mpc85xx_cds_common.h
--- a/arch/ppc/platforms/85xx/mpc85xx_cds_common.h 2005-03-02 22:11:56 -06:00
+++ b/arch/ppc/platforms/85xx/mpc85xx_cds_common.h 2005-03-02 22:11:56 -06:00
@@ -33,6 +33,10 @@
#define CM_CSR (1)
#define CM_RST (2)
+/* CDS NVRAM/RTC */
+#define CDS_RTC_ADDR (0xf8000000)
+#define CDS_RTC_SIZE (8 * 1024)
+
/* PCI config */
#define PCI1_CFG_ADDR_OFFSET (0x8000)
#define PCI1_CFG_DATA_OFFSET (0x8004)
diff -Nru a/arch/ppc/syslib/Makefile b/arch/ppc/syslib/Makefile
--- a/arch/ppc/syslib/Makefile 2005-03-02 22:11:56 -06:00
+++ b/arch/ppc/syslib/Makefile 2005-03-02 22:11:56 -06:00
@@ -99,4 +99,5 @@
ifeq ($(CONFIG_85xx),y)
obj-$(CONFIG_PCI) += indirect_pci.o pci_auto.o
endif
+obj-$(CONFIG_MPC8555_CDS) += todc_time.o
obj-$(CONFIG_PPC_MPC52xx) += mpc52xx_setup.o mpc52xx_pic.o
^ permalink raw reply
* [PATCH] ppc32: Add support for the Dallas 1553 RTC/NVRAM
From: Kumar Gala @ 2005-03-03 4:26 UTC (permalink / raw)
To: akpm; +Cc: linuxppc-embedded
Andrew,
This patch adds support for the Dallas 1553 RTC/NVRAM.
Signed-off-by: Kumar Gala <kumar.gala@freescale.com>
---
diff -Nru a/arch/ppc/syslib/todc_time.c b/arch/ppc/syslib/todc_time.c
--- a/arch/ppc/syslib/todc_time.c 2005-03-02 22:05:08 -06:00
+++ b/arch/ppc/syslib/todc_time.c 2005-03-02 22:05:08 -06:00
@@ -287,6 +287,7 @@
limit = 1;
switch (todc_info->rtc_type) {
+ case TODC_TYPE_DS1553:
case TODC_TYPE_DS1557:
case TODC_TYPE_DS1743:
case TODC_TYPE_DS1746: /* XXXX BAD HACK -> FIX */
@@ -322,6 +323,7 @@
if (todc_info->rtc_type != TODC_TYPE_MC146818) {
switch (todc_info->rtc_type) {
+ case TODC_TYPE_DS1553:
case TODC_TYPE_DS1557:
case TODC_TYPE_DS1743:
case TODC_TYPE_DS1746: /* XXXX BAD HACK -> FIX */
@@ -418,6 +420,7 @@
unsigned char save_control = 0, val;
switch (todc_info->rtc_type) {
+ case TODC_TYPE_DS1553:
case TODC_TYPE_DS1557:
case TODC_TYPE_DS1746: /* XXXX BAD HACK -> FIX */
case TODC_TYPE_DS1747:
@@ -432,6 +435,7 @@
val = todc_read_val(addr);
switch (todc_info->rtc_type) {
+ case TODC_TYPE_DS1553:
case TODC_TYPE_DS1557:
case TODC_TYPE_DS1746: /* XXXX BAD HACK -> FIX */
case TODC_TYPE_DS1747:
diff -Nru a/include/asm-ppc/todc.h b/include/asm-ppc/todc.h
--- a/include/asm-ppc/todc.h 2005-03-02 22:05:08 -06:00
+++ b/include/asm-ppc/todc.h 2005-03-02 22:05:08 -06:00
@@ -98,6 +98,7 @@
#define TODC_TYPE_PC97307 10 /* PC97307 internal RTC */
#define TODC_TYPE_DS1557 11 /* Dallas DS1557 RTC */
#define TODC_TYPE_DS17285 12 /* Dallas DS17285 RTC */
+#define TODC_TYPE_DS1553 13 /* Dallas DS1553 RTC */
#define TODC_TYPE_MC146818 100 /* Leave room for m48txx's */
/*
@@ -207,6 +208,28 @@
#define TODC_TYPE_DS1501_FLAGS (TODC_TYPE_DS1501_NVRAM_SIZE + 0xff)
#define TODC_TYPE_DS1501_NVRAM_ADDR_REG 0x10
#define TODC_TYPE_DS1501_NVRAM_DATA_REG 0x13
+
+#define TODC_TYPE_DS1553_NVRAM_SIZE 0x1ff0
+#define TODC_TYPE_DS1553_SW_FLAGS 0
+#define TODC_TYPE_DS1553_YEAR 0x1fff
+#define TODC_TYPE_DS1553_MONTH 0x1ffe
+#define TODC_TYPE_DS1553_DOM 0x1ffd /* Day of Month */
+#define TODC_TYPE_DS1553_DOW 0x1ffc /* Day of Week */
+#define TODC_TYPE_DS1553_HOURS 0x1ffb
+#define TODC_TYPE_DS1553_MINUTES 0x1ffa
+#define TODC_TYPE_DS1553_SECONDS 0x1ff9
+#define TODC_TYPE_DS1553_CNTL_B 0x1ff9
+#define TODC_TYPE_DS1553_CNTL_A 0x1ff8 /* control_a R/W regs */
+#define TODC_TYPE_DS1553_WATCHDOG 0x1ff7
+#define TODC_TYPE_DS1553_INTERRUPTS 0x1ff6
+#define TODC_TYPE_DS1553_ALARM_DATE 0x1ff5
+#define TODC_TYPE_DS1553_ALARM_HOUR 0x1ff4
+#define TODC_TYPE_DS1553_ALARM_MINUTES 0x1ff3
+#define TODC_TYPE_DS1553_ALARM_SECONDS 0x1ff2
+#define TODC_TYPE_DS1553_CENTURY 0x1ff8
+#define TODC_TYPE_DS1553_FLAGS 0x1ff0
+#define TODC_TYPE_DS1553_NVRAM_ADDR_REG 0
+#define TODC_TYPE_DS1553_NVRAM_DATA_REG 0
#define TODC_TYPE_DS1557_NVRAM_SIZE 0x7fff0
#define TODC_TYPE_DS1557_SW_FLAGS 0
^ permalink raw reply
* Re: PowerPC4xx Watchdog
From: Matt Porter @ 2005-03-02 23:15 UTC (permalink / raw)
To: Kumar Gala; +Cc: ppcembed
In-Reply-To: <b83e8f546345414634e6c7518b441996@freescale.com>
On Wed, Mar 02, 2005 at 05:06:31PM -0600, Kumar Gala wrote:
> Matt,
>
> [snip]
>
> > What do you see as the advantage to having a watchdog driver
> > that uses the booke hardware watchdog facility over a generic
> > timebase driven driver?
>
> I would think the watchdog would be useful in cases that the normal
> decrementer exceptions gets disabled when MSR[EE] = 0.
That's the only thing I can think of. I guess my question then
is whether people think this is important enough in practice
to have the hardware watchdog as an alternative. My guess is yes,
but I don't have a strong opinion.
-Matt
^ permalink raw reply
* Re: PowerPC4xx Watchdog
From: Kumar Gala @ 2005-03-02 23:06 UTC (permalink / raw)
To: Matt Porter; +Cc: ppcembed
In-Reply-To: <20050302105201.C31614@cox.net>
Matt,
[snip]
> What do you see as the advantage to having a watchdog driver
> that uses the booke hardware watchdog facility over a generic
> timebase driven driver?
I would think the watchdog would be useful in cases that the normal
decrementer exceptions gets disabled when MSR[EE] = 0.
- kumar
^ permalink raw reply
* Re: Building a Kernel for the AMCC PPC440EP Bamboo Board
From: Jörn Engel @ 2005-03-02 21:53 UTC (permalink / raw)
To: Gerhard Jaeger; +Cc: linuxppc-embedded
In-Reply-To: <200503011737.22205.g.jaeger@sysgo.com>
On Tue, 1 March 2005 17:37:22 +0100, Gerhard Jaeger wrote:
> On Tuesday 01 March 2005 17:14, Zeighami, Roy wrote:
> >
> > When I select 44x as the CPU type, I don't see "Bamboo" under machine
> > type.
>
> This won't work, as Bamboo BSP stuff is currently not added.
Correct.
> > Any suggestions?
>
> try to use ebony_defconfig
Doesn't work, neither does ocotea. Both are able to display "TUX!" on
the dot-matrix display, but panic before writing any serial output.
/me has one of these beauties as well and will try to hack up support
for it. If anyone has patches or suggestions, help is always
appreciated.
Jörn
--
Simplicity is prerequisite for reliability.
-- Edsger W. Dijkstra
^ permalink raw reply
* Re: linuxppc tree with mv64xxx included?
From: Dale Farnsworth @ 2005-03-02 20:35 UTC (permalink / raw)
To: linuxppc-embedded
In-Reply-To: <42260A4F.8030205@katalix.com>
On Wed, Mar 02, 2005 at 06:47:43PM +0000, James Chapman wrote:
> The latest ethernet code can be obtained from
> bk://farnsworth.bkbits.net/linux-2.5-mv643xx-enet
Make that bk://dfarnsworth@bkbits.net/linux-2.5-mv643xx-enet
-Dale
^ permalink raw reply
* RE: linuxppc tree with mv64xxx included?
From: Ron Bianco @ 2005-03-02 19:03 UTC (permalink / raw)
To: James Chapman; +Cc: Linuxppc-Embedded
In-Reply-To: <42260A4F.8030205@katalix.com>
Thanks James and Mark,
I should have searched it rather than looking in 2.4 tree locations. :-P
We're going with 2.5 (2.6), but still getting familiar... many improvements
over 2.4.23.
Ron
> -----Original Message-----
> From: James Chapman [mailto:jchapman@katalix.com]
>
> Ron Bianco wrote:
>
> > I'm trying to locate the correct bitkeeper or other URL to get
> access to a
> > linux 2.5 or 2.6 tree that includes the support for the marvell mv64xxx
> > series chips.
> > I've examined the emails in this list regarding related patches
> for clues,
> > but am still confused.
> >
> > Tried bk://ppc.bkbits.net/linuxppc-2.5, but there is no marvell code.
>
> There is Marvell code in that tree. Look in drivers/net/mv64*,
> arch/ppc/syslib/mv*
>
> Some boards are already ported. See arch/ppc/platforms/*
>
> You'll also find the Marvell code in the "mainline" at
>
> bk://linux.bkbits.net/linux-2.6
>
> > We downloaded a 2.4.23 kernel tree directly from the marvell
> website, but it
> > is lacking some things like i2c for marvell, that have been
> discussed here.
> > Was further work, existing in some other tree, based on this?
>
> i2c and several other improvements are in queue. Check the archives for
> patches.
>
> The latest ethernet code can be obtained from
> bk://farnsworth.bkbits.net/linux-2.5-mv643xx-enet
>
> --
> James Chapman
> PGP key : http://www.katalix.com/~jchapman/pgpkey.txt
^ permalink raw reply
* Re: linuxppc tree with mv64xxx included?
From: James Chapman @ 2005-03-02 18:47 UTC (permalink / raw)
To: Ron Bianco; +Cc: Linuxppc-Embedded
In-Reply-To: <NCBBJPCHJLKAEAHINDCEGEJFFMAA.ronb@lcsaudio.com>
Ron Bianco wrote:
> I'm trying to locate the correct bitkeeper or other URL to get access to a
> linux 2.5 or 2.6 tree that includes the support for the marvell mv64xxx
> series chips.
> I've examined the emails in this list regarding related patches for clues,
> but am still confused.
>
> Tried bk://ppc.bkbits.net/linuxppc-2.5, but there is no marvell code.
There is Marvell code in that tree. Look in drivers/net/mv64*,
arch/ppc/syslib/mv*
Some boards are already ported. See arch/ppc/platforms/*
You'll also find the Marvell code in the "mainline" at
bk://linux.bkbits.net/linux-2.6
> We downloaded a 2.4.23 kernel tree directly from the marvell website, but it
> is lacking some things like i2c for marvell, that have been discussed here.
> Was further work, existing in some other tree, based on this?
i2c and several other improvements are in queue. Check the archives for
patches.
The latest ethernet code can be obtained from
bk://farnsworth.bkbits.net/linux-2.5-mv643xx-enet
--
James Chapman
PGP key : http://www.katalix.com/~jchapman/pgpkey.txt
^ permalink raw reply
* Re: PowerPC4xx Watchdog
From: Matt Porter @ 2005-03-02 17:52 UTC (permalink / raw)
To: Takeharu KATO; +Cc: ppcembed
In-Reply-To: <421D1375.5000904@ybb.ne.jp>
On Thu, Feb 24, 2005 at 08:36:21AM +0900, Takeharu KATO wrote:
> Hi
>
> >> Are you looking for the old "ppc405 watchdog" driver that simply
> >> hooked into the generic PPC heartbeat facility? Or are you looking
> >> for a driver that utilizes the 4xx/booke hardware watchdog facility?
> >>
> > I am looking for a driver that utilizes the 4xx/booke hardware watchdog
> > facility.
> >
> >
> FYI, I wrote a driver uses 4xx/booke hardware watchdog.
> BTW, is hooking PPC heartbeat facility obsoleted?
I see. The ppc_md.heartbeat facility isn't going anywhere as there
are multiple users. It's possible to take the "ppc405_wdt" driver
with a rename and minor cleanup have it be a generic timebase driven
watchdog driver that is compliant with the familiar WD interface.
What do you see as the advantage to having a watchdog driver
that uses the booke hardware watchdog facility over a generic
timebase driven driver?
-Matt
^ permalink raw reply
* Re: Looking for prebuilt PPC board with miniPCI slot
From: Conn Clark @ 2005-03-02 17:41 UTC (permalink / raw)
To: Andriy Korud; +Cc: linuxppc-embedded
In-Reply-To: <60E856FD577CC04BA3727AF4122D3F1611352E@3bit.vector.com.pl>
Andriy Korud wrote:
> Hi,
> we are looking for a embedded board with at least one miniPCI slot and Ethernet port with performance at AMCC 405EP@333 level and Linux 2.6 support.
> Have anybody heard about something like this preferably in Europe?
>
> Thanks in advance,
>
> --
>
> Andriy Korud
> software engineer,
>
> http://www.vector.com.pl
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
There is the Inrinsyc Cerf Cube 405EP
http://www.intrinsyc.com/products/mob_ref_sys/cerfcube_405_ep/ . It has
a MiniPCI slot and uses the 405EP . I don't know where it stands as far
as 2.6 kernel support. I'm pretty sure nobody is actively supporting it
with the current 2.4 kernel at this time though. You might have to call
them to find out where software development stands. They might be able
to make you some with a 333MHz part.
-- Conn Clark
*****************************************************************
Give a man a match and you heat him for a moment. Set him on fire
and you'll heat him for life.
*****************************************************************
Conn Clark
Engineering Stooge clark@esteem.com
Electronic Systems Technology Inc. www.esteem.com
Stock Ticker Symbol ELST
^ permalink raw reply
* Re: [PATCH] ppc4xx_sgdma.c
From: Matt Porter @ 2005-03-02 16:37 UTC (permalink / raw)
To: Roger Larsson; +Cc: linuxppc-embedded
In-Reply-To: <518B77BB6246D54D9E88FC49AFB0389D1E6C2C@seskoptronicmsx.optronic.local>
On Mon, Feb 28, 2005 at 02:22:46AM +0100, Roger Larsson wrote:
> * Dynamic list length
> 1. short lists will not waste a whole page
> 2. no limit in list length
> * End of Transfer termination
> * Residue corrected
>
> Working with hardware (some tests remaining)
You might want to copy/forward to Wolfgang since this patch is
against the Denx 2.4 tree in ELDK. Since it doesn't mention the
tree (most patches here are for linuxppc-2.4 or 2.6), he might
have missed this thread.
-Matt
^ 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