From: Brad Midgley <bmidgley@xmission.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Unable to set number of SCO buffers : please upgrade your Kernel !
Date: Tue, 24 Apr 2007 07:45:57 -0600 [thread overview]
Message-ID: <462E0A15.1070707@xmission.com> (raw)
In-Reply-To: <7.0.1.0.2.20070423075933.03d4a650@dubai.oilfield.slb.com>
John
> The earliest patch in the cvs is v2.0 for 2.6.18-mh7 - given that I
> have 2.6.12 (DSL-N is like Knoppix, you cannot easily update the
> kernel), is there a patch archive somewhere with a patch closer to my
> kernel or do I need to try and apply the patch "manually"?
Fabien may have submitted an early patch that is closer to your kernel
but rather than backport or dig in the archives I suggest you consider
trying a newer kernel.
Brad
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-04-24 13:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-22 6:52 [Bluez-devel] Unable to set number of SCO buffers : please upgrade your Kernel ! John Frankish
2007-04-22 16:50 ` Brad Midgley
2007-04-23 4:07 ` John Frankish
2007-04-24 13:45 ` Brad Midgley [this message]
2007-04-25 5:56 ` John Frankish
-- strict thread matches above, loose matches on Subject: below --
2007-04-15 9:57 Brandon Philips
2007-04-15 18:34 ` Brad Midgley
2007-04-16 7:35 ` Brandon Philips
2007-04-24 18:48 ` Marc Haber
2007-04-29 12:34 ` Klaus
2007-04-29 16:17 ` Klaus
2007-04-29 16:18 ` Brad Midgley
2007-04-29 20:58 ` Klaus
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=462E0A15.1070707@xmission.com \
--to=bmidgley@xmission.com \
--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