All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Steffen Larsen" <zool@zool.dk>
To: <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] piconet..
Date: Mon, 13 Dec 2004 10:48:15 +0100	[thread overview]
Message-ID: <018c01c4e0f8$de417700$6401000a@zool> (raw)
In-Reply-To: 00b001c4dfa9$f3bc0870$6401000a@zool


HI Marcel and other!,

I found out what I did wrong. All my sockets and fork()'ing just worked
fine. My problem was that I tried to make:


----- Original Message -----
From: "Steffen Larsen" <zool@zool.dk>
To: <bluez-devel@lists.sourceforge.net>
Sent: Saturday, December 11, 2004 6:50 PM
Subject: Re: [Bluez-devel] piconet..


> Hi Marcel,
>
> > > I got the two others:
> > >
> > >  hci0: Type: USB
> > > BD Address: 00:01:53:00:14:EE ACL MTU: 192:8 SCO MTU: 64:8
> > > UP RUNNING PSCAN ISCAN
> > > RX bytes:81 acl:0 sco:0 events:10 errors:0
> > > TX bytes:39 acl:0 sco:0 commands:10 errors:0
> > > Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
> > > Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
> > > Link policy:
> > > Link mode: SLAVE ACCEPT
> > > Name: 'knoglen'
> > > Class: 0x000000
> > > Service Classes: Unspecified
> > > Device Class: Miscellaneous,
> > > HCI Ver: 1.1 (0x1) HCI Rev: 0x20d LMP Ver: 1.1 (0x1) LMP Subver: 0x20d
> > > Manufacturer: Cambridge Silicon Radio (10)
> > >
> > > hci0: Type: USB
> > > BD Address: 00:01:53:00:0D:B5 ACL MTU: 192:8 SCO MTU: 64:8
> > > UP RUNNING PSCAN ISCAN
> > > RX bytes:87 acl:0 sco:0 events:11 errors:0
> > > TX bytes:39 acl:0 sco:0 commands:10 errors:0
> > > Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
> > > Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
> > > Link policy:
> > > Link mode: SLAVE ACCEPT
> > > Name: 'JESPER'
> > > Class: 0x000000
> > > Service Classes: Unspecified
> > > Device Class: Miscellaneous,
> > > HCI Ver: 1.1 (0x1) HCI Rev: 0x20d LMP Ver: 1.1 (0x1) LMP Subver: 0x20d
> > > Manufacturer: Cambridge Silicon Radio (10)
> >
> > these two are HCI 16.4 and so there should be no problem. See my CSR
> > page why it is good to have HCI 16.x at least.
> >
> > > > so far so good, but check with "hciconfig hci0 revision" for the
> > > > firmware version. This one is too old. It should be HCI 16.4 or
newer,
> > > > but if this is a DBT-120 Rev. B3 you might have a chance to update
it.
> > >
> > > Well. It is the B3 revision, so I would be able to do that. :-)
> >
> > I suppose you do that (at your own risk of course).
> >
> > > Hmm.. This dosn't really answer my question. I am using fork()., and
> would
> > > like to get my application to work. I tried to compare it towards the
> > > l2test, but couldn't see that much difference. And the l2test works
with
> the
> > > same dongles; connecting two clients against one server. Can you point
> > > somewhere in my code, where I should do some changes, so it could
work??
> >
> > Getting the fork stuff right is not very easy. You must carefully think
> > about what file descriptors to close at what time and in what process. I
> > am not going to check your code for such mistakes, because it will take
> > me too much time and the other reason is that it is C++ and not C.
>
> I understand. I have been spending alot of time in it my self. I will look
> deeper into the socket, and which of them that have been closed and at
which
> time... But I think I have checked this a million times.. But I will try
> again! :-)
>
> > Update the dongle or try to swap the pre HCI 16.4 one. The master option
> > can help, but you must choose the master device carefully.
>
> Yes I can try to swap the devices. You mention that the master device
should
> be carefully choosen. I what way?
> I have just assumed that my server should be the master, and thats that.
> What should I taken in to consideration?
>
> -Once again thanks for all the quick answers! :-)
>
> /Steffen Larsen
>
>
>
> -------------------------------------------------------
> 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://productguide.itmanagersjournal.com/
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>



-------------------------------------------------------
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://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2004-12-13  9:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-11 10:20 [Bluez-devel] piconet Steffen Larsen
2004-12-11 11:28 ` Marcel Holtmann
2004-12-11 11:00   ` Steffen Larsen
2004-12-11 12:10     ` Marcel Holtmann
2004-12-11 12:10       ` Steffen Larsen
2004-12-11 15:33         ` Steffen Larsen
2004-12-11 16:44           ` Marcel Holtmann
2004-12-11 16:29             ` Steffen Larsen
2004-12-11 17:37               ` Marcel Holtmann
2004-12-11 17:50                 ` Steffen Larsen
2004-12-13  9:48                   ` Steffen Larsen [this message]
2004-12-13  9:54                     ` Steffen Larsen
2004-12-13 11:05                       ` 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='018c01c4e0f8$de417700$6401000a@zool' \
    --to=zool@zool.dk \
    --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 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.