Re: BFS for the power kernel
 

No problem - glad that i could help.

I'm not kernel specialist in any case, so this time i may be wrong - but as far as i know bleeding edge wifi modules can't be distributed as standalone package - that's why it is now in kernel-power v47. When modules are present, then indeed - You can just install them and load/unload as You wish. Sorry for any technical mistakes I'm probably writing here - the point is that this is 1st time someone write that using bleeding-edge doesn't need any kernel-side part.

Also, if i remember correctly, lxp created patches to allow quick integration with other kernels.

If bfs-kernel is developed such way that it already got code from kp47 - i.e kernel-side things need to use bleeding-edge wifi drivers, then ignore this post ;)

Re: BFS for the power kernel
 

You can distribute them as a standalone, although of course you need a script to then insert them or disable them. However, this has its uses should the bleeding-edge ones fail or cause issues then you can't revert to the standard ones if they are bundled with the kernel.

Re: BFS for the power kernel
 

I can say that without a shadow of a doubt it is the cause of the problems I have because I built a modified v47 without that patch and it fixed my problem, I can't speak for anyone else's problems though. I suppose the issue is do more people need bluetooth mice support than have problems with bluetooth audio because of the patch?

Re: BFS for the power kernel
 

Retsaw, if You got no problems using kp46, that this is NOT source of errors- cause path is exact same as in kp46. I'm not saying that definitely this path cause no problems. Ho ever, I agree with freemangordon, that this may be similar case to both CSSU and kp47 beign blamed for A/V problems, that - what was finally discovered - were cause by gstreamer error in ogg-support package.

By the way, freemangordon is developer of on-topic bluetooth path, so we can ask him directly. Anyway, he said in other topic that he would be glad for any info/debug data considering possible relation of his path with Your BT headset problems - on this moment he can't find any relation.

simply said, can't anyone who's experiencing such problems grab new version of BFS kernel with bluetooth path disabled, and then, test if problems are gone?

Re: BFS for the power kernel
 

Who said I didn't have problems with kernel-power v46, I did, I just didn't end up using it for long, so I put off doing a bug report at the time, and consequently forgot about it until v47 came along. And if you read what I just posted, I just said I have a build of v47 with just that one patch removed and it fixed the problem. Please try reading what I write before arguing with me. The "patch", I'm quoting it because it isn't much of a patch it just removes some code from the bluetooth stack, it doesn't add anything, so it isn't surprising that when you remove code that has been put in for a reason that things break. As to the debugging info, Freemangordon didn't tell me specifically what I need to enable to get it, so when I have some spare time and feel like it I'll have a go at working it out for myself. As it is I'm just sharing the information I do know for certain.

Re: BFS for the power kernel
 

Retsaw, I;m not arguing You - just asked, cause 99% times when someone say "kp47 bluetooth broke my bluetooth [whatever]", he got it working nicely with kp46.

also, I'm not quite sure if we even talk about same path, cause i can't imagine how deleting some code would allow so many bluetooth mices to work.

Anyway, instead of complaining that freemangordon didn't provided point-blank directions, I'll contact him and mention about this topic. I'm also interested in clearing things about bluetooth compatibility - even, when this bug doesn't affect me directly. So, please don't disrespect my even small contribution to ensure max possible quality, either or kp47, or bfs-kernel ;)

Re: BFS for the power kernel
 

It seems you're not understanding what I was saying, try taking a little more time to read posts you intend to respond to, and if you don't understand ask for clarification. Then it might not seem like you are disagreeing with my statement, hence you coming across as arguing even if you don't mean to. And yes, I do respect that you are trying to help.

I did not ask anything in this thread, I made a statement of fact

We are talking about the same patch, download the source and have a look for yourself, I didn't understand what the code was doing, so I don't know why removing it made bluetooth mice work, but I could see it was a simple code deletion.

And the bit you took as a complaint about freemangordon not providing step-by-step instructions, wasn't meant as a complaint rather an explanation as to why I haven't investigated further. And I don't need step-by-step instructions, I'm an old-hand when it comes to linux, just something a little less vague than enable debugging in the kernel bluetooth stack when there appears to be no such option to do so. If I had missed something obvious then pointing it out would be fine. Since I didn't get a second response from him, I assumed he wasn't too bothered about this issue, which is fine by me, and I put the problem aside for the moment. I could post a thread asking for assistance if I really wanted it, but I've got a couple of ideas to investigate before saying I need help getting useful debug info, I just haven't got round to trying them.

Re: BFS for the power kernel
 

Guys, I start feeling in position to prove that my sister is not a whore.

@estel The post you mention earlier is in answer to an user which has broken bluetooth car audio (if I remember correctly) after upgrading from KP46 to KP47, that is why it is obvious that bt mice PATCH is not the cause for his problems (as it exists in KP46 too). On the other hand it seems that retsaw really has problems with this patch (at least from his explanations).

@retsaw I would define patch as "modification of source code to fix bug or to bring new functionality". I does not matter if one removes or adds lines of source code ;) . Sometimes it could cause regression. Anyway I will appreciate debug info when you find time to compile KP46 (not KP47) with BT debugging enabled (as we discussed) .

I will stop here, lets not hijack this thread. If anyone think thread "KP46 bt mice patch problem" is needed - it is easy to be opened.

Re: BFS for the power kernel
 

Regarding audio issues and the sched_reset_on_fork patch - child/daughter spawns don't pull high priority and since we no longer have cgroups or omhd working to split up and assign, a process for audio isn't inheriting FIFO or RT scheduling and is taking a back-burner to something else?

Dropping audio I/O to anything other than the highest priority on a phone is just bad news, IMHO.

Re: BFS for the power kernel
 

I've built the newest kernel without the aforementioned patch -- seems to be working fine, but only time will tell.

Only issue I'm having is building the new fcam-drivers as something seems to have changed again.

EDIT: Nevermind. Noticed some changes from Tigerite's recent bfs5 post didn't make it upstream? lxp wl12xx patches not incorporated either?