From: "durai" <durai@isofttech.com>
To: <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Porting BlueZ on embedded uClinux
Date: Wed, 17 Aug 2005 10:02:55 +0530 [thread overview]
Message-ID: <000201c5a2e4$c1076e20$9301a8c0@DURAI> (raw)
Hi Al,
In uClinux there is no fork, only vfork is available. You have to change
your fork to vfork in uClinux.
Please refer
http://www.ucdot.org/article.pl?sid=03/12/12/0317219&mode=thread.
regards
durai
----- Original Message -----
Subject: Re: [Bluez-devel] Porting BlueZ on embedded uClinux
Date: Wed, 17 Aug 2005 10:28:54 +0800
From: "Al" <Al_chane@issc.com.tw>
Hi, durai:
I port hcid to embedded uClinux (2.4.20). But it has problem to
fork(), fork() return -1. Did you have fork() problem in your embedded
linux?
thanks a lot,
Al
----- Original Message -----
From: "durai" <durai@isofttech.com>
To: <bluez-devel@lists.sourceforge.net>
Sent: Monday, August 15, 2005 3:22 PM
Subject: Re: [Bluez-devel] Porting BlueZ on embedded uClinux
> Hi Al,
> I recently ported bluez stack in a embedded linux running 2.4.18 kernel.
> First I downloaded the MH patch from
> http://www.holtmann.org/linux/kernel/. and
> applied it. Now both statically compiled driver as well as modules are
> working correctly.
> You can also try finding an appropriate patch and patch it with your
> kernel. But what is
> surprising for me is, though your kernel is 2.4.21 and you are not able to
> find the options in
> make menuconfig. I guess something is messed up in your package.
>
> Can you find "hci_usb_init" in your System.map? Is it integrated
> correctly?
> regards
> durai
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2005-08-17 4:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-17 4:32 durai [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-17 5:15 [Bluez-devel] Porting BlueZ on embedded uClinux Al
2005-08-18 5:28 ` durai
2005-08-18 9:42 ` durai
2005-08-17 2:28 Al
2005-08-15 10:01 Al
2005-08-15 10:16 ` Peter Wippich
2005-08-15 6:13 Al
2005-08-15 7:22 ` durai
2005-08-15 5:10 Al
2005-08-15 5:38 ` Paul Webster
2005-08-15 2:44 Al
2005-08-12 10:02 Al
2005-08-12 12:34 ` Peter Wippich
2005-08-12 9:25 Al
2005-08-12 9:38 ` Peter Wippich
2005-08-12 8:39 Al
2005-08-12 9:01 ` Peter Wippich
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='000201c5a2e4$c1076e20$9301a8c0@DURAI' \
--to=durai@isofttech.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