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 do the general purpose
"make" operation from the same context, it is built.
Confused.
On Wed, M
>> A 'make path/to/package/compile' (i.e. 'make package/busybox/compile')
>> in the TOPDIR with an optional V=99 switch will do the trick.
>
> Note that the "patch/to/package" bit is misleading.
>
> Even if a package is in package/feeds/packages/foobar/ you can still
> just say make package/foob
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> A 'make path/to/package/compile' (i.e. 'make package/busybox/compile')
> in the TOPDIR with an optional V=99 switch will do the trick.
Note that the "patch/to/package" bit is misleading.
Even if a package is in package/feeds/packages/foobar/ you ca
The Wiki basically answers it:
http://wiki.openwrt.org/doc/howto/build
A 'make path/to/package/compile' (i.e. 'make package/busybox/compile') in the
TOPDIR with an optional V=99 switch will do the trick.
Cheers,
Christian
On May 12, 2011, at 12:40 AM, John Zavgren wrote:
> If I wish to build j
If I wish to build just one KLM (or application, or library), is there a way
I can target my build to just that one thing? At this time, I'm executing a
make command at the top level of the openWRT source tree, every time I wish
to cross compile something. And, ... , that's awfully slow.
Thanks,
J
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 use in some
way (help!) to create a serial interface that I could connect
On 2011-05-11 10:13 AM, Emmanuel Deloget wrote:
On 05/10/2011 07:03 PM, Felix Fietkau wrote:
On 2011-05-10 3:37 PM, Emmanuel Deloget wrote:
Hello,
I'm facing an interesting porting challenge : one of the program which
is to be installed on our target is compressed using upx. As you may
kn
On Sunday 24 April 2011 16:05:31 Jonas Gorski wrote:
> Add the required board definition, default config and image generation for
> the T-Home Speedport W 303V Typ B.
>
> Signed-off-by: Jonas Gorski
> ---
Applied in r26878, thanks!
--
Florian
___
openw
On Sunday 24 April 2011 16:05:30 Jonas Gorski wrote:
> Add two helpers for generating correctly tagged images for the T-Home
> Speedport W 303V Typ B as well as xor'd ones as required by CFE.
>
> Signed-off-by: Jonas Gorski
> ---
Applied in r26877, thanks!
--
Florian
On Thursday 21 April 2011 05:37:17 Jonas Gorski wrote:
> Signed-off-by: Jonas Gorski
> ---
Applied in r26875, thanks!
--
Florian
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
On Thursday 21 April 2011 05:37:18 Jonas Gorski wrote:
> Rename the DSL-274xB rev C2's board ID to "AW4139" to match the one used
> for the rev C3 (same hardware) and add a fixup for C2. Also generate
> images for C3.
>
> While we are at it, rename the LEDs to conform to the Linux LED naming
> con
On Thursday 21 April 2011 05:37:16 Jonas Gorski wrote:
> Make the fixup board ID independent from the image name to allow using
> the same board ID for similar devices.
>
> Signed-off-by: Jonas Gorski
> ---
Applied in r26874, thanks!
--
Florian
___
ope
There's only 2.6, so it doesn't make sense to mention modules that are
2.4 only or for modules that they are available only for 2.6.
Signed-off-by: Jonas Gorski
---
package/kernel/modules/netfilter.mk | 20
1 files changed, 8 insertions(+), 12 deletions(-)
diff --git a/pa
Since the oldest kernel in trunk is 2.6.30 the modules always use the
newer names, so we can just use the _generic prefix directly.
Signed-off-by: Jonas Gorski
---
package/kernel/modules/crypto.mk | 32 +---
1 files changed, 9 insertions(+), 23 deletions(-)
diff --
With no 2.4 support in trunk, we can safely remove any 2.4 definitions for
kmods and merge the 2.6 definitions into the generic ones.
Signed-off-by: Jonas Gorski
---
Changes RFT -> V1:
* Removed one superflous added line
package/kernel/modules/block.mk | 47 -
Over the time the kernel module definitions have collected a lot of
workarounds for the differences between 2.4 and 2.6 kernels, and for
differences between older and newer 2.6 kernels.
Since the oldest supported kernel in trunk is now 2.6.30, we can safely
drop most of these workarounds.
We can
Since there's only 2.6 in trunk $(KMOD_SUFFIX) can be safely replaced with
ko for all mainline kernel modules.
Signed-off-by: Jonas Gorski
---
package/kernel/modules/block.mk | 30 +++---
package/kernel/modules/netfilter.mk |2 +-
package/kernel/modules/netsup
The patch I sent works for me with Mikrotik's RB52n cards (ie.
802.11n). I don't plan to test anything else, as this is what
satisfies me. You may find my userspace code on my website [1], in
generator.git/interface.c.
[1] http://www.iitis.pl/~pjf/
2011/5/10 Roberto Riggio :
> Did you have any l
On 05/10/2011 07:03 PM, Felix Fietkau wrote:
On 2011-05-10 3:37 PM, Emmanuel Deloget wrote:
Hello,
I'm facing an interesting porting challenge : one of the program which
is to be installed on our target is compressed using upx. As you may
know, upx-compressed programs are not to be stripped (st
19 matches
Mail list logo
