Comments below
Regards,
Roman
On 28 September 2010 19:44, Luca Niccoli wrote:
> This second version of the patch is rebased on the work done by Roman
> Yeryomin and applied in r23126.
> It corrects a minor miscalculation in the port rate code and cleans the
> code a bit, plus it
On 29 September 2010 23:23, Luca Niccoli wrote:
> On 29 September 2010 11:27, Roman Yeryomin wrote:
>
>> Realtek storm filtering code is commented out in rtl8366rb_api.c and
>> there are different registers defined in rtl8366rb_api.h - that's why
>> I'm in do
On 30 September 2010 02:10, Luca Niccoli wrote:
> On 29 September 2010 22:23, Luca Niccoli wrote:
>
>> (I still have to test the effect it has, though.)
>
> I'll have to rework this a bit, the switch can base its priority
> decisions on port, 802.1q priority tag, DSCP IP tag and ACL, so that
> ne
On 30 September 2010 02:23, Luca Niccoli wrote:
> On 30 September 2010 01:12, Roman Yeryomin wrote:
>> if to follow your logic you should append `|| val->value.i < 0` also
>
> Actually, this way one can use both 0 or any negative value to set
> unlimited bandwidth.
&
Signed-off-by: Roman Yeryomin
Index: feeds/packages/libs/spandsp/Makefile
===
--- a/feeds/packages/libs/spandsp/Makefile (revision 0)
+++ b/feeds/packages/libs/spandsp/Makefile (revision 0)
@@ -0,0 +1,44 @@
+#
+# Copyright
On 18 October 2010 12:30, Michael Büsch wrote:
> On Mon, 2010-10-18 at 02:22 +0300, Roman Yeryomin wrote:
>> Signed-off-by: Roman Yeryomin
>>
>> +
>> +TARGET_CFLAGS += $(FPIC)
>> +MAKE_FLAGS += all install DESTDIR=$(PKG_INSTALL_DIR)
>
> This most likely bre
>> On 29 September 2010 13:22, Roman Yeryomin wrote:
>>> Add rtl8366 switch kernel packages so that they could be selected if a
>>> user has board with such switch.
>>
ping
___
openwrt-devel mailing list
openwrt
so... what others think? it doesn't worth doing like this?
Regards,
Roman
On 29 September 2010 15:45, Roman Yeryomin wrote:
> I've tested this with ramips board.
> Of cause device should be registered but it's intended to be selected
> automatically via target boa
ok, here goes the second part:
rtl8366 generic vlan fid support
Those who will use this don't forget to `set vlan fid` every time
after `set vlan ports` if you want non default behavior.
Minor changes. Version bump.
Signed-off-by: Roman Yeryomin
--
Index: target/linux/generic/files/driver
Hello!
Is there anything wrong with this?
Regards,
Roman
On 27 October 2010 04:57, Roman Yeryomin wrote:
> ok, here goes the second part:
>
> rtl8366 generic vlan fid support
> Those who will use this don't forget to `set vlan fid` every time
> after `set vlan ports` if
Allows to use fids 0 to 7. Default is 0.
Those who will use this don't forget to `set vlan fid` every time
after `set vlan ports` if you want non default behavior.
Minor changes. Version bump.
I've already sent this patch but it seems that it was lost in threads.
Signed-off-by: Roma
This is v2 patch which defines these modules as built-in. As Jonas
pointed earlier it's not the best way to use such drivers as real
modules.
This is intended to be selected via board profiles but of cause can be
selected manually too.
Tested with ramips target.
Signed-off-by: Roman Yer
No support for usb for now.
Signed-off-by: Roman Yeryomin
--
Index: target/linux/ramips/files/arch/mips/ralink/rt305x/Makefile
===
--- a/target/linux/ramips/files/arch/mips/ralink/rt305x/Makefile
(revision
22707)
+++ b
Why do we need to add DEFAULT_PACKAGES if we have default profile?
Fix package name in default profile.
Signed-off-by: Roman Yeryomin
--
Index: target/linux/ramips/rt305x/profiles/00-default.mk
===
--- a/target/linux/ramips/rt305x
Use it for Belkin F5D8235 v2 for now. Or add other boards.
Signed-off-by: Roman Yeryomin
--
Index: target/linux/ramips/rt305x/profiles/belkin.mk
===
--- a/target/linux/ramips/rt305x/profiles/belkin.mk (revision 0)
+++ b/target
This magic is from original driver. Maybe ramips_esw can be rewritten
to support swconfig but this will do the job for now.
Tested with Belkin F5D8235 v2 board.
Signed-off-by: Roman Yeryomin
--
Index: target/linux/ramips/files/drivers/net/ramips_esw.c
On 24 November 2010 11:56, Gabor Juhos wrote:
> 2010.11.20. 2:22 keltezéssel, Roman Yeryomin írta:
>> Why do we need to add DEFAULT_PACKAGES if we have default profile?
>
> Why would we have to add those packages to each profile?
>
ok, then there is no need to list same pa
On 24 November 2010 12:07, Gabor Juhos wrote:
> 2010.11.20. 2:35 keltezéssel, Roman Yeryomin írta:
>> This magic is from original driver. Maybe ramips_esw can be rewritten
>> to support swconfig but this will do the job for now.
>> Tested with Belkin F5D8235 v2 board.
>&
applied in 24125
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
applied in 24126
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Fix package names in default profiles.
Signed-off-by: Roman Yeryomin
--
Index: target/linux/ramips/rt305x/profiles/00-default.mk
===
--- a/target/linux/ramips/rt305x/profiles/00-default.mk (revision 24146)
+++ b/target/linux/ramips
Belkin profile v2
Signed-off-by: Roman Yeryomin
--
Index: target/linux/ramips/rt305x/profiles/belkin.mk
===
--- a/target/linux/ramips/rt305x/profiles/belkin.mk (revision 0)
+++ b/target/linux/ramips/rt305x/profiles/belkin.mk
On 20 November 2010 03:09, Roman Yeryomin wrote:
> This is v2 patch which defines these modules as built-in. As Jonas
> pointed earlier it's not the best way to use such drivers as real
> modules.
> This is intended to be selected via board profiles but of cause can be
> s
On 10 March 2011 19:09, Layne M. Edwards wrote:
> Also, the switch configuration (swconfig) is not working as expected (when
> using r24328). The VLANs for LAN (eth0.1) and WAN (eth0.2) are not
> configured properly by default (i.e. WAN port is on one of the LAN ports).
> Modifying the swconfig i
401 - 424 of 424 matches
Mail list logo
