From: Florian Fainelli <florian@openwrt•org>
To: Philip Prindeville <philipp_subx@redfish-solutions•com>
Cc: netdev@vger•kernel.org
Subject: Re: Using net_devices with ATM/DSL
Date: Mon, 13 Dec 2010 13:50:09 +0100 [thread overview]
Message-ID: <201012131350.10206.florian@openwrt.org> (raw)
In-Reply-To: <4D05C2D3.7010306@redfish-solutions.com>
Hello,
On Monday 13 December 2010 07:53:07 Philip Prindeville wrote:
> I was trying to get this discussion rolling on linux-atm-general but didn't
> have much luck.
>
> I was wondering what the downside to having ATM/DSL interfaces use
> net_devices would be?
I think you would have to add ATM/DSL-specific extensions (ala wext) just to
extend it, specializing an atm_dev would make more sense to me.
>
> Part of the reason for wanting to do this is to have an end-point to
> send/receive netlink messages to, so that the interface can report carrier
> state transitions, bit rates, bit-error rates, SNR, attenuation,
> constellations, transmitter gain, etc.
>
> Seems simple enough.
If you want to be able to report informations from the DSL PHY, I would rather
specialize an interface called, say dsl_phy which has a list of operations for
setting/getting the DSL PHY state, low-level counters ...
The atm stack more or less already supports an ATM PHY with
atmphy_ops, but is in my opinion too limited to query chip-speficic infos.
Once that interface is well defined, adding netlink support to it should be
rather straight forward.
>
> Why not do this?
>
> Thanks,
>
> -Philip
>
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger•kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-12-13 12:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-13 6:53 Using net_devices with ATM/DSL Philip Prindeville
2010-12-13 12:50 ` Florian Fainelli [this message]
2010-12-15 4:36 ` Philip Prindeville
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201012131350.10206.florian@openwrt.org \
--to=florian@openwrt$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=philipp_subx@redfish-solutions$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox