While trying to add ar8316 support to the ar8216 driver, I noticed
several small issues in the driver itself. Since I lack an ar8216
to test, somebody please verify I did not break it.
This patch makes the following changes:
* Create defines for some magic values/masks.
* Change vlan_id to
Felix Fietkau írta:
Applied in r20083, with one exception. I left out this change:
-#define AR8216_GCTRL_MTU BITS(0, 10)
+#define AR8216_GCTRL_MTU BITS(0, 14)
as it does not match my hardware info for AR8216.
Apart from this, the original value seems to be wrong:
On 2010-03-09 12:28 PM, Jonas Gorski wrote:
While trying to add ar8316 support to the ar8216 driver, I noticed
several small issues in the driver itself. Since I lack an ar8216
to test, somebody please verify I did not break it.
This patch makes the following changes:
* Create defines
On 2010-03-09 4:09 PM, Gabor Juhos wrote:
Felix Fietkau írta:
Applied in r20083, with one exception. I left out this change:
-#define AR8216_GCTRL_MTU BITS(0, 10)
+#define AR8216_GCTRL_MTU BITS(0, 14)
as it does not match my hardware info for AR8216.
Apart from
Does anybody succeeded to debug a multithread app with kamikaze 8.09.1 ?
When I set a breakpoint to a function gdb correctly stops there when
my code hits that point, unfortunately gdb shows me only the main
thread (and in my case it's another thread that hit the breakpoint, so
I can't see
Most important is Compile the kernel with symbol table information under
Global build settings.
This will resolve all hex addresses to their related names.
I set that option [*], but no more information is printed.
___
openwrt-devel mailing list
Apart from this, the original value seems to be wrong:
(((1UL 10) - 1) 0) = 0x3ff = 1023
The switch should be able to handle larger frames than this.
You're right. The datasheet says bits 0:10, so it should have been 11
bits not 10. Fixed in r20110
Following this logic then 14
