From: Pete Zaitcev <zaitcev@redhat.com>
To: David Brownell <david-b@pacbell.net>
Cc: linux-kernel@vger.kernel.org, greg@kroah.com,
linux-usb-devel@lists.sourceforge.net
Subject: Re: usbmon, usb core, ARM
Date: Wed, 19 Jan 2005 07:42:08 -0800 [thread overview]
Message-ID: <20050119074208.3bfa6458@localhost.localdomain> (raw)
In-Reply-To: <200501182214.25273.david-b@pacbell.net>
On Tue, 18 Jan 2005 22:14:24 -0800, David Brownell <david-b@pacbell.net> wrote:
> > > Also, I don't like the idea of scattering knowledge all over the place
> > > that the root hub is always given address 1 ...
>
> which you didn't address yet.
Yes, I have to look why you do not like using the pipe. Relying on pipe makes
tests dependant on URB only. No references to bus or HCD, therefore no
extra refcounts or worries about oopses. Also, HC drivers zero out the
urb->dev in giveback sequence which is a royal pain when trying to identify
a root hub. I thought about adding an extra flag like URB_ROOT_HUB to split
this use from the abuse of URB_NO_TRANSFER_DMA_MAP, but pipe looks better
all around. If you look at it from the angle I did, it stands to reason
that excessive encapsulation only masks _why_ it was safer, e.g. if one sees
something like urb_is_root_hub(urb), one must look up the implementation
to know if it uses urb->dev or not. Relying on address 1 without any symbolic
constant is obviously a bad idea though, I'll fix that.
-- Pete
next prev parent reply other threads:[~2005-01-19 15:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-19 5:20 usbmon, usb core, ARM Pete Zaitcev
2005-01-19 6:14 ` David Brownell
2005-01-19 15:42 ` Pete Zaitcev [this message]
2005-01-19 15:54 ` Oliver Neukum
2005-01-19 17:08 ` David Brownell
2005-01-20 19:35 ` Pete Zaitcev
2005-01-21 6:28 ` David Brownell
2005-01-22 8:12 ` Pete Zaitcev
2005-01-23 23:34 ` [linux-usb-devel] " David Brownell
2005-01-24 1:17 ` Pete Zaitcev
2005-01-24 2:08 ` David Brownell
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=20050119074208.3bfa6458@localhost.localdomain \
--to=zaitcev@redhat.com \
--cc=david-b@pacbell.net \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
/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