The Microsoft MN-700 router (very similar to the ASUS WL-500g) is not
detected correctly by the broadcom-diag kernel module. Also it is not
possible to switch off the power LED after it was enabled. With the
included patch these two issues are solved. It also exports the LED
flash interval via /pro
Nico wrote:
> You can use the "CompareKernelPatchVer" macro, defined in
> ./include/kernel.mk.
> A typical use can be found in ./package/fuse/Makefile.
In this case it's probably better to simply use $(CONFIG_LINUX_2_6)
All of our actively maintained targets are on 2.6.23 or later...
- Felix
You can use the "CompareKernelPatchVer" macro, defined in
./include/kernel.mk.
A typical use can be found in ./package/fuse/Makefile.
Regards,
--
Nico
Hauke Mehrtens wrote:
> If kernel is *not* 2.6.23 or 2.6.24 the headers of libnl where not
> exported, but hostapd needs the headers to build.
>
If kernel is *not* 2.6.23 or 2.6.24 the headers of libnl where not
exported, but hostapd needs the headers to build.
This patches corrects the problem.
x86 image doesn't build without this patch.
Or is there a better way to detect an image for kernel 2.6?
--
Hauke Mehrtens
Index: Makefile
ZioPRoTo (Saverio Proto) wrote:
> Is it yet possibile to use that driver and build the OpenWRT image for
> the Fonera ?
>
No, ath5k has to be changed to support the AHB bus.
But I'd also like to know if there is anything planned regarding this
cause MadWifi is now basically deprecated.
- Axel
Hello,
the latest 2.6.25 kernel ships the ath5k wireless driver...
I saw that the latest OpenWRT trunk has Linux 2.6.25 but I cant find
ath5k in there :(
Any pointers ?
Is it yet possibile to use that driver and build the OpenWRT image for
the Fonera ?
Saverio
__
nice1 if they work for me tonight i will merge them with your usb driver
update
Hinko Kočevar wrote:
> Imre Kaloz wrote:
>> On Fri, 30 May 2008 13:46:53 +0200, Hinko Kočevar
>> <[EMAIL PROTECTED]> wrote:
>>
>>> It does not matter - the objcopy creates 3GB file in both cases.
>>> [EMAIL PROTECTE
Imre Kaloz wrote:
> On Fri, 30 May 2008 13:46:53 +0200, Hinko Kočevar
> <[EMAIL PROTECTED]> wrote:
>
>> It does not matter - the objcopy creates 3GB file in both cases.
>> [EMAIL PROTECTED] ~/work/ws/linux-2.6-git $
>> /work/stage/openwrt-trunk/staging_dir/toolchain-cris_gcc4.2.3/bin/cris-linux-
On Fri, 30 May 2008 13:46:53 +0200, Hinko Kočevar
<[EMAIL PROTECTED]> wrote:
> It does not matter - the objcopy creates 3GB file in both cases.
> [EMAIL PROTECTED] ~/work/ws/linux-2.6-git $
> /work/stage/openwrt-trunk/staging_dir/toolchain-cris_gcc4.2.3/bin/cris-linux-uclibc-objcopy
> -O binary
John Crispin wrote:
>>> But I have another problem when compiling kernel with uvlibc generated
>>> toochain
>>> - the resulting arch/cris/boot/Image is 3GB large!? arch/cris/boot/zImage
>>> is
>>> later trimmed down to 'just' 4MB but still too big!!
>
> have you got debugging turned on in the
Hello,
I found some papers in the Internet that talk about a software called
ART (Atheros radio test).
This tool looks perfect for characterize in the right way the response
in terms of frequency and power of miniPCI cards.
I googled a bit but I found no website of this software... maybe is
not
Nicolas Schichan schrieb:
> On Thursday 29 May 2008 22:15:47 Tomasz Chmielewski wrote:
>> # kexec -e
>> b44: eth0: powering down PHY
>> Starting new kernel
>> Will call new kernel at 00305000
>
> The calling address of the kernel looks quite wrong, it should clearly
> be inside the KSEG0 zone. cou
>>
>> But I have another problem when compiling kernel with uvlibc generated
>> toochain
>> - the resulting arch/cris/boot/Image is 3GB large!? arch/cris/boot/zImage is
>> later trimmed down to 'just' 4MB but still too big!!
>
have you got debugging turned on in the kconfig ?
Hinko Kočevar wrote:
> John Crispin wrote:
>
>> yes, the cris-elf seems the problem. if we have a cris-elf that can
>> translate a head.S in to a working bin, then i can get the rest running
>> in no time. but until then you need the axis toolchain installed so we
>> can use their gcc_cris -mel
John Crispin wrote:
>
> yes, the cris-elf seems the problem. if we have a cris-elf that can
> translate a head.S in to a working bin, then i can get the rest running
> in no time. but until then you need the axis toolchain installed so we
> can use their gcc_cris -melf
Great.
But I have anot
Hinko Kočevar wrote:
> John Crispin wrote:
>>> What is the etrax status in openwrt? Does it use generated uclibc toolchain
>>> or
>>> vendor (Axis) provided glibc toochain?
>> i can run the generated images on a foxboard, only draw back is, that
>> the head.S in kernel needs to be compiled with
John Crispin wrote:
>> What is the etrax status in openwrt? Does it use generated uclibc toolchain
>> or
>> vendor (Axis) provided glibc toochain?
>
> i can run the generated images on a foxboard, only draw back is, that
> the head.S in kernel needs to be compiled with the axis toolchain.
> us
> What is the etrax status in openwrt? Does it use generated uclibc toolchain
> or
> vendor (Axis) provided glibc toochain?
i can run the generated images on a foxboard, only draw back is, that
the head.S in kernel needs to be compiled with the axis toolchain.
using the stage3 elf compiler, i
John Crispin wrote:
> i will try it out the following days
Have you had the chance to test the cris compiler and kernel?
I had partial success with the uclibc toolchain that openwrt produced.
The toolchain is based on uClibc 0.29.9 and gcc 4.2.3. It manages to build the
packages but, running the
19 matches
Mail list logo
