* [Bluez-devel] Bluez for Motorola EZX mobile phones
@ 2006-03-13 14:14 Florian Echtler
2006-03-13 14:40 ` Kosta Welke
0 siblings, 1 reply; 3+ messages in thread
From: Florian Echtler @ 2006-03-13 14:14 UTC (permalink / raw)
To: bluez-devel
Hi everybody,
there already was a thread a while ago about BlueZ on the Motorola EZX
phones, and in the motorolafans.com forum, one can download a binary
package containing the modules. However, I wanted a) to look at the
source code and b) to have the newest BlueZ modules available, so I
backported the modules from 2.4.31-mh1 to the custom Motorola kernel,
which is based on 2.4.20.
My question is now what to do with the patch. I don't think it would
make sense to integrate it into the main Bluez tree, would it? Perhaps
it would be best to create a separate patch against the Motorola custom
kernel tree? (There are some nasty little hacks involved so that the
kernel itself doesn't have to be recompiled, which could only be updated
by flashing the phone - that's a big "DON'T" for me :-)
Yours, Florian
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Bluez-devel] Bluez for Motorola EZX mobile phones
2006-03-13 14:14 [Bluez-devel] Bluez for Motorola EZX mobile phones Florian Echtler
@ 2006-03-13 14:40 ` Kosta Welke
2006-03-13 18:11 ` Florian Echtler
0 siblings, 1 reply; 3+ messages in thread
From: Kosta Welke @ 2006-03-13 14:40 UTC (permalink / raw)
To: bluez-devel
Florian Echtler wrote:
> I
> backported the modules from 2.4.31-mh1 to the custom Motorola kernel,
> which is based on 2.4.20.
> My question is now what to do with the patch.
Could you send it to openezx.org?
Kosta
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Bluez-devel] Bluez for Motorola EZX mobile phones
2006-03-13 14:40 ` Kosta Welke
@ 2006-03-13 18:11 ` Florian Echtler
0 siblings, 0 replies; 3+ messages in thread
From: Florian Echtler @ 2006-03-13 18:11 UTC (permalink / raw)
To: bluez-devel
[-- Attachment #1: Type: text/plain, Size: 521 bytes --]
> > backported the modules from 2.4.31-mh1 to the custom Motorola kernel,
> > which is based on 2.4.20.
> > My question is now what to do with the patch.
> Could you send it to openezx.org?
I will, as soon as it's finished.
I noticed there's a bug in rfcomm left:
The newest BlueZ modules use a function tty_wakeup() that isn't present
in the 2.4.20 tree. Does anyone have an idea how to replace that
function with one that is available in the old kernel? Maybe just
wake_up_interruptible?
Yours, Florian
[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 191 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2006-03-13 18:11 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-03-13 14:14 [Bluez-devel] Bluez for Motorola EZX mobile phones Florian Echtler
2006-03-13 14:40 ` Kosta Welke
2006-03-13 18:11 ` Florian Echtler
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).