Quoting Gary Li <[EMAIL PROTECTED]>:
> Hi,
>
>
>
> I am a newbie for openwrt. I am puzzled about patches.
>
> Generally, In the patch directory, there r several patches like
> 001-XXX.patch and 002-XXX.patch etc.
>
> I want to know, when compile, what about the turn of patching to the source
> cod
Hi,
I am a newbie for openwrt. I am puzzled about patches.
Generally, In the patch directory, there r several patches like
001-XXX.patch and 002-XXX.patch etc.
I want to know, when compile, what about the turn of patching to the source
code?
Does it patch according to the NO. ?
001, 002...
applied, thanks
Quoting Alina Friedrichsen <[EMAIL PROTECTED]>:
> The remote address is $5 and not $4.
>
> /ppp-2.4.3/scripts/ipv6-up.sample
>> # This script is called with the following parameters: # interface
>> tty speed local-address remote-address ipparam
>
> Signed-off-by: Alina Friedrich
Hello again,
Sorry for previous mangled line wrapping (this is my first patch
submission).
Here is another try! The patch is also attached to ticket #3785.
---
Regarding https://dev.openwrt.org/cgi-bin/trac.fcgi/ticket/3785
I've been running dovecot 1.1.1 on my WL-500P (brcm-47xx) for a week a
Hello,
Regarding https://dev.openwrt.org/cgi-bin/trac.fcgi/ticket/3785
I've been running dovecot 1.1.1 on my WL-500P (brcm-47xx) for a week and
recently updated to 1.1.2 and cleaned up the patches, see attached
dovecot-1.1.2.svn.patch
The updated configure.in.patch was inspired by optware and fu
You suspicious are right:
[EMAIL PROTECTED] Desktop]# ./boot_linux -F -d eth0 -i owrt.zImage Using
internal boot loader: INTERNAL_NW - Network boot (default).
Starting boot...
We're doing a flash write, this may take up to a few minutes...
Device ID = 0xb7f7
This bootloader was built by root
The remote address is $5 and not $4.
/ppp-2.4.3/scripts/ipv6-up.sample
# This script is called with the following parameters: # interface tty
speed local-address remote-address ipparam
Signed-off-by: Alina Friedrichsen <[EMAIL PROTECTED]>
Index: package/ppp/files/etc/ppp/ipv6-up
=
If anyone is really missing a driver for onboard speaker on RB133,
here is an ugly hack that uses it from userspace:
http://artax.karlin.mff.cuni.cz/~zajio1am/software/wmon/
--
Elen sila lumenn' omentielvo
Ondrej 'SanTiago' Zajicek (email: [EMAIL PROTECTED])
OpenPGP encrypted e-mails preferred
Hinko Kocevar wrote:
>
> I'll give it a try.
Kamikaze image produces the same result for me here. Up until now I never used
kamikaze image(s)
on my hardware :( and wasn't aware of the problem. I've mainly used owrt for
toolchain generating.
I found out that owrt somehow mangles kernel image w
On Mon, Jul 28, 2008 at 11:43:38AM +0200, Roberto Riggio wrote:
> This patch allows the user to select the version
> of madwifi to be built. At the moment the following
> sources are supported:
>
> - Use subversion revision 3314
> - Use subversion revision 3776
> - Use stable release version 0.9
MichelinoK wrote:
> Big-Cut :)
>
>
>> Both outputs look sane - could you please post the output of these two
>> commands as well:
>> 2. ./boot_linux -F -d eth0 -i openwrt-etrax-jffs2-64k-fimage -p
>
> The output is this:
>
> [EMAIL PROTECTED] Desktop]# ./boot_linux -F -d eth0 -i
> kamikaze/tr
11 matches
Mail list logo