netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: jamal <hadi@cyberus.ca>
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: rtnetlink interface state monitoring problems.
Date: Mon, 21 Oct 2002 19:57:50 +0100	[thread overview]
Message-ID: <24818.1035226670@passion.cambridge.redhat.com> (raw)
In-Reply-To: <Pine.GSO.4.30.0210210852130.17911-100000@shell.cyberus.ca>


hadi@cyberus.ca said:
> I cant see anything on netlink and irda; i am also not very familiar
> with either IrDA or Bluetooth. Regardless,  you dont need to be a net
> device to use netlink. 

IrDA devices are network devices. The core network code sends a RTM_NETLINK 
message when they go up or down. All is well, and once the permission fix 
gets into the kernel I'm using, my irda monitor applet no longer needs to 
poll the state of the interface.

But Bluetooth devices are not network devices, it seems. There exists no 
current mechanism for notifying anyone of state changes. Should we invent a 
new method of notification using netlink, or should Bluetooth interfaces in 
fact be normal network devices just like IrDA devices are?

--
dwmw2

  reply	other threads:[~2002-10-21 18:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-21 11:18 rtnetlink interface state monitoring problems David Woodhouse
2002-10-21 13:02 ` jamal
2002-10-21 18:57   ` David Woodhouse [this message]
2002-10-23  0:59     ` jamal
2002-10-23  1:44       ` Tim Hockin
2002-10-23  3:17         ` jamal
2002-10-23 19:42           ` Maksim (Max) Krasnyanskiy
2002-10-28 12:35             ` jamal
2002-10-23 19:41       ` Maksim (Max) Krasnyanskiy
2002-10-21 13:46 ` James Morris
2002-10-21 13:48   ` James Morris
2002-10-21 17:01     ` David S. Miller
2002-10-24  3:41       ` [PATCH] " James Morris

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=24818.1035226670@passion.cambridge.redhat.com \
    --to=dwmw2@infradead.org \
    --cc=hadi@cyberus.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@oss.sgi.com \
    /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).