From: Krzysztof Halasa <khc@pm.waw.pl>
To: <netdev@vger.kernel.org>
Subject: WAN device configuration, again...
Date: Wed, 28 Oct 2009 14:28:51 +0100 [thread overview]
Message-ID: <m3d447hcks.fsf@intrepid.localdomain> (raw)
Hi,
I'm currently at final stages of "producing" two WAN drivers and there
is one thing to solve: they have really complex options. It's no longer
a V.35 with ca. 4 clock modes, a clock rate and few encodings etc. They
need many options unique to each driver/board. I think I need a more
capable interface to configure the devices than the current ioctl-based
one.
I think of something:
- using netlink or similar interface
- with potentially unlimited "payload" size (data may be transfered in
smaller packets)
- the "command" and "response" should be variable-length ASCII-based,
instead of fixed structures. This way I don't have to duplicate all
option handling in userspace, only the specific driver has to know
about them.
Comments? Perhaps there is already an example?
Should I use something else?
I also thought about using /sys read/write calls, but I'm not sure it's
a good idea.
--
Krzysztof Halasa
next reply other threads:[~2009-10-28 13:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-28 13:28 Krzysztof Halasa [this message]
2009-10-28 16:03 ` WAN device configuration, again Dan Williams
2009-10-29 14:48 ` Krzysztof Halasa
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=m3d447hcks.fsf@intrepid.localdomain \
--to=khc@pm.waw.pl \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).