>Would you mind documenting the process you used to get the build
>system to use a not stable kernel?
>
>Because it is an RC release, was it enough to just change the
>LINUX_VERSION in the appropriate makefile?
LINUX_VERSION is what needs to be updated on the
target/linux/platform/Makefile. in th
Would you mind documenting the process you used to get the build
system to use a not stable kernel?
Because it is an RC release, was it enough to just change the
LINUX_VERSION in the appropriate makefile?
Thanks,
wt
On Mon, Jan 26, 2009 at 12:16 PM, Alexandros C. Couloumbis wrote:
> I have conv
I just want to note that I resumed work on the WL500gV2, which
has a b43 based LP-PHY wireless device.
I cannot make any guarantees or timelines, just that it's done when it's done.
I'll first look into making the serial port work.
--
Greetings, Michael.
__
I have converted some 2.6.28 patches to apply against a linux-2.6.29-rc2
kernel. this is not a complete work as a few things still do not work
but it does produce a bootable openwrt 2.6.29-rc2 system on an rb532
device. you can find these patches here:
http://wifi.ozo.com/airo/openwrt/source/2.6.29
Thanks Nico,
I will integrate asap on my experimental tree. I noticed a mistake
row 262:
+ ifndef ($(CONFIG_NATIVE_TOOLCHAIN),)
should be:
+ ifneq ($(CONFIG_NATIVE_TOOLCHAIN),)
Anyway, it should be great if a toolchain prepared using OpenWRT can be
exported to others developers.
I know
Hi Luigi,
I have a patch [1] for external toolchains support, it will allow you to
select your target name (powerpc-unknow-linux-gnu), toolchain commands
prefix, toolchain binaries & libraries path (for toolchains installed in
unusual locations and needing custom PATH & LD_LIBRARY_PATH).
Let me k
On Mon, Jan 26, 2009 at 6:23 PM, Luigi 'Comio' Mantellini
wrote:
> Hi ML,
>
> I need your help to understand the actual status of external toolchain
> support.
>
> In my environment, there are a lot of developers that works on an building
> environment openwrt-based. Openwrt is a good choice to ma
Hi ML,
I need your help to understand the actual status of external toolchain
support.
In my environment, there are a lot of developers that works on an building
environment openwrt-based. Openwrt is a good choice to manage my builds and :
I am happy to have chosen one year ago.
The big probl
On Mon, 2009-01-26 at 10:08 +0100, Harald Schiöberg wrote:
>
> it is the very image that ends up in ${TOPDIR}/bin/openwrt-avila-zImage
Hrm. My ${TOPDIR}/bin contains:
-rw-r--r-- 1 brian brian 1024 2009-01-23 03:38 md5sums
-rw-r--r-- 1 brian brian 1654563 2009-01-23 03:38
openwrt-brcm47xx-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brian J. Murrell wrote:
> On Wed, 2009-01-21 at 17:46 +0100, Harald Schiöberg wrote:
>> here is the script we use to boot an Openwrt from a running Openwrt.
>
> Thanx!
>
>> Make sure to have kexec-tools installed
>
> Indeed.
>
>> kexec -l /mnt/
10 matches
Mail list logo