From: maha k <maha.cedt@gmail.com>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Help for cross compilation of BlueZ
Date: Mon, 21 Mar 2005 16:49:52 +0530 [thread overview]
Message-ID: <14397664050321031963ce0576@mail.gmail.com> (raw)
Hi,
>I have to add bluetooth functionality to my MIPS based hardware
> platform. Hardware has montavista linux kernel 2.4.20 without rfcomm
> and bnep support. I need help regarding compilation of rfcomm,bnep and
> BlueZ. For cross compilation whether i have to use cross compilers or
> native gcc which is available in file system?
>I am not the right person to ask about cross-compiling stuff, but I
>think you need to rebuild your whole kernel. Apply patch-2.4.20-mh18 to
>get RFCOMM and BNEP support. However be aware of that most of the fixes
>and future enhancements are only present in the 2.6 kernel series.
I am able to add RFCOMM support. Giving problem for BNEP and HIDP support.
I can't upgrade kernel version since it is a montavista custom linux
kernel for specific board.
Can any one help me out in cross compilation of BlueZ utils and libs
for MIPS flatform?
Regards
--
Maha
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next reply other threads:[~2005-03-21 11:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-21 11:19 maha k [this message]
2005-03-21 11:34 ` [Bluez-users] Help for cross compilation of BlueZ Marcel Holtmann
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=14397664050321031963ce0576@mail.gmail.com \
--to=maha.cedt@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.