From: Marcel Holtmann <marcel@holtmann.org>
To: Greg KH <greg@kroah.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
BlueZ Mailing List <bluez-devel@lists.sourceforge.net>,
USB development list <linux-usb-devel@lists.sourceforge.net>
Subject: [Bluez-devel] Re: PATCH: (as265) Fix bluetooth driver's wait_for_urb()
Date: Wed, 28 Apr 2004 20:08:53 +0200 [thread overview]
Message-ID: <1083175733.4000.67.camel@pegasus> (raw)
In-Reply-To: <20040428174325.GG32040@kroah.com>
Hi Greg,
> I know. I really hate what the Bluetooth driver does, and it's up to
> them to keep up with the changes in urbs due to them statically
> including a urb in their structures. That is what they agreed to when
> they did this a while ago. They are on their own here...
I know that Max accepted this. So I also have to accept this, but this
doesn't count for the bfusb driver and inserting this hack prevents it
from oopsing on a UHCI controller, too.
> So, Bluetooth developers, have you reconsidered your "need" to put a
> static urb in your structure? Are you convinced yet of the wrongness of
> your ways? Do you want a patch to change your subsystem to follow the
> rest of the kernel with regards to USB?
Right now I don't have enough time to rewrite the hci_usb driver, but it
is on my todo list. Actually the bulk and isoc URB's should only be
started when they are needed. This means when an ACL or SCO link is
really established. However I think we should go back to the discussion
how we can combine an URB with a SKB in a nice way. This would also be
helpful for the bfusb driver.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-04-28 18:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44L0.0404281321520.1238-100000@ida.rowland.org>
2004-04-28 17:43 ` PATCH: (as265) Fix bluetooth driver's wait_for_urb() Greg KH
2004-04-28 18:08 ` Marcel Holtmann [this message]
2004-04-28 18:18 ` Greg KH
2004-04-28 22:05 ` [Bluez-devel] " Marcel Holtmann
2004-04-28 19:13 ` Alan Stern
2004-04-28 20:05 ` [linux-usb-devel] " Oliver Neukum
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=1083175733.4000.67.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=greg@kroah.com \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=stern@rowland.harvard.edu \
/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