Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: acr@acroberts.com
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Windows Port
Date: Tue, 27 Jan 2004 15:25:52 +0100	[thread overview]
Message-ID: <1075213551.12766.22.camel@pegasus> (raw)
In-Reply-To: <46161.80.63.28.114.1075214415.squirrel@acroberts.com>

Hi Antony,

> Thanks for the answer. I don't see any reason why BlueZ can't be
> implemented on Windows. Obviously the hardware drivers will have to be
> completely rewritten, but surely the tricky stuff (L2CAP and RFCOMM) can
> be used in a Windows environment?

you have to rewrite all kernel stuff including L2CAP and RFCOMM. Take a
look at the source code of the kernel (for example net/bluetooth/) and
you will see that the code is full of Linux specific API calls. It is
much more easier to write a Bluetooth stack from scratch than porting
BlueZ to the Windows platform.

Regards

Marcel




-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  parent reply	other threads:[~2004-01-27 14:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-27  8:54 [Bluez-devel] Windows Port Antony C. Roberts
2004-01-27 13:59 ` Marcel Holtmann
     [not found]   ` <46161.80.63.28.114.1075214415.squirrel@acroberts.com>
2004-01-27 14:25     ` Marcel Holtmann [this message]
     [not found]       ` <46892.80.63.28.114.1075215434.squirrel@acroberts.com>
     [not found]         ` <48760.80.63.28.114.1075219113.squirrel@acroberts.com>
2004-01-27 16:38           ` Marcel Holtmann
  -- strict thread matches above, loose matches on Subject: below --
2004-01-28  7:33 Peter Kjellerstedt
2004-01-28  7:53 ` Marcel Holtmann
2004-01-28  7:58   ` Antony C. Roberts
2004-01-28  8:08     ` Marcel Holtmann
2004-01-28  8:18       ` Antony C. Roberts
2004-01-28 16:22         ` Marcel Holtmann
2004-01-28 19:55           ` Antony C. Roberts

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=1075213551.12766.22.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=acr@acroberts.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