Re: [Linux-ATM-General] Solos driver weirdness in bridged mode

[Philip P. <phi...@re...>]

On 3/22/11 12:55 PM, chas williams - CONTRACTOR wrote:
> On Tue, 22 Mar 2011 12:36:25 -0700
> Philip Prindeville<phi...@re...>  wrote:
>
>> So for users with the older FPGA firmware, that doesn't see the carrier state change messages, how should we handle this?
> just update the carrier/signal status of the adapter.  initially
> configure that state to SIG_UNKNOWN.  the logic to determine the value
> of the carrier sysfs value will get the rest right.

Ok, but I thought we had agreed to change the initial state to LOST instead of UNKNOWN?

BTW:  Is there an easy way to detect which version of firmware we're talking to?  Or do we need to add a module parameter?


>> My inclination is to think that tearing down the circuits was never the correct behavior...
> i dont believe it is correct either.  no other driver does this because
> the carrier status shouldnt be used to reset any of the protocols
> running over a pvc or svc.  signalling used a seperate channel (0.5) to
> keep track of whether or not you are alive and well (sscop).  i gather
> that pvc circuits used ppp to keep track of link state.  so the carrier
> state bouncing briefly shouldnt bother them really.

Yeah, that sounds right to me too.

-Philip