From: Marcel Holtmann <marcel@holtmann.org>
To: Ian Kumlien <pomac@vapor.com>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [2.6.8 ->] Problems, hci_usb dosn't work.
Date: Wed, 22 Sep 2004 20:29:04 +0200 [thread overview]
Message-ID: <1095877744.6223.88.camel@pegasus> (raw)
In-Reply-To: <1095877600.3211.15.camel@big>
Hi Ian,
> The problem is, this computer doesn't have a usb 1.1 port.
> But it should basically fallback, and afair it worked with a cable
> direct to the computer, i haven't tested that since... because i need
> the hubs.
>
> But if it indeed is a usb 1.1 vs 2.0 problem then it has to be
> something broken in the kernel... Anyone else using this with usb 2.0?
this problem was reported two or three times, but I am unable to
reproduce it with my USB 2.0 host controllers.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-09-22 18:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-21 22:50 [Bluez-devel] [2.6.8 ->] Problems, hci_usb dosn't work Ian Kumlien
2004-09-22 8:47 ` Marcel Holtmann
2004-09-22 18:26 ` Ian Kumlien
2004-09-22 18:29 ` Marcel Holtmann [this message]
2004-09-22 18:32 ` Ian Kumlien
2004-09-22 18:38 ` Marcel Holtmann
2004-09-22 18:49 ` Ian Kumlien
2004-09-22 18:52 ` Marcel Holtmann
2004-09-22 19:20 ` Ian Kumlien
2004-09-22 19:26 ` Marcel Holtmann
2004-09-22 21:51 ` Ian Kumlien
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=1095877744.6223.88.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=pomac@vapor.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