All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Trudel <mtrudel@gmx.ch>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] BlueZ on ETRAX 100LX devboard 82+
Date: Tue, 14 Jun 2005 20:26:17 +0200	[thread overview]
Message-ID: <42AF2149.1030701@gmx.ch> (raw)
In-Reply-To: <20050614140459.79023.qmail@web52802.mail.yahoo.com>

> My question is this: instead of creating a device
> using ioctl(), do you know how to assign this already
> created device to dev in the above if statement?

no. I never worked with such devices.

> The device resides in the /dev directory.  This is a
> problem I will face even if I write step(6)
> separately

actually no. There's no need for a device, use a socket.

> becuase the question of using an already
> created device will still come up.

what for? not for bluez...


regards
Marco


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2005-06-14 18:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-09 11:12 [Bluez-users] BlueZ on ETRAX 100LX devboard 82+ Naved Aziz
2005-06-09 11:43 ` Marco Trudel
2005-06-09 13:57   ` Naved Aziz
2005-06-09 15:26     ` Marco Trudel
2005-06-10  5:06       ` Naved Aziz
2005-06-12  9:51         ` Marco Trudel
2005-06-14 14:04           ` Naved Aziz
2005-06-14 18:26             ` Marco Trudel [this message]
2005-06-26 10:40               ` Naved Aziz
2005-06-26 13:36                 ` Naved Aziz
2005-06-13  8:32         ` Erwin Authried

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=42AF2149.1030701@gmx.ch \
    --to=mtrudel@gmx.ch \
    --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.