public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Christoph Torens" <c.torens@web.de>
To: "bluez-users@lists.sourceforge.net" <bluez-users@lists.sourceforge.net>
Subject: [Bluez-users] bluetooth pand and isp116x problems partly solved
Date: Mon, 04 Oct 2004 03:52:17 +0200	[thread overview]
Message-ID: <opsfbotflbeocfdv@debian> (raw)

hello List,

i wrote to the list a long time ago, because I had the problem, that a
pand connection didn't work. And after trying this the usb dongle
produced only timeouts.

You pointed me to the usb host controller that could be the
problem and of course you ware right.

I found out that the host controller driver needed a 4 msec deelay in a
function hc_submit_urb to work properly.
But sadly I don't understand WHY this helps. I believe my solution is
only a cure for the symptom not for the cause.
And it's not the right playe for a delay in this function, I think.

What I would like to know now:
Why is pand (or dund or ppp over rfcomm) so critical?
l2ping gave no errors, and also other usb tasks were ok.


-- 
regards,
Christoph


-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

             reply	other threads:[~2004-10-04  1:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-04  1:52 Christoph Torens [this message]
2004-10-04  9:28 ` [Bluez-users] bluetooth pand and isp116x problems partly solved Marcel Holtmann

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=opsfbotflbeocfdv@debian \
    --to=c.torens@web.de \
    --cc=bluez-users@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