Zintis wrote:
I was more like surprised that bdb package is in repository but doesnt
works
Welcome to the world of open source :)
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
http://lists.openwrt.org/cgi-bin/mailman/listinf
Felipe Maya wrote:
> e-mail to [EMAIL PROTECTED]
>
e-mail what exactly ?
Or are you just saying that's the way to ask the madwifi developers
if we can add our stuff to their code ?
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
http:
...do we have such a big mess of patches for madwifi ?
I'm just sayin... every time we pick up a new madwifi revision
most of the patches need to be re-done. Has anyone tried to
put, for example, the stuff that disables debug code, and the
multi-binary stuff back into the upstream code ? Just seem
Zintis wrote:
I'm trying to port Direct Connect Text Client for Broadcom 2.4 kernel.
It needs Berkeley DB. Although there is a package in repository, it
doesn't work -- I'm getting error: "unable to initialize mutex:
Function not implemented"
This might imply that the package was config
Felix Fietkau wrote:
btw, the fix I'm trying to use is in the trunk, rather than the DFS
branch version
you pointed me at earlier. This one : http://madwifi.org/changeset/3505
Well, what I actually meant was: try to backport this one to the OpenWrt
version of MadWiFi - that shouldn't be
I want to have trunk OpenWrt pick up this fix in
madwifi : http://madwifi.org/changeset/3505
I've been through this exercise once before (figuring
out which of the patches applied to madwifi are now
included in the upstream, which are no longer needed, etc).
However, I'm sure that others here kno
David Boreham wrote:
David Boreham wrote:
Felix Fietkau wrote:
I think you misunderstood the comment. This patch was added precisely
because the HAL does not provide the API to disable ANI. Also it was added
to trunk, which has that specific HAL version in question.
Just give it a try
David Boreham wrote:
Felix Fietkau wrote:
I think you misunderstood the comment. This patch was added precisely
because the HAL does not provide the API to disable ANI. Also it was added
to trunk, which has that specific HAL version in question.
Just give it a try :)
Hmm...I will do
Felix Fietkau wrote:
I think you misunderstood the comment. This patch was added precisely
because the HAL does not provide the API to disable ANI. Also it was added
to trunk, which has that specific HAL version in question.
Just give it a try :)
Hmm...I will do thanks.
_
David Boreham wrote:
Roberto Riggio wrote:
I was looking for this too. I will give it a try tomorrow on our mesh testbed.
That'd be very interesting thanks. I've got as far as launching a build
of 7_07
(which is what we are running in the field) that includes the 0.9
Roberto Riggio wrote:
> I was looking for this too. I will give it a try tomorrow on our mesh testbed.
>
That'd be very interesting thanks. I've got as far as launching a build
of 7_07
(which is what we are running in the field) that includes the 0.9.4 madwifi
integration from https://dev.openw
Felix Fietkau wrote:
I believe that http://madwifi.org/changeset/3375 is what you're looking for.
Unfortunately no. That changeset you will see says :
/* NB: INTMIT was not implemented so that it could be enabled/disabled,
* and actually in 0.9.30.13 HAL it really can't even be disabled bec
Hmm...looks like someone has already done the work to integrate madwifi
0.9.4:
https://dev.openwrt.org/ticket/3270
David Boreham wrote:
> Madwifi has a major problem with 802.11a sensitivity that makes it
> pretty much useless for long links.
> (the entire sorry tale can be seen in
Madwifi has a major problem with 802.11a sensitivity that makes it
pretty much useless for long links.
(the entire sorry tale can be seen in this bug :
http://madwifi.org/ticket/705)
I'm wondering if there is any prospect of making a 'fixed' madwifi that
is compatible with OpenWrt. This appears
I back-ported the AD7418 temp/voltage sensor driver from 2.6.22
to OpenWrt 7.07. Complete patch attached, and also copies of
the various post-patched files for ease of reviewing.
I didn't totally understand what I was doing with the build file
changes in openwrt so please excuse any blunders. I c
Imre Kaloz wrote:
> I had a .22-rc patchset, and have a .22 port somewhere. We didn't
> migrate due to the problems with the IDE controller with .22 on the FSG3.
> I can clean it up and put it online today or tomorrow if you want to
> give it a try.
That'd be useful if you could, thanks.
I'd begu
I want to use the ad7418 driver which is new in 2.6.22.
I'm wondering if it would be easier to a) use that kernel
or b) make a patch to back-port the driver to the existing
2.6.20 kernel ? Anyone have any thoughts ? Generally
I'd expect some of the patches would not apply to the newer
kernel, but I
17 matches
Mail list logo
