netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Michael Buesch <mbuesch@freenet.de>,
	jgarzik@pobox.com, bcm43xx-dev@lists.berlios.de,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [Bcm43xx-dev] [Fwd: State of the Union: Wireless]
Date: Fri, 06 Jan 2006 13:46:15 +0100	[thread overview]
Message-ID: <43BE6697.3030009@trash.net> (raw)
In-Reply-To: <1136549423.7429.88.camel@localhost>

Marcel Holtmann wrote:

>>I just personally liked the idea of having a device node in /dev for
>>every existing hardware wlan card. Like we have device nodes for
>>other real hardware, too. It felt like a bit of a "unix way" to do
>>this to me. I don't say this is the way to go.
>>If a netlink socket is used (which is possible, for sure), we stay with
>>the old way of having no device node in /dev for networking devices.
>>That is ok. But that is really only an implementation detail (and for sure
>>a matter of taste).
> 
> 
> At the OLS last year, I think the consensus was to use netlink for all
> configuration task. However this was mainly driven by Harald Welte and
> he might be able to talk about the pros and cons of netlink versus a
> character device.

I think the main advantages of netlink over a character device is its
flexible format, which is easily extendable, and multicast capability,
which can be used to broadcast events and configuration changes. Its
also good to have all the net stuff accessible in a uniform way.

  reply	other threads:[~2006-01-06 12:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1136541243.4037.18.camel@localhost>
2006-01-06 11:00 ` [Bcm43xx-dev] [Fwd: State of the Union: Wireless] Michael Buesch
2006-01-06 11:38   ` Marcel Holtmann
2006-01-06 11:45     ` Michael Buesch
2006-01-06 12:10       ` [Bcm43xx-dev] " Marcel Holtmann
2006-01-06 12:46         ` Patrick McHardy [this message]
2006-01-06 18:23           ` Stephen Hemminger
2006-01-06 22:16           ` David Lang
2006-01-06 22:18             ` David S. Miller
2006-01-09 18:24               ` Ingo Oeser
2006-01-06 22:22             ` Patrick McHardy
2006-01-12 14:20           ` Harald Welte
2006-01-06 16:12       ` Feyd
2006-01-06 16:25         ` Johannes Berg
2006-01-06 17:02   ` Ben Greear
     [not found] <5rXDU-5s4-7@gated-at.bofh.it>
     [not found] ` <5rXDU-5s4-5@gated-at.bofh.it>
2006-01-06 22:57   ` Bodo Eggert

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=43BE6697.3030009@trash.net \
    --to=kaber@trash.net \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=mbuesch@freenet.de \
    --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).