public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@osdl.org>
To: Tilman Schmidt <tilman@imap.cc>
Cc: Lee Revell <rlrevell@joe-job.com>, Hansjoerg Lipp <hjlipp@web.de>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/9] isdn4linux: add drivers for Siemens Gigaset ISDN DECT PABX
Date: Mon, 19 Dec 2005 13:30:22 -0800	[thread overview]
Message-ID: <20051219133022.173a8b92@localhost.localdomain> (raw)
In-Reply-To: <43A70882.80106@imap.cc>

On Mon, 19 Dec 2005 20:22:42 +0100
Tilman Schmidt <tilman@imap.cc> wrote:

> On 2005-12-19 18:01, Lee Revell wrote:
> > On Mon, 2005-12-19 at 17:38 +0100, Tilman Schmidt wrote:
> > 
> >>Unfortunately these don't fit our needs, as we are not dealing with a
> >>network device, but with an ISDN device.
> > 
> > Um, isn't that what the N in ISDN stands for?
> 
> While the ISDN is indeed called a network, devices connecting a computer
> to it are nevertheless not commonly referred to as network devices.
> 
> > I guess what you mean is that although ISDN devices are obviously
> > networking devices, the kernel uses a separate subsystem for ISDN?
> 
> There's more to it than that. The notion of a "network" is a rather
> broad one, including such diverse phenomena as Ethernet, ISDN, TV cable
> or even roads or TV stations. The notion of a "network device", on the
> other hand, is a quite specific one, at least in the computer world, and
> it certainly doesn't include ISDN TAs.
> 
> In fact, the operation of an ISDN device is much closer to a modem or
> even an answering machine than to that prototypical network device which
> is the Ethernet card. This is of course the reason why the Linux kernel
> puts them in a subsystem of their own. Making them net_device-s just
> wouldn't work.
> 


My definition is simple. Any device driver that exports a netdevice
interface needs to be reviewed on netdev to make sure the assumptions
about network device semantics are being followed.

-- 
Stephen Hemminger <shemminger@osdl.org>
OSDL http://developer.osdl.org/~shemminger

  reply	other threads:[~2005-12-19 21:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20051212181356.GC15361@hjlipp.my-fqdn.de>
2005-12-19 16:38 ` [PATCH 0/9] isdn4linux: add drivers for Siemens Gigaset ISDN DECT PABX Tilman Schmidt
2005-12-19 17:01   ` Lee Revell
2005-12-19 17:04     ` Arjan van de Ven
2005-12-19 19:22     ` Tilman Schmidt
2005-12-19 21:30       ` Stephen Hemminger [this message]
2005-12-19 21:53         ` Tilman Schmidt
2006-02-11 14:52 Hansjoerg Lipp
2006-02-12 10:29 ` Andrew Morton
  -- strict thread matches above, loose matches on Subject: below --
2005-12-11 18:20 Hansjoerg Lipp
2005-12-12 17:41 ` Stephen Hemminger

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=20051219133022.173a8b92@localhost.localdomain \
    --to=shemminger@osdl.org \
    --cc=hjlipp@web.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rlrevell@joe-job.com \
    --cc=tilman@imap.cc \
    /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