From: Jean Tourrilhes <jt@bougret.hpl.hp.com>
To: Greg KH <greg@wirex.com>, Dag Brattli <dag@brattli.net>,
torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: [patch] patch-2.4.2-irda1 (irda-usb)
Date: Tue, 27 Feb 2001 18:41:09 -0800 [thread overview]
Message-ID: <20010227184109.B6898@bougret.hpl.hp.com> (raw)
In-Reply-To: <20010227093329.A10482@wirex.com> <200102272032.UAA74232@tepid.osl.fast.no> <20010227135810.E910@wirex.com>
In-Reply-To: <20010227135810.E910@wirex.com>; from greg@wirex.com on Tue, Feb 27, 2001 at 01:58:11PM -0800
On Tue, Feb 27, 2001 at 01:58:11PM -0800, Greg KH wrote:
> On Tue, Feb 27, 2001 at 08:32:28PM +0000, Dag Brattli wrote:
> > > I'd recommend that this file be in the /drivers/usb directory, much like
> > > almost all other USB drivers are.
> >
> > Yes, but do we want to spread the IrDA code around? The same argument
> > applies to IrDA device drivers!?
>
> I agree, and am not saying that it _has_ to be there. Just a
> suggestion, and if you're comfortable with it in the irda directory,
> that's fine.
>
> thanks,
>
> greg k-h
Hi,
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...
Have fun...
Jean
next prev parent reply other threads:[~2001-02-28 2:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-27 8:29 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 [this message]
2001-02-28 5:40 ` Greg KH
2001-02-28 3:43 Dunlap, Randy
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=20010227184109.B6898@bougret.hpl.hp.com \
--to=jt@bougret.hpl.hp.com \
--cc=dag@brattli.net \
--cc=greg@wirex.com \
--cc=jt@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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
all inboxes | Powered by JetHome®