From: Zsolt Barat <zsolt@softmonsters.com>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] [PATCH] fix for kernel flow control patch mh7
Date: Thu, 07 Dec 2006 13:13:57 +0100 [thread overview]
Message-ID: <45780585.5050502@softmonsters.com> (raw)
In-Reply-To: <4577529E.7000304@softmonsters.com>
i tried also 2.6.18-mh8 now. it apllies cleanly and works. the order i
applied the patches where:
for gentoo:
4410-suspend2-2.2.8-for-2.6.18.patch
4411-x86_64-nosave.patch
patch-2.6.18-mh8
bluez-sco-flowcontrol-mh7.patch (without fix)
the two gentoo patches forms the suspend2-source. if someone wants to
build a non-suspen2/non-gentoo kernel he has to apply the two latest
ones naturally.
this would be the safest way to apply the flow-controll patch i think,
since it implies the mh-patch-set.
regards
zsolt
Zsolt Barat schrieb:
> Brad Midgley schrieb:
>> Zsolt
>>
>>> attached is a trivially fixed version of the flow-control-patch mh7,
>>> which could be found on
>>> http://bluetooth-alsa.sf.net/bluez-sco-flowcontrol-mh7.patch
>>> to work with gentoo-suspend2-sources and linux-2.6.18-vanilla.
>>> i don't know which kernel-version it supposed to be apply.
>>> would be nice to mention it on the website somewhere.
>> I've linked to Fabien's latest submission and linked to the bluez patch
>> page. Fabien's patch is against -mh7 but I will try it against -mh8 to
>> se if there are any conflicts.
> ah, ok now i understand. mh is an extra patch set. i thought mh is
> already fabians private patch set.
> then all is probably wrong.
> nevertheless with the small fix above the flow-control patch applies
> also against 2.6.18 with suspend2-patches and even to 2.6.18-vanilla.
> if it has any use it's another question.
> what i can say for sure is that with the flow-control-patch sco and the
> alsa-plugin layer works. i had to figure out to do resampling and
> channel-routing right to get it work. but it was after i applied the patch.
> btw. the setup with the kernel module is much easier in this regard.
>
>> It would be good to know if suspend2 patches complicate things. I don't
>> use suspend2 myself.
> no, no complications so far. i think suspend2 doesn't touch this areas
> where flow-control is involved. i have the kernel running on my notebook
> since i posted the patch. suspend+resume works fine.
>
> regards
>
> zsolt
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2006-12-07 12:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-05 10:59 [Bluez-users] [PATCH] fix for kernel flow control patch mh7 Zsolt Barat
2006-12-06 22:00 ` Brad Midgley
2006-12-06 23:30 ` Zsolt Barat
2006-12-07 12:13 ` Zsolt Barat [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=45780585.5050502@softmonsters.com \
--to=zsolt@softmonsters.com \
--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