Re: [OpenWrt-Devel] [PATCH v3] Add SPI over GPIO driver
On Friday 17 October 2008 05:14:26 Magnus Damm wrote: On Mon, Jul 21, 2008 at 4:46 AM, Michael Buesch [EMAIL PROTECTED] wrote: This adds a driver that lets you drive an SPI bus over generic GPIO pins. Signed-off-by: Michael Buesch [EMAIL PROTECTED] Very useful. Fits my shiny new GPIO implementation for SuperH like a glove. Michael, as you know, I have some SuperH board code that makes use of this driver. Are there any outstanding issues with this driver that I can help resolving? bool cs_activelow should probably be removed from struct spi_gpio_platform_data. I think cs always is activelow, so we can simply hardcode this in spi_gpio_chipselect() If you want to do this, please feel free to do so. I currently don't have the time for this. The rest of the driver is fine with me. -- Greetings Michael. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] cross ksymoops
Hi. I have patched the openwrt buildroot to build a cross-ksymoops. It seems I have an array of target and architectures I can choose from. ksymoops tells me they are: $ staging_dir/toolchain-mipsel_gcc4.1.2/bin/mipsel-linux-uclibc-ksymoops -a '?' ksymoops 2.4.11 on i686 2.6.27-6-generic. Options used ... Architectures supported by your libbfd mips mips:3000 mips:3900 mips:4000 mips:4010 mips:4100 mips:4111 mips:4120 mips:4300 mips:4400 mips:4600 mips:4650 mips:5000 mips:5400 mips:5500 mips:6000 mips:7000 mips:8000 mips:9000 mips:1 mips:12000 mips:16 mips:mips5 mips:isa32 mips:isa32r2 mips:isa64 mips:isa64r2 mips:sb1 Note that the above list comes from libbfd. I have to assume that your other binutils libraries (libiberty, libopcodes) and binutils programs (nm and objdump) are in sync with libbfd. and $ staging_dir/toolchain-mipsel_gcc4.1.2/bin/mipsel-linux-uclibc-ksymoops -t '?' ksymoops 2.4.11 on i686 2.6.27-6-generic. Options used ... Targets supported by your libbfd elf32-tradlittlemips elf32-tradbigmips ecoff-littlemips ecoff-bigmips elf32-ntradlittlemips elf64-tradlittlemips elf32-ntradbigmips elf64-tradbigmips elf64-little elf64-big elf32-little elf32-big srec symbolsrec tekhex binary ihex Note that the above list comes from libbfd. I have to assume that your other binutils libraries (libiberty, libopcodes) and binutils programs (nm and objdump) are in sync with libbfd. Which should I choose? When I don't choose any I get: $ PATH=$PATH:/usr/src/openwrt/staging_dir/toolchain-mipsel_gcc4.1.2/bin/ strace -o /tmp/ksymoops.strace -f mipsel-linux-uclibc-ksymoops -K -v ../openwrt-11527/build_dir/linux-brcm47xx/linux-2.6.25.7/vmlinux -m ../openwrt-11527/build_dir/linux-brcm47xx/linux-2.6.25.7/System.map /tmp/foo.txt ksymoops 2.4.11 on i686 2.6.27-6-generic. Options used -v ../openwrt-11527/build_dir/linux-brcm47xx/linux-2.6.25.7/vmlinux (specified) -K (specified) -l /proc/modules (default) -o /lib/modules/2.6.27-6-generic/ (default) -m ../openwrt-11527/build_dir/linux-brcm47xx/linux-2.6.25.7/System.map (specified) No modules in ksyms, skipping objects No ksyms, skipping lsmod Data bus error, epc == 8011635c, ra == 8015dfe4 Cpu 0 $ 0 : 1000d800 81c52454 8015ddd4 $ 4 : c3f8 81c52454 0001 $ 8 : 80257f40 8025 802a 802a $12 : 802a 80298588 802985a8 $16 : 81c52400 81c52454 03f8 0002 $20 : c02bd000 0007 c02e9090 0001 $24 : 80ea1b78 000186a0 $28 : 80ea 80ea1cb8 80ef4d80 8015dfe4 Hi: 003d08db Lo: c5476300 epc : 8011635c Not tainted Using defaults from ksymoops -t elf32-little -a unknown Cause : 0080001c c02e9090 800c7294 0003 0002 0007 0001 028c3263 0003 80ef4d80 81c52400 81c77400 0001 80ef4e1c 81f1a584 0001 80ea1e00 c0321d68 81c52454 c0321d84 81c7ac8c c02bd000 001a c02e9090 c02e8be0 c01d0140 8015bfac 81c52454 800c7a6c Call Trace:[c02fd094][800c7294][c01d0140][8015bfac][800c7a6c][8010457c][80138030][80137fd4][8020d7cc][801384c8][80136bf8][80104af0][80104348][80138350][80136d78][80104b50][80136a24][80137a98][80137a70][80105444][80138c18][80057af0][8006ecf8][c0263034][8006eec4][8004bff4][8003aed8][8006a800][8000b0d0] Code: 9082 03e8 304200ff 9482 03e8 3042 8c82 03e8 Error (Oops_bfd_perror): scan_arch for specified architecture File in wrong format Sorry, looks like your binutils cannot handle the specified architecture RA; 8015dfe4 ssb_pci_read16+58/7c $12; 802a swap_info+18c/88c $14; 80298588 per_cpu__runqueues+30/410 $15; 802985a8 per_cpu__runqueues+50/410 $31; 8015dfe4 ssb_pci_read16+58/7c ???; 8011635c ioread16+0/c = Trace; c02fd094 END_OF_CODE+40052754/ Trace; 800c7294 sysfs_new_dirent+7c/128 Trace; c01d0140 END_OF_CODE+3ff25800/ Trace; 8015bfac ssb_device_probe+44/7c Trace; 800c7a6c sysfs_create_dir+3c/58 Trace; 8010457c kobject_get+20/34 Trace; 80138030 driver_probe_device+16c/288 Trace; 80137fd4 driver_probe_device+110/288 Trace; 8020d7cc klist_next+6c/a4 Trace; 801384c8 __driver_attach+178/2d8 Trace; 80136bf8 next_device+10/2c Trace; 80104af0 kobject_add_varg+58/78 Trace; 80104348 kobject_init+58/9c Trace; 80138350 __driver_attach+0/2d8 Trace; 80136d78 bus_for_each_dev+5c/a8 Trace; 80104b50 kobject_init_and_add+40/58 Trace; 80136a24 bus_get+28/3c Trace; 80137a98 bus_add_driver+cc/2b4 Trace; 80137a70 bus_add_driver+a4/2b4 Trace; 80105444 kobject_uevent_env+3dc/42c Trace; 80138c18 driver_register+80/128 Trace; 80057af0 free_hot_cold_page+18c/1e4 Trace; 8006ecf8 remove_vm_area+4c/78 Trace; c0263034 END_OF_CODE+3ffb86f4/ Trace; 8006eec4 __vunmap+f8/12c Trace; 8004bff4 sys_init_module+1420/15cc
Re: [OpenWrt-Devel] cross ksymoops
On Fri, 17 Oct 2008, Brian J. Murrell wrote: I have patched the openwrt buildroot to build a cross-ksymoops. It seems I have an array of target and architectures I can choose from. ksymoops tells me they are: Well done! $ staging_dir/toolchain-mipsel_gcc4.1.2/bin/mipsel-linux-uclibc-ksymoops -a '?' ksymoops 2.4.11 on i686 2.6.27-6-generic. Options used ... Architectures supported by your libbfd mips mips:3000 mips:3900 mips:4000 mips:4010 mips:4100 mips:4111 mips:4120 [...] Error (Oops_bfd_perror): scan_arch for specified architecture File in wrong format Sorry, looks like your binutils cannot handle the specified architecture I'd run it with -a mips:4000 looking at that list, assuming I've remembered your processor correctly (Broadcom bcm47xx series?) ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] cross ksymoops
On Fri, 17 Oct 2008, Brian J. Murrell wrote: Code: 9082 03e8 304200ff 9482 03e8 3042 8c82 03e8 /usr/bin/mipsel-linux-uclibc-objdump: Can't disassemble for architecture UNKNOWN! [...] Notice the /usr/bin/mipsel-linux-uclibc-objdump: Can't disassemble for architecture UNKNOWN! above. It was a small problem in my ksymoops cross-build, but to remedy it (the build error is fixed of course) I have done: $ ls -l /usr/bin/mipsel-linux-uclibc-objdump lrwxrwxrwx 1 root root 86 2008-10-17 07:27 /usr/bin/mipsel-linux-uclibc-objdump - /usr/src/openwrt/staging_dir/toolchain-mipsel_gcc4.1.2/bin/mipsel-linux-uclibc-objdump $ ls -lL /usr/bin/mipsel-linux-uclibc-objdump -rwxr-xr-x 2 brian brian 381228 2008-10-16 19:14 /usr/bin/mipsel-linux-uclibc-objdump So that shouldn't be the problem. Maybe my cross-build was not successful. Try -a r4000 instead. That's what my objdump claims to support as a -m switch (of course we're guessing about how ksymoops calls objdump, but it's an educated guess) ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] setting kernel config parameters from ./files/
Is there any reference document explaining the structure of ./files/ directory? For example, include/kernel.mk uses it to copy some custom modules into the target's lib/modules/$(LINUX_VERSION)/ What I'd like to have is a consistent, file-based way to influence the kernel config options, so that they are not overridden by the next make menuconfig. In the short term, I want to build a kernel which would have CONFIG_CMDLINE pointing the root to the USB stick -- basically it's what bifferos is doing in his squidge distribution. But I want to make it possible in a way that is consistent with the OpenWRT mainline. Another approach would be to add a menu option for CONFIG_CMDLINE into the OpenWRT's menuconfig script. It's not a problem for me to produce a patch for the makefiles, but I'd like to hear your opinions first. thanks, stan ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] setting kernel config parameters from ./files/
I meant, having an option to add anything by just creating ./files/linux-2.6/.config looks a much more flexible approach than just adding another option to the Config.in. Ideally the makefiles would search for the custom kernel config in ./files/linux/.config ./files/linux-2.6/.config ./files/linux-2.6.26/.config sequentially - Original Message From: Stanislav Sinyagin [EMAIL PROTECTED] To: openwrt-devel@lists.openwrt.org Sent: Saturday, October 18, 2008 2:09:11 AM Subject: [OpenWrt-Devel] setting kernel config parameters from ./files/ Is there any reference document explaining the structure of ./files/ directory? For example, include/kernel.mk uses it to copy some custom modules into the target's lib/modules/$(LINUX_VERSION)/ What I'd like to have is a consistent, file-based way to influence the kernel config options, so that they are not overridden by the next make menuconfig. In the short term, I want to build a kernel which would have CONFIG_CMDLINE pointing the root to the USB stick -- basically it's what bifferos is doing in his squidge distribution. But I want to make it possible in a way that is consistent with the OpenWRT mainline. Another approach would be to add a menu option for CONFIG_CMDLINE into the OpenWRT's menuconfig script. It's not a problem for me to produce a patch for the makefiles, but I'd like to hear your opinions first. thanks, stan ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
