Re: [OpenWrt-Devel] kgdb?

2011-05-12 Thread Florian Fainelli
Hello, On Thursday 12 May 2011 00:38:40 John Zavgren wrote: > Dear readers: > > I need to debug a kernel loadable module via gdb when the kernel is running > on a device that doesn't have a traditional DB9/RS232 serial interface. > Although, it does have a USB interface that I might be able to us

Re: [OpenWrt-Devel] kgdb?

2011-05-12 Thread John Crispin
there is a good howto regarding kgdb on lmo http://www.linux-mips.org/wiki/KGDB ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] How does one build just one KLM?

2011-05-12 Thread Jo-Philipp Wich
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 It obviously depends on how your module is packaged. Do you patch it into the kernel tree? In this case the most fine grained make target to use is make target/linux/{clean,compile} . If you can you should consider packaging your source as an out-of

[OpenWrt-Devel] kernel 2.6.38.6 update

2011-05-12 Thread Peter Wagner
kernel 2.6.38.6 update i only tested it on brcm47xx and it works like a charm - but brcm47xx is still on 2.6.37 i didnt include it in the patch... Signed-off-by: Peter Wagner with kind regards, Peter Wagner diff --git a/target/linux/at91/Makefile b/target/linux/at91/Makefile index f285c2c..33df

Re: [OpenWrt-Devel] How does one build just one KLM?

2011-05-12 Thread edgar . soldin
Could you post your makefile here?.. ede On 12.05.2011 02:02, John Zavgren wrote: > Thanks, Christian: > > I read the article on the wiki and then I tried "make > package/vislinkRcv/compile" from the TOPDIR (vislinkRcv is the stuff that I'm > developing) and no KLM was actually built. When I d

[OpenWrt-Devel] Add Artec ThinCan targets

2011-05-12 Thread lauri
Hi, I attached two patches: * First one adds support for Artec ThinCans (currently DBE61 only) * Second one adds mkelfimage and wraplinux tools needed to generate Etherboot images for DBE61 and DBE60 respectively -- Lauri Võsandi tel: +372 53329412 e-mail: lauri.vosa...@gmail.com company: Povi

Re: [OpenWrt-Devel] How does one build just one KLM?

2011-05-12 Thread John Zavgren
Here's the Makefile. Thanks, John -- # # Copyright (C) 2006 OpenWrt.org # # This is free software, licensed under the GNU General Public License v2. # See /LICENSE for more information. # # $Id: Makefile 10203 2008-01-15 03:25:11Z matteo $ include $(TOPDIR)/rules.mk include $(INCL

Re: [OpenWrt-Devel] How does one build just one KLM?

2011-05-12 Thread edgar . soldin
isn't it build in the build_dir or just not installed? i see no install definition in your makefile. as jow wrote > f you can you should consider packaging your source as an out-of-tree > module, see for example the KernelPackage / kmod defintions in > package/wprobe/Makefile . ede On 12.05.201

Re: [OpenWrt-Devel] How does one build just one KLM?

2011-05-12 Thread John Zavgren
It get's built and staged when I do a "global" make. I want a technique for making just this one KLM, so that I don't need to build the entire enchilada, every time I make a change to it's source code. I don't care where the .ko file lands, because I'm moving it to my target (via scp) anyway. (I

Re: [OpenWrt-Devel] How does one build just one KLM?

2011-05-12 Thread edgar . soldin
so where does a (in buildroot root) $> make package//{clean,compile} V=99 leave you?... attach the output or pastebin it .. also check if the new binary is created in builddir ..ede On 12.05.2011 16:08, John Zavgren wrote: > It get's built and staged when I do a "global" make. > > I want

Re: [OpenWrt-Devel] How does one build just one KLM?

2011-05-12 Thread John Zavgren
Thank you SO much for your help. I've identified my problem. It seems that I need to make the clean target before I make the compile target, otherwise, the KLM isn't generated. This recipe works: make package/vislinkRcv/clean V=99 make package/vislinkRcv/compile V=99 On Thu, May 12, 2011 at 10:

Re: [OpenWrt-Devel] How does one build just one KLM?

2011-05-12 Thread edgar . soldin
welcome.. you could also manually remove builddir. buildroot is putting files in builddir (.prepared and the like). this is to circumvent to prepare,rebuild,install something again (e.g. when recompile an image with one added pkg added in menuconfig). keep that in mind and you are set for your

[OpenWrt-Devel] [PATCH v2 1/1] alix2: provide x86/alix2 subtarget

2011-05-12 Thread Philip A. Prindeville
This patch provides an image suitable for the alix2*, alix3, and alix6 headless (non-VGA equipped) SBC's. Note that the Alix6 uses GPIO 27 to disable wireless transmit (W_DIS#), whereas on all other versions this is used to actuate the speaker. GPIO 1 : SIM select (Alix6) GPIO 6 : LED1 GPIO 25

Re: [OpenWrt-Devel] [PATCH v2 1/1] alix2: provide x86/alix2 subtarget

2011-05-12 Thread John Crispin
On 12/05/11 20:47, Philip A. Prindeville wrote: > BOARDNAME:=x86 > FEATURES:=squashfs jffs2 ext4 vdi vmdk pcmcia targz > -SUBTARGETS=generic olpc xen_domu ep80579 net5501 kvm_guest geos > +SUBTARGETS=generic olpc xen_domu ep80579 net5501 kvm_guest geos alix2 > > -LINUX_VERSION:=2.6.37.6 > +LINU

Re: [OpenWrt-Devel] [OpenWrt] #7768: block-extroot on WRT54GL (v1.1) SD card (mmc) overlay double mount problem

2011-05-12 Thread Daniel Dickinson
On Mon, 25 Apr 2011 23:15:25 - "OpenWrt" wrote: > #7768: block-extroot on WRT54GL (v1.1) SD card (mmc) overlay double > mount problem > +--- > Reporter: lance@…| Owner: cshore Type: > defect

[OpenWrt-Devel] [PATCH v3 1/1] alix2: provide x86/alix2 subtarget

2011-05-12 Thread Philip Prindeville
This patch provides an image suitable for the alix2*, alix3, and alix6 headless (non-VGA equipped) SBC's. Note that the Alix6 uses GPIO 27 to disable wireless transmit (W_DIS#), whereas on all other versions this is used to actuate the speaker. GPIO 1 : SIM select (Alix6) GPIO 6 : LED1 GPIO 25