Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 15 Oct 2013 16:39:00 +0000
From:      "Sam Fourman Jr." <sfourman@gmail.com>
To:        Kris Moore <kris@pcbsd.org>
Cc:        freebsd-wireless@freebsd.org
Subject:   Re: Wireless API
Message-ID:  <CAOFF%2BZ3zWR1tJkOvdBE-g27Bm7a3JrG44EhMAVm2AOKxueHvBA@mail.gmail.com>
In-Reply-To: <525D6CBA.4010101@pcbsd.org>
References:  <525B2802.5050904@gmail.com> <CAJ-Vmomu3nq9tckFC=x5f95DpVXNG5jxawToQfknvx3zWszCfQ@mail.gmail.com> <CADRZFmrMsLYT-txAkJuEg2UW%2Bd6nQ0N%2BJv=je8Q=tVk-iq8Hyg@mail.gmail.com> <CAJ-Vmo=7To-vO=-EcueueT6TmBdU5VtUXGaWVwX8UOEabKB4-A@mail.gmail.com> <CADRZFmpxgBSpCor1ntPwE%2B-W5z58mj=vL-6SBDLWcyx4Czh0VA@mail.gmail.com> <CAJ-VmontQCyRSht0r2wo-fU92%2BgpdnOUvTGoh6t9qv20rTjSCA@mail.gmail.com> <CADRZFmpcQM3BcP3adPROk2goLU3Kq4PLyqrOv2ctDTWZWqBmWQ@mail.gmail.com> <CAJ-VmomHjGUob1enQ4f6K=SrTDQXjmqX_152tar6MvB8Uv7CiQ@mail.gmail.com> <525D6CBA.4010101@pcbsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Oct 15, 2013 12:26 PM, "Kris Moore" <kris@pcbsd.org> wrote:
>
> On 10/15/2013 11:15, Adrian Chadd wrote:
> > Well, up until now the interactions have all been via the ioctl API or
the
> > ifconfig command. Both are cumbersome.
> >
> > There's a decent amount of library code in ifconfig for wifi and
regulatory
> > related stuff. It could be broken out into a public library..
> >
> > -adrian
> >
>
> Yea, our PC-BSD network utils are using a mixture of C ioctl and
> "ifconfig" parsing, +1 for a public library API at some point ;)

This really is somthing that should be brought to the FreeBSD foundations
attetion.
As an example the network manager in Gnome hasn't been ported for years,
and I belive the largest part of the reason is lack of an API.

The importance of this really can't be underestimated.
Is there a formal way, to propose a project to the FreeBSD foundation?

Sam Fourman Jr.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOFF%2BZ3zWR1tJkOvdBE-g27Bm7a3JrG44EhMAVm2AOKxueHvBA>