From: Gary Thomas <gthomas@redhat.com>
To: eCos Discussion <ecos-discuss@sourceware.cygnus.com>
Subject: [ECOS] RE: [aeb] Bluetooth on aeb/arm and eCos
Date: Fri, 07 Jul 2000 07:26:00 -0000 [thread overview]
Message-ID: <XFMail.000707082559.gthomas@redhat.com> (raw)
In-Reply-To: <1781-144@arm.com>
Firtly, the best place to ask these sorts of questions are on the eCos
discussion lists. I've copied my response appropriately.
On 07-Jul-00 Andreas.Karlsson@combitechsystems.com wrote:
>
> I'm going to run Bluetooth on top of eCos.
This will be a great addition to eCos. Do you plan to donate your work
back to us [say "yes"]?
> A have an open source Bluetooth stack from www.developer.axis.com/ but it is
> mapped to Linux.
> Is there anyone that have experiences from this kind of project?
> Any hints?
> My first compilation can't find files like tty.h, malloc.h, kernel.h,
> termios.h, module.h, sched.h, delay.h and so on. Most of them could be found
> in either the cygwin or the ecos directory. Will these files do good?
> Some files are found in several places, any idea which will be best?
> My first thought was that this won't be that hard but maybe it will...
>
The eCos I/O model is somewhat different from Linux [to say the least]. You'll
need to make some significant changes to get this to work on eCos.
I'd suggest that you use the Linux driver as a logical framework and then build
the eCos version based on the OpenBSD network stack we already have in place.
One thing to note: the Axis Bluetooth stack is GPL which is slightly incompatible
with the RHEPL. As such, be careful of anything you import if you wish to make
it generally available to the eCos public.
parent reply other threads:[~2000-07-07 7:26 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1781-144@arm.com>]
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=XFMail.000707082559.gthomas@redhat.com \
--to=gthomas@redhat.com \
--cc=ecos-discuss@sourceware.cygnus.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).