From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Do I need to patch 2.6 kernel?
Date: Mon, 23 Jul 2007 14:06:23 +0200 [thread overview]
Message-ID: <1185192383.7111.37.camel@violet> (raw)
In-Reply-To: <EJENLMBEOLKAMCJFBFMDMEDFCAAA.leiyu@kcoe.cn>
Hi Leiyu,
> I port bluez to embedded system, there are some patches for 2.4 kernel in www.bluez.org, but that I use the kernel version is 2.6.14, Do I need patch the kernel, if yes , where I should download from?
> thanks very much
start using a 2.6.22 kernel or later. Your kernel is already ancient and
a 2.4 is even more ancient.
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2007-07-23 12:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-23 11:48 [Bluez-users] Do I need to patch 2.6 kernel? leiyu
2007-07-23 12:06 ` Marcel Holtmann [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=1185192383.7111.37.camel@violet \
--to=marcel@holtmann.org \
--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