From: "Dunlap, Randy" <randy.dunlap@intel.com>
To: "'jt@hpl.hp.com'" <jt@hpl.hp.com>, Greg KH <greg@wirex.com>,
Dag Brattli <dag@brattli.net>,
linux-kernel@vger.kernel.org
Subject: RE: [patch] patch-2.4.2-irda1 (irda-usb)
Date: Tue, 27 Feb 2001 19:43:05 -0800 [thread overview]
Message-ID: <D5E932F578EBD111AC3F00A0C96B1E6F07DBE0C9@orsmsx31.jf.intel.com> (raw)
> From: Jean Tourrilhes [mailto:jt@bougret.hpl.hp.com]
>
> First thanks for Dag for bringing me into the conversation. I
> may add my little bit of spice, especially that I was the one pushing
> for having the driver in .../drivers/net/irda.
> By the way, Greg, sorry if I hurt your feeling, I don't want
> to put down any of the great work that has been done on the USB stack.
>
> My feeling is that devices are mostly defined by their higher
> level interface, because this is what is closer to the user.
> If I look at a Pcmcia Ethernet card, I will tend to associate
> more with a PCI Ethernet card rather than a Pcmcia SCSI card. Both
> card have the same high level interface (TCP/IP) even if their low
> level interface is different (Pcmcia, PCI).
> People tend to agree with that, and that's why you have
> directories called drivers/net, drivers/scsi and driver/sound, rather
> that drivers/pci, drivers/isa, drivers/mca and drivers/pcmcia.
>
> If I get an IrDA-USB dongle, the feature that matter the most
> is that it does IrDA, the fact that it connect to my PC via USB is
> rather secondary.
> That's it. I hope it explain some of the rationale and why we
> departed from the usual drivers/usb arrangement. Actually, I think
> that stuffing all USB drivers in drivers/usb is not that great, but
> that's not my call...
That has been discussed & Linus like[ds] it that way.
~Randy
next reply other threads:[~2001-02-28 3:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-28 3:43 Dunlap, Randy [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-27 8:29 [patch] patch-2.4.2-irda1 (irda-usb) Dag Brattli
2001-02-27 17:33 ` Greg KH
2001-02-27 20:32 ` Dag Brattli
2001-02-27 21:58 ` Greg KH
2001-02-28 2:41 ` Jean Tourrilhes
2001-02-28 5:40 ` Greg KH
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=D5E932F578EBD111AC3F00A0C96B1E6F07DBE0C9@orsmsx31.jf.intel.com \
--to=randy.dunlap@intel.com \
--cc=dag@brattli.net \
--cc=greg@wirex.com \
--cc=jt@hpl.hp.com \
--cc=linux-kernel@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).