From: Felipe Balbi <balbi@xxxxxx> Date: Tue, 6 Jan 2015 11:43:32 -0600 > CPSW completely hangs if we add, and later remove, > VLAN ID #1. What happens is that after removing > VLAN ID #1, no packets will be received by CPSW > rendering network unusable. > > In order to "fix" the issue, we're returning -EINVAL > if anybody tries to add VLAN ID #1. While at that, > also filter out any ID > 4095 because we only have > 12 bits for VLAN IDs. > > Fixes: 3b72c2f (drivers: net:ethernet: cpsw: add support for VLAN) > Cc: <stable@xxxxxxxxxxxxxxx> # v3.9+ > Cc: Mugunthan V N <mugunthanvnm@xxxxxx> > Tested-by: Schuyler Patton <spatton@xxxxxx> > Signed-off-by: Felipe Balbi <balbi@xxxxxx> You can't just unilaterally make one VLAN ID unusable. A better way to handle this situation must be found, and if that means turning off hw VLAN support completely, that's a much better alternative to this. I'm not applying this patch, sorry. -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
