Re: [Linux-ATM-General] Sync status in userspace

[chas w. - C. <ch...@cm...>]

in the kernel yes, but i dont know if there is a userspace mechanism to
watch for this kind of thing.  as mentioned br2684ctl shows you how to
watch for carrier changes in the kernel.

On Mon, 13 Sep 2010 09:05:05 -0700
Philip Prindeville <phi...@re...> wrote:

>   So I can't use rtnetlink RTM_NEWLINK messages to monitor state
> changes?
> 
> 
> On 9/13/10 8:29 AM, chas williams - CONTRACTOR wrote:
> > this patch added event monitoring for the carrier/line status.  it
> > also fixed some assumptions about the carrier state.  carrier is
> > now assumed to be UP (it used to be not well defined) unless the
> > hardware is capable of updating the state.  userspace can determine
> > the carrier status by examining /sys/class/atm/<device
> > instance>/carrier.  we dont have an ioctl or ethtool type interface
> > instance>to get this data.
> >
> > On Mon, 13 Sep 2010 09:30:16 +0200
> > Karl Hiramoto<ka...@hi...>  wrote:
> >
> >>    On 13/09/2010 6:32, Philip Prindeville wrote:
> >>>    I think a few weeks ago I saw a patch fly by on linux-kernel on
> >>> signaling sync status from the DSL driver to an upper layer, with
> >>> the remark that it would be useful to userspace. There's something
> >>> there.
> >>>
> >>> Ciao.
> >>> Vincent.
> >>>
> >>> I'm not on linux-kernel but I'll check gmane... Thanks.
> >>>
> >>> Actually, just checked but couldn't find it.  If you remember who
> >>> wrote it or what the subject was, that would help a lot...
> >>>
> >>>
> >> I wrote the patch.  It should be in this list's archives and the
> >> netdev list at the beginning of july.  The patches are in mainline
> >> now, but only work on br2684 VCs so it passes the LOWER_UP flag.
> >>
> >> The patches are in mainline now see commits
> >> 49d49106fc6cbb48c832aa58e3e6cee8b49d5e8f,
> >> 7313bb8f3dd6e28bcf9c42adfd54a5cf9a4949e0,
> >> 005066122b58f3b350736cc896af46aea2e32d23,  and others for each
> >> device.
> >>
> >> --
> >> Karl
>