public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: 卞磊 <mykofzone@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: Re: bluez kernel patch for 2.6.25
Date: Fri, 6 Mar 2009 10:57:39 +0800	[thread overview]
Message-ID: <a172fe730903051857n2bb80733j6984c9d44b62cbf0@mail.gmail.com> (raw)
In-Reply-To: <1236303372.30602.1.camel@localhost.localdomain>

Hi Marcel,
      I have migrated 2.6.29 BlueZ driver and protocol to 2.6.25. The
oops is caused by hci_sysfs.c. The majar reason is the arguments of
registing sysfs is different between 2.6.25 and 2.6.27 (or 28/29) in
function hci_register_sysfs and hci_conn_add_sysfs. Thanks for your
help.


2009/3/6 Marcel Holtmann <marcel@holtmann.org>:
> Hi,
>
> we don't do top posting on the mailing list. Please respect this and
> follow proper mailing list behavior.
>

I'm sorry for it.

>>      I only charge the bluetooth in my team, and i can't let others
>> migrate their drivers to 2.6.28 or 2.6.29 for me. So, i should proting
>> the lastest bluez drivers and protocol to the current kernel(2.6.25).
>> The bluetooth chipset is stlc2500c. I think the bluez in 2.6.27 is
>> better than 2.6.25, but after porting them to 2.6.25, there's some
>> error such as the listed in the last email. So, i would like to try
>> 2.6.25 first. Thus, is theare a kernel patch for 2.6.25? Thanks.
>
> Sorry, but I don't see how anybody here can help you. If you wanna stick
> with an old kernel that is your choice.
>
> Regards
>
> Marcel
>
>
>

Regards
LeiBian

      reply	other threads:[~2009-03-06  2:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-04  3:53 bluez kernel patch for 2.6.25 卞磊
2009-03-04 21:05 ` Marcel Holtmann
2009-03-05  4:32   ` 卞磊
2009-03-06  1:36     ` Marcel Holtmann
2009-03-06  2:57       ` 卞磊 [this message]

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=a172fe730903051857n2bb80733j6984c9d44b62cbf0@mail.gmail.com \
    --to=mykofzone@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    /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