Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Re: Re: Re: Re: Re: hciattach problem
Date: Sun, 06 Feb 2005 19:35:56 +0100	[thread overview]
Message-ID: <1107714956.12834.72.camel@pegasus> (raw)
In-Reply-To: <42065FAA.8030309@web.de>

Hi Andreas,

> >no. The libs and utils will not change the behaviour of your kernel. I
> >think you had an experimental patch in one of the kernels that causes
> >your problem. May you wanna also check the 2.6.11-rc3 to be sure that
> >everything is fine.
> >
> >  
> I have checked with -mh3, too, and it does also work. I have no 
> experimental patch in my kernel, so I don't know, what the problem was. 
> But I think, I have done something wrong in the config or so. Thanks for 
> your help.

actually I asked you to test 2.6.11-rc3 and not the -mh3. I want to be
sure that the latest testing kernel before the final 2.6.11 has no
problems with it. So grab 2.6.11-rc3-bk3 and test it please.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2005-02-06 18:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-06 18:19 [Bluez-devel] Re: Re: Re: Re: Re: hciattach problem Andreas Millinger
2005-02-06 18:35 ` Marcel Holtmann [this message]
2005-02-07  8:58   ` [Bluez-devel] documentation question Jack Jia
2005-02-07 11:22     ` Marcel Holtmann
2005-02-08  9:14       ` Jack Jia
2005-02-08 10:01         ` Marcel Holtmann
2005-02-08 11:25           ` Chen Bin

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=1107714956.12834.72.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-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