Hello, So, I don't know on which chips this feature is supported. Our chip of interest is the BCM53128. Maybe I could first add a "is53128()" function, so that it's only specific to this chip, especially since we want to push more features that we've developed on this particular chip. Then, if others find that it works on other chips, it could be adapted/extended.
To answer the questions: A port that is marked protected means that it cannot talk to another port that is marked protected. A protected port can send data to an unprotected port, and unprotected ports can send data to any port. This can be adapted into a sort of a security feature. The Broadcom default is for the protected mode to be off in hardware, but our board has this default overridden in hw, because it is required in several of our use-cases. So, unsetting those bits sets the default behaviour, which should not affect normal behaviour. Maybe I could re-spin this patch, and include a more informative comment ? Or, if there's no desire for it, we could just drop it. Either way, I will send further patches for the b53 driver, and include more informative comments. Thanks Alex On Tue, Feb 17, 2015 at 3:15 PM, Jonas Gorski <[email protected]> wrote: > On Fri, Feb 13, 2015 at 8:10 PM, Alexandru Ardelean > <[email protected]> wrote: > > From: Helmut Schaa <[email protected]> > > > > Signed-off-by: Helmut Schaa <[email protected]> > > What does it protect from? Is it available on all supported chips? > What are the use cases of this? Please explain what this bit does and > why we want to (un)set it. > > > Jonas >
_______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
