2.6.24 for mpc8458amc
Hi, I am trying to make a 2.6.24 vanilla kernel boot (an work fine in a second time) on a mpc8548amc board. I have add the platform specific stuff from the sources of the current kernel running on the cards. What I have basically add is: - a folder mpc8548amc, in the config/platform directory, which allow to select the mpc8548amc as the supported platform - add the following files: - arch/ppc/configs/mpc8548amc_defconfig - arch/ppc/configs/platforms/85xx/mpc_8548_amc.h and .c - I have used the dts of an another platform (mpc8548cds) which seems quite the same, but I haven't got any confirmation of that yet. When I am booting the kernel image I get: AMC= dhcp 0x100 uImage.amc.2.6.24 Speed: 1000, full duplex BOOTP broadcast 1 DHCP client bound to address 10.255.255.2 Using eTSEC0 device TFTP from server 0.0.0.0; our IP address is 10.255.255.2; sending through gateway 10.1.1.1 Filename 'uImage.amc.2.6.24'. Load address: 0x100 Loading: # # # # # ### done Bytes transferred = 1802102 (1b7f76 hex) AMC= bootm 0x100 ## Booting image at 0100 ... Image Name: Linux-2.6.24 Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size:1802038 Bytes = 1.7 MB Load Address: Entry Point: Verifying Checksum ... OK Uncompressing Kernel Image ... OK No further messages... Does someone has an idea ? thanks, Maxime -- Maxime Louvel 0044 7964 80 43 Allen road Whitemore reans WV60AW Wolverhampton United Kingdom ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
MPC8641D PCI-Express error
Hi, I'm working with the Freescale evaluation board MPC8641DHPCN and the VIRTEX5 evaluation board ML555 connected with the PCI-Express. When I try to read some register I have this problem: Machine check in kernel mode. Caused by (from SRR1=149030): Transfer error ack signal Oops: Machine check, sig: 7 [#1] PREEMPT SMP NR_CPUS=2 Modules linked in: virtex5 LTT NESTING LEVEL : 0 NIP: F108019C LR: F1080198 CTR: 0001 REGS: c044dd60 TRAP: 0200 Tainted: GF (2.6.18-mpc8641d_hpcn) MSR: 00149030 EE,ME,IR,DR CR: 22000222 XER: TASK = c20e9990[568] 'insmod' THREAD: c044c000 CPU: 0 GPR00: F1080198 C044DE10 C20E9990 002E 8000 8000 2EA3 GPR08: C20E9990 C04C0220 C044C000 22000222 1001956C GPR16: GPR24: 3000EAA0 7FD6FDC0 C045FCC0 F107E594 F10A C2036000 NIP [F108019C] virtex5_probe+0x130/0x1c4 [virtex5] LR [F1080198] virtex5_probe+0x12c/0x1c4 [virtex5] Call Trace: [C044DE10] [F1080198] virtex5_probe+0x12c/0x1c4 [virtex5] (unreliable) [C044DE30] [C01D2A58] pci_device_probe+0x84/0xbc [C044DE50] [C0213754] driver_probe_device+0x60/0x118 [C044DE70] [C0213890] __driver_attach+0x84/0x88 [C044DE90] [C02130F4] bus_for_each_dev+0x58/0x94 [C044DEC0] [C02135D4] driver_attach+0x24/0x34 [C044DED0] [C0212AC8] bus_add_driver+0x88/0x164 [C044DEF0] [C021397C] driver_register+0x70/0xb8 [C044DF00] [C01D284C] __pci_register_driver+0x64/0x98 [C044DF10] [F1080030] init_module+0x30/0x6c [virtex5] [C044DF20] [C004CBFC] sys_init_module+0xc8/0x25c [C044DF40] [C0011358] ret_from_syscall+0x0/0x38 --- Exception: c00 at 0xff6de0c LR = 0x1de4 Instruction dump: 40820060 3c60f108 3863cea0 48000311 807f0238 3c81 48000395 7c7d1b78 3c60f108 3863ced4 480002f5 809d 3c60f108 3863cf04 480002e5 3c60f108 Have you got any suggestions? Thanks. Marco ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Re: 2.6.24 for mpc8458amc
Hello Maxime, if your board is still running, although you can't see the messages that means you don't have any console. Try to set one (I think you can use a SCM of the CPM) in the kernel configuration (characters devices) or in the command line (console=). Anyway, if you want to be sure if the kernel is booting up, look up the buffer where the messages are saved before the console is enabled. Find the function __log_buffer in the System.map file and throu the bootloader, have a look at this address. Raúl Moreno maxime louvel [EMAIL PROTECTED] maxime louvel Enviado por: [EMAIL PROTECTED] 19/02/2008 12:59 Para: linuxppc-embedded@ozlabs.org cc: Asunto: 2.6.24 for mpc8458amc Hi, I am trying to make a 2.6.24 vanilla kernel boot (an work fine in a second time) on a mpc8548amc board. I have add the platform specific stuff from the sources of the current kernel running on the cards. What I have basically add is: - a folder mpc8548amc, in the config/platform directory, which allow to select the mpc8548amc as the supported platform - add the following files: - arch/ppc/configs/mpc8548amc_defconfig - arch/ppc/configs/platforms/85xx/mpc_8548_amc.h and .c - I have used the dts of an another platform (mpc8548cds) which seems quite the same, but I haven't got any confirmation of that yet. When I am booting the kernel image I get: AMC= dhcp 0x100 uImage.amc.2.6.24 Speed: 1000, full duplex BOOTP broadcast 1 DHCP client bound to address 10.255.255.2 Using eTSEC0 device TFTP from server 0.0.0.0; our IP address is 10.255.255.2; sending through gateway 10.1.1.1 Filename 'uImage.amc.2.6.24'. Load address: 0x100 Loading: ## ### # # # # ### done Bytes transferred = 1802102 (1b7f76 hex) AMC= bootm 0x100 ## Booting image at 0100 ... Image Name: Linux-2.6.24 Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size:1802038 Bytes = 1.7 MB Load Address: Entry Point: Verifying Checksum ... OK Uncompressing Kernel Image ... OK No further messages... Does someone has an idea ? thanks, Maxime -- Maxime Louvel 0044 7964 80 43 Allen road Whitemore reans WV60AW Wolverhampton United Kingdom ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Re: Ethernet breakdown on a Yosemite evaluation board
On Tue, 19 Feb 2008 14:00:19 +0100 Nicolas Genevrier [EMAIL PROTECTED] wrote: Hello all, I noticed an Ethernet blocking on a Yosemite evaluation board when we are using both Ethernet devices (eth0 and eth1). To reproduce the issue, I just telnet the board from a PC (PC1) through eth0 and then telnet another PC (PC2) from the first telnet session through eth1. Then I display a lot of characters on the last telnet session: $ for i in `seq 1 10`; do echo $i aaa..(x160)..aaa; done After a while, transmission is blocked and leads to an rxde interruption from the MAL. Yosemite evaluation kit runs Linux 2.16.13 but I reproduced the issue with our board running Linux-2.6.16 on a 440EP. In Linux 2.6.16, the new ibm_emac driver tries to recover the error but Ethernet remains very very slow even one day after the end of the transmission. I didn't notice any evolution related to this neither any discussion on the topic. Sorry if I missed them. I am working on the subject but an idea or related information would be helpful. There was a patch from Wolfgang Ocker recently that fixed some interrupt settings for 440EP in arch/ppc. You might want to look at that. I still need to evaluate if the arch/powerpc port needs fixing. http://patchwork.ozlabs.org/linuxppc/patch?person=1210id=16789 josh ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Re: 2.6.24 for mpc8458amc
maxime louvel wrote: Hi, I am trying to make a 2.6.24 vanilla kernel boot (an work fine in a second time) on a mpc8548amc board. I have add the platform specific stuff from the sources of the current kernel running on the cards. What I have basically add is: - a folder mpc8548amc, in the config/platform directory, which allow to select the mpc8548amc as the supported platform - add the following files: - arch/ppc/configs/mpc8548amc_defconfig - arch/ppc/configs/platforms/85xx/mpc_8548_amc.h and .c - I have used the dts of an another platform (mpc8548cds) which seems quite the same, but I haven't got any confirmation of that yet. Uh, let's clear up minor confusion here. Are you using ARCH=ppc or ARCH=powerpc? I'm surprised to see that there is mention of arch/ppc/... above. Are you sure this is an ARCH=ppc build? You won't need a DTS file at all then. But if you are using a DTS file, and I suspect you should, then this is ARCH=powerpc. When I am booting the kernel image I get: AMC= dhcp 0x100 uImage.amc.2.6.24 Speed: 1000, full duplex BOOTP broadcast 1 DHCP client bound to address 10.255.255.2 http://10.255.255.2/ Using eTSEC0 device TFTP from server 0.0.0.0 http://0.0.0.0/; our IP address is 10.255.255.2 http://10.255.255.2/; sending through gateway 10.1.1.1 http://10.1.1.1/ Filename 'uImage.amc.2.6.24'. Load address: 0x100 Loading: ## ### # # # # ### done Bytes transferred = 1802102 (1b7f76 hex) AMC= bootm 0x100 ## Booting image at 0100 ... Image Name: Linux-2.6.24 Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size:1802038 Bytes = 1.7 MB Load Address: Entry Point: Verifying Checksum ... OK Uncompressing Kernel Image ... OK No further messages... Does someone has an idea ? thanks, Maxime Did you download a DTB file and use it on the bootm command? Nope. This is really a FAQ failure mode. Are you sure you have the console set up properly? Any chance you can get to the __log_buf with a BDI-2000? Thanks, jdl ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Ethernet breakdown on a Yosemite evaluation board
Hello all, I noticed an Ethernet blocking on a Yosemite evaluation board when we are using both Ethernet devices (eth0 and eth1). To reproduce the issue, I just telnet the board from a PC (PC1) through eth0 and then telnet another PC (PC2) from the first telnet session through eth1. Then I display a lot of characters on the last telnet session: $ for i in `seq 1 10`; do echo $i aaa..(x160)..aaa; done After a while, transmission is blocked and leads to an rxde interruption from the MAL. Yosemite evaluation kit runs Linux 2.16.13 but I reproduced the issue with our board running Linux-2.6.16 on a 440EP. In Linux 2.6.16, the new ibm_emac driver tries to recover the error but Ethernet remains very very slow even one day after the end of the transmission. I didn't notice any evolution related to this neither any discussion on the topic. Sorry if I missed them. I am working on the subject but an idea or related information would be helpful. Thank you, Nicolas Genevrier ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Re: 2.6.24 for mpc8458amc
Thanks for your answer, I am going to check this ppc / powerpc things. I should use the architecture powerpc, don't I? I'm not really sure I have understand what do you want to do with a BDI-2000. I access the cards through a serial line directly. cheers, Maxime On Feb 19, 2008 2:24 PM, Jon Loeliger [EMAIL PROTECTED] wrote: maxime louvel wrote: Hi, I am trying to make a 2.6.24 vanilla kernel boot (an work fine in a second time) on a mpc8548amc board. I have add the platform specific stuff from the sources of the current kernel running on the cards. What I have basically add is: - a folder mpc8548amc, in the config/platform directory, which allow to select the mpc8548amc as the supported platform - add the following files: - arch/ppc/configs/mpc8548amc_defconfig - arch/ppc/configs/platforms/85xx/mpc_8548_amc.h and .c - I have used the dts of an another platform (mpc8548cds) which seems quite the same, but I haven't got any confirmation of that yet. Uh, let's clear up minor confusion here. Are you using ARCH=ppc or ARCH=powerpc? I'm surprised to see that there is mention of arch/ppc/... above. Are you sure this is an ARCH=ppc build? You won't need a DTS file at all then. But if you are using a DTS file, and I suspect you should, then this is ARCH=powerpc. When I am booting the kernel image I get: AMC= dhcp 0x100 uImage.amc.2.6.24 Speed: 1000, full duplex BOOTP broadcast 1 DHCP client bound to address 10.255.255.2 http://10.255.255.2/ Using eTSEC0 device TFTP from server 0.0.0.0 http://0.0.0.0/; our IP address is 10.255.255.2 http://10.255.255.2/; sending through gateway 10.1.1.1 http://10.1.1.1/ Filename 'uImage.amc.2.6.24'. Load address: 0x100 Loading: ## ### # # # # ### done Bytes transferred = 1802102 (1b7f76 hex) AMC= bootm 0x100 ## Booting image at 0100 ... Image Name: Linux-2.6.24 Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size:1802038 Bytes = 1.7 MB Load Address: Entry Point: Verifying Checksum ... OK Uncompressing Kernel Image ... OK No further messages... Does someone has an idea ? thanks, Maxime Did you download a DTB file and use it on the bootm command? Nope. This is really a FAQ failure mode. Are you sure you have the console set up properly? Any chance you can get to the __log_buf with a BDI-2000? Thanks, jdl -- Maxime Louvel 0044 7964 80 43 Allen road Whitemore reans WV60AW Wolverhampton United Kingdom ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
RE: Ethernet breakdown on a Yosemite evaluation board
Thanks a lot for the information, I apologize having not seen the posted patch. Everything seems to run well now. Nicolas -Message d'origine- De : Josh Boyer [mailto:[EMAIL PROTECTED] Envoyé : mardi 19 février 2008 15:17 À : Nicolas Genevrier Cc : linuxppc-embedded@ozlabs.org Objet : Re: Ethernet breakdown on a Yosemite evaluation board On Tue, 19 Feb 2008 14:00:19 +0100 Nicolas Genevrier [EMAIL PROTECTED] wrote: Hello all, I noticed an Ethernet blocking on a Yosemite evaluation board when we are using both Ethernet devices (eth0 and eth1). To reproduce the issue, I just telnet the board from a PC (PC1) through eth0 and then telnet another PC (PC2) from the first telnet session through eth1. Then I display a lot of characters on the last telnet session: $ for i in `seq 1 10`; do echo $i aaa..(x160)..aaa; done After a while, transmission is blocked and leads to an rxde interruption from the MAL. Yosemite evaluation kit runs Linux 2.16.13 but I reproduced the issue with our board running Linux-2.6.16 on a 440EP. In Linux 2.6.16, the new ibm_emac driver tries to recover the error but Ethernet remains very very slow even one day after the end of the transmission. I didn't notice any evolution related to this neither any discussion on the topic. Sorry if I missed them. I am working on the subject but an idea or related information would be helpful. There was a patch from Wolfgang Ocker recently that fixed some interrupt settings for 440EP in arch/ppc. You might want to look at that. I still need to evaluate if the arch/powerpc port needs fixing. http://patchwork.ozlabs.org/linuxppc/patch?person=1210id=16789 josh ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Re: 2.6.24 for mpc8458amc
maxime louvel wrote: Thanks for your answer, I am going to check this ppc / powerpc things. I should use the architecture powerpc, don't I? ARCH == ppc is scheduled for _removal_ from the entire Kernel source base is just about 4 months. Feel free to move the deck chairs around. :-) I'm not really sure I have understand what do you want to do with a BDI-2000. Perhaps, for starters, you read Building Embedded Linux Systems as found here: http://www.oreilly.com/catalog/belinuxsys/ I access the cards through a serial line directly. Of course. But when you get no information there, you might try a different interface. jdl ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Re: MPC8641D PCI-Express error
Jon Loeliger ha scritto: Marco Stornelli wrote: Hi, I'm working with the Freescale evaluation board MPC8641DHPCN and the VIRTEX5 evaluation board ML555 connected with the PCI-Express. When I try to read some register I have this problem: Machine check in kernel mode. Any chance you can tell us what rev anything is? SoC, Board, Kernel? Significant improvement went into the 2.6.24 kernel development effort for many FSL PCI/PCI-E parts. Thanks, jdl Board: MPC8641D HPCN SoC: MPC8641D rev. 2 Kernel: 2.6.18 Thanks. Marco ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Re: Ethernet breakdown on a Yosemite evaluation board
On Tue, 19 Feb 2008 16:04:35 +0100 Nicolas Genevrier [EMAIL PROTECTED] wrote: Thanks a lot for the information, I apologize having not seen the posted patch. Everything seems to run well now. No worries. It was a recent patch and not on this list even, so no need to apologize. Glad things are working for you. josh ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Re: 2.6.24 for mpc8458amc
Hi again, this time I have tried to compile the kernel, with an embedded compiler on the board. here is the result... BOOTAS arch/powerpc/boot/ps3-hvcall.o BOOTCC arch/powerpc/boot/ps3.o BOOTCC arch/powerpc/boot/treeboot-bamboo.o BOOTCC arch/powerpc/boot/cuboot-8xx.o BOOTCC arch/powerpc/boot/cuboot-pq2.o BOOTCC arch/powerpc/boot/cuboot-sequoia.o BOOTCC arch/powerpc/boot/treeboot-walnut.o Assembler messages: Error: Internal assembler error for instruction icbt Internal error, aborting at ../../gas/config/tc-ppc.c line 1300 in ppc_setup_opcodes Please report this bug. make[2]: *** [arch/powerpc/boot/treeboot-walnut.o] Error 2 make[1]: *** [uImage] Error 2 make: *** [sub-make] Error 2 any idea ? cheers, Maxime On Feb 19, 2008 2:57 PM, Jon Loeliger [EMAIL PROTECTED] wrote: maxime louvel wrote: Thanks for your answer, I am going to check this ppc / powerpc things. I should use the architecture powerpc, don't I? ARCH == ppc is scheduled for _removal_ from the entire Kernel source base is just about 4 months. Feel free to move the deck chairs around. :-) I'm not really sure I have understand what do you want to do with a BDI-2000. Perhaps, for starters, you read Building Embedded Linux Systems as found here: http://www.oreilly.com/catalog/belinuxsys/ I access the cards through a serial line directly. Of course. But when you get no information there, you might try a different interface. jdl -- Maxime Louvel 0044 7964 80 43 Allen road Whitemore reans WV60AW Wolverhampton United Kingdom ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
RTC woes
Hi: I'm new to the list. I have an e500-based embedded Linux system running a 2.6.22 kernel. I have a PCF8563T i2c based RTC chip attached to the PPC i2c bus. In my kernel config file I have selected CONFIG_RTC_INTF_DEV=y and CONFIG_RTC_DRV_PCF8563=y. I do a mknod for /dev/rtc as c 10 135 (standard Linux) and link /dev/rtc0 to it. When I boot, get the following message: drivers/rtc/hctosys.c: unable to open rtc device (rtc0) and, of course I cannot access /dev/rtc after booting. I can, however, talk to the rtc if I use /dev/i2c and a generic i2c read and write utility. When I look in /proc/devices, I see that rtc has taken major number 254 which puzzles me. RTC should not need a dynamic major number, right? I have perused the drivers in linux/drivers/rtc and don't find any of them calling register_chrdev() to get a dynamic major number. So here are my questions: 1) Shouldn't rtc automagically use major/minor 10/135? 2) How can I find where in the source it asks for a dynamic major number? 3) Does the PPC have some quirks regarding i2c operation that are at the root of this problem? BYW, I tried making the rtc device file as c 254 0 to match what's in /proc/devices and that gives me the same bejavior. Thanks in advance for any help you can offer. Marc ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Re: 2.6.24 for mpc8458amc
On Tue, 19 Feb 2008 11:53:02 -0600 Scott Wood [EMAIL PROTECTED] wrote: maxime louvel wrote: Hi again, this time I have tried to compile the kernel, with an embedded compiler on the board. here is the result... BOOTAS arch/powerpc/boot/ps3-hvcall.o BOOTCC arch/powerpc/boot/ps3.o BOOTCC arch/powerpc/boot/treeboot-bamboo.o BOOTCC arch/powerpc/boot/cuboot-8xx.o BOOTCC arch/powerpc/boot/cuboot-pq2.o BOOTCC arch/powerpc/boot/cuboot-sequoia.o BOOTCC arch/powerpc/boot/treeboot-walnut.o Assembler messages: Error: Internal assembler error for instruction icbt Internal error, aborting at ../../gas/config/tc-ppc.c line 1300 in ppc_setup_opcodes Please report this bug. make[2]: *** [arch/powerpc/boot/treeboot-walnut.o] Error 2 make[1]: *** [uImage] Error 2 make: *** [sub-make] Error 2 That's a bug in older toolchains, which is aggravated by a misguided policy that we build all wrapper platforms, always. Either use a newer toolchain, or remove treeboot-walnut from arch/powerpc/boot/Makefile. It would be good to know what versions of binutils and gcc are being used though. josh ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
BUG: scheduling while atomic
I'm using 2.6.24-rc8 on a PPC 440 and getting this error. I've also seen another form of it when doing Telnet. In this case, I'm doing a copy of a file on an NFS mount. Any help would be appreciated. Thanks, John Linn # cp ftptest2 ftptest2_copied BUG: scheduling while atomic: cp/355/0x0efe Call Trace: [cfc89ec0] [c000725c] show_stack+0x4c/0x174 (unreliable) [cfc89ef0] [c0016880] __schedule_bug+0x54/0x68 [cfc89f10] [c01df464] schedule+0x50/0x300 [cfc89f40] [c0002374] recheck+0x0/0x24 BUG: scheduling while atomic: cp/355/0x0efe Call Trace: [cfc89c50] [c000725c] show_stack+0x4c/0x174 (unreliable) [cfc89c80] [c0016880] __schedule_bug+0x54/0x68 [cfc89ca0] [c01df464] schedule+0x50/0x300 [cfc89cd0] [c01df744] io_schedule+0x30/0x54 [cfc89cf0] [c003d79c] sync_page+0x44/0x58 [cfc89d00] [c01dfaf0] __wait_on_bit_lock+0x68/0xc8 [cfc89d20] [c003da28] __lock_page+0x64/0x78 [cfc89d60] [c00402d0] do_generic_mapping_read+0x218/0x418 [cfc89db0] [c00405fc] generic_file_aio_read+0x12c/0x1a8 [cfc89e00] [c00cba0c] nfs_file_read+0xf0/0x104 [cfc89e30] [c005b3d4] do_sync_read+0xb8/0x10c [cfc89ef0] [c005b840] vfs_read+0xc0/0x154 [cfc89f10] [c005c3bc] sys_read+0x4c/0x8c [cfc89f40] [c0001960] ret_from_syscall+0x0/0x3c BUG: scheduling while atomic: cp/355/0x0efe Call Trace: ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Re: RTC woes
Marc LeFevre schrieb: I’m new to the list. Welcome! :-) I have an e500-based embedded Linux system running a 2.6.22 kernel. I have a PCF8563T i2c based RTC chip attached to the PPC i2c bus. In my kernel config file I have selected CONFIG_RTC_INTF_DEV=y and CONFIG_RTC_DRV_PCF8563=y. I do a mknod for /dev/rtc as c 10 135 (standard Linux) and link /dev/rtc0 to it. When I boot, get the following message: drivers/rtc/hctosys.c: unable to open rtc device (rtc0) 2.6.22.x and 2.6.23.x i2c rtc code was quite messy around PCF8563. 3) Does the PPC have some quirks regarding i2c operation that are at the root of this problem? The RTC subsystem was improved quite a bit lately. Try 2.6.24' powerpc architecture with a proper device tree instead. It works over here on mpc8540 / mpc8548 whereas the older ones were just a waste of time. Regards, Clemens ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Re: 2.6.24 for mpc8458amc
On Feb 19, 2008, at 6:19 AM, [EMAIL PROTECTED] wrote: Hello Maxime, if your board is still running, although you can't see the messages that means you don't have any console. Try to set one (I think you can use a SCM of the CPM) in the kernel configuration (characters devices) or in the command line (console=). If you really have a mpc8548 than there is no CPM. It has 16550 style UARTs on it. - k ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Sample driver
Does anyone have sample drivers in Linux for the EBC interface for PPC405Ex? I would be thankful if someone could put in a sample code here. -- View this message in context: http://www.nabble.com/Sample-driver-tp15582059p15582059.html Sent from the linuxppc-embedded mailing list archive at Nabble.com. ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
