On Friday 27 July 2012 03:18:44 Luka Perkov wrote:
> You were not in MAINTAINER macro.
That is true; to be a real maintainer I would argue that it's necessary to
have commit access - I have inquired about it in the past but nothing was
forthcoming, if I had the ability to commit to the repo, I w
On 26/07/2012, at 8:42 PM, Luka Perkov wrote:
> On Thu, Jul 26, 2012 at 11:58:48PM +0100, Tim Fletcher wrote:
>> On 26/07/12 00:43, Frank Horowitz wrote:
>>> The device needs to be powered off and back on to come back from this
>>> hang.
>>>
>>> I've setup the environment above to be able to boo
On Fri, Jul 27, 2012 at 02:59:41AM +0200, Oliver wrote:
> On Friday 27 July 2012 01:09:43 Mirko Vogt wrote:
> > On 07/27/2012 12:24 AM, Oliver wrote:
> > > As it stands, it is *impossible* to build any of the dhcp tools with IPv6
> > > support due to this bug, so something should be done in the int
On Friday 27 July 2012 01:09:43 Mirko Vogt wrote:
> On 07/27/2012 12:24 AM, Oliver wrote:
> > As it stands, it is *impossible* to build any of the dhcp tools with IPv6
> > support due to this bug, so something should be done in the interim.
>
> You might have a valid point, however your attitude t
On Thu, Jul 26, 2012 at 11:58:48PM +0100, Tim Fletcher wrote:
> On 26/07/12 00:43, Frank Horowitz wrote:
> >The device needs to be powered off and back on to come back from this
> >hang.
> >
> >I've setup the environment above to be able to boot into the still
> >stock iconnect firmware (other than
On 07/27/2012 12:24 AM, Oliver wrote:
> As it stands, it is *impossible* to build any of the dhcp tools with IPv6
> support due to this bug, so something should be done in the interim.
You might have a valid point, however your attitude to _demand_ getting
this fixed (instead of just politely cal
On 26/07/12 00:43, Frank Horowitz wrote:
Hi All,
The device needs to be powered off and back on to come back from this hang.
I've setup the environment above to be able to boot into the still stock iconnect firmware (other
than the re-flashed u-boot and my environment, of course) using the c
On Thursday 26 July 2012 16:54:57 Mirko Vogt wrote:
> The point is: We want to tell, from the package name, what's inside an
> ipkg archive.
> This is not possible with so-called 'conditional dependencies', which
> influence the
> build, taking other config options into account.
> Vice versa that m
Daniel,
can you verify this on one of your units ?
Thanks,
John
On 26/07/12 17:04, Сергей Василюгин wrote:
> No device to check but it looks like a typo.
>
>
> Signed-off-by: Serge Vasilugin
>
> Index: target/linux/ramips/files/drivers/net/ethernet/ramips/ramips_main.c
> ===
ew-dorin: added USB support
Signed-off-by: Reiner Rusnak
---
Index: target/linux/ar71xx/generic/profiles/ew.mk
===
--- target/linux/ar71xx/generic/profiles/ew.mk (revision 32832)
+++ target/linux/ar71xx/generic/profiles/ew.mk (wor
No device to check but it looks like a typo.
Signed-off-by: Serge Vasilugin
Index: target/linux/ramips/files/drivers/net/ethernet/ramips/ramips_main.c
===
--- target/linux/ramips/files/drivers/net/ethernet/ramips/ramips_main.c
(r
ew-dorin: added router firmware generation
Signed-off-by: Reiner Rusnak
---
Index: target/linux/ar71xx/files/arch/mips/ath79/mach-ew-dorin.c
===
--- target/linux/ar71xx/files/arch/mips/ath79/mach-ew-dorin.c (revision
32832)
+++ t
The point is: We want to tell, from the package name, what's inside an
ipkg archive.
This is not possible with so-called 'conditional dependencies', which
influence the
build, taking other config options into account.
Vice versa that means: We want to avoid having one and the same package
(as in
'n
On Thursday 26 July 2012 16:07:15 John Crispin wrote:
> i am talking about a version with and without ipv6. Or to make it easy
> to understand, IPV4 and dual stack.
Which is exactly how I originally had it - it sat in its own section as
"dhcp4" and there was a checkable option to enable IPv6 supp
Is this normal now? It didn't used to be so.
-K-
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
On 26/07/12 16:04, Oliver wrote:
> On Thursday 26 July 2012 15:57:14 John Crispin wrote:
>> Really, I think it's insufficient to just check CONFIG_IPV6. i want a
>> build without and one with ipv6 version with the latter being depended
>> on CONFIG_IPV6. Doing what you propose means a ipkg is gener
On Thursday 26 July 2012 15:57:14 John Crispin wrote:
> Really, I think it's insufficient to just check CONFIG_IPV6. i want a
> build without and one with ipv6 version with the latter being depended
> on CONFIG_IPV6. Doing what you propose means a ipkg is generated that
> can have 1 of 2 binaries i
On 26/07/12 15:53, Oliver wrote:
> On Thursday 26 July 2012 15:32:22 John Crispin wrote:
>> Hi Oliver,
>>
>> i think making a build_variant for ip4 and ip6 is a better solution than
>> creating a menuconfig option.
>
> Really, I think it's sufficient to just check CONFIG_IPV6 - separating the
> t
On Thursday 26 July 2012 15:32:22 John Crispin wrote:
> Hi Oliver,
>
> i think making a build_variant for ip4 and ip6 is a better solution than
> creating a menuconfig option.
Really, I think it's sufficient to just check CONFIG_IPV6 - separating the two
builds is really not feasible unless you
On 26/07/12 15:14, Oliver wrote:
> To whoever reworked my ISC-DHCP package into regular old DHCP:
>
> You left in the CONFIG_DHCP4_ENABLE_IPV6 checks without actually putting it
> as
> an option in the menu, so right now, all builds will have IPv6 support
> disabled.
>
> Please either add the
To whoever reworked my ISC-DHCP package into regular old DHCP:
You left in the CONFIG_DHCP4_ENABLE_IPV6 checks without actually putting it as
an option in the menu, so right now, all builds will have IPv6 support
disabled.
Please either add the option back to menuconfig for enabling/disabling I
21 matches
Mail list logo
