All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabrizio Guglielmino <guglielmino@infitsrl.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] About l2cap patch to handle multiple connections....
Date: Mon, 31 Jul 2006 12:02:17 +0200	[thread overview]
Message-ID: <44CDD529.6030001@infitsrl.com> (raw)
In-Reply-To: <1154085261.2298.34.camel@localhost>

Hi I'm trying to play with the patch to make it work (as Marcel said it =

hangs my machine).

First I'm trying a simple debug by printing to find where it hangs...

There is a first question about this: various BT_DBG statements that =

print bluetooth address
in string format (using batostr) print them in reverse =

order(00:01:02.... is printed 02:01:00).
My test machine is a powerpc based mac, I've used in user-space the =

ba2str  without problems in same architecture
so I'm confused about this.

An other dubt is about following log :

Jul 31 10:36:39 localhost kernel: [  596.604617] Bluetooth: =

00:00:00:00:00:00 -> 44:53:25:E3:01:00 psm 0x300
Jul 31 10:36:39 localhost kernel: [  596.606752] Bluetooth: =

00:00:00:00:00:00 -> 20:68:2A:2D:09:00 psm 0x300
(address are in reverse order as I said above)

Why psm is 0x300? May be also the psm in reverse order and really it's =

0x003 (RFCOMM) as I would have expected ?

Many thanks
Fabrizio


Marcel Holtmann ha scritto:
> Hi Fabrizio,
>
>   =

>> I'm trying to use the patch to handle multiple l2cap connection, I'm not =

>> a kernel/modules expert developer so
>> I need a little help.
>> Firts I'm trying to understand what the patch do and I think it's clear =

>> (is used a linked list to handle multiple connection).
>>     =

>
> one warning up-front. I never actually ran this patch on any machine. It
> is only compile tested. So it might crash your system.
>
>   =

>> My problems are with kernel programming enviromnment:
>>
>> 1) I'm using kernel-2.6.10 I have to update to a more recent version?
>>     =

>
> It might work, but I advise you to develop against 2.6.18-rc2 or even
> the Git repository from Linus.
>
>   =

>> 2) Is there some documentation about bluez kernel modules? I need to =

>> understand how modules works to make try to make the patch.
>>     =

>
> Check out the kernel documentation itself. There exists no specific
> BlueZ documentation for kernel programming.
>
> Regards
>
> Marcel
>
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share y=
our
> opinions on IT & business topics through brief surveys -- and earn cash
> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>
>
>   =



-- =

______________________________
Fabrizio Guglielmino =

Infit Srl
Software Engineering
Tel. +39 11 7410915
Fax. +39 11 7410915
www.infitsrl.com
C.so Svizzera, 79/8 - Torino
______________________________

Il presente messaggio ed ogni eventuale allegato hanno natura
confidenziale e sono riservati ai destinatari indicati. La diffusione a
terzi e qualsiasi altro uso non autorizzato sono proibiti. I messaggi ed
i relativi allegati possono essere soggetti ad alterazioni. Il mittente
declina ogni responsabilit=E0 per le eventuali alterazioni, modificazioni
o falsificazioni.


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DDE=
VDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2006-07-31 10:02 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-19 16:28 [Bluez-devel] Error: sdptool browse --> Connection reset by peer JP Freeley
2006-07-20  0:48 ` Marcel Holtmann
2006-07-20 21:27   ` JP Freeley
2006-07-25  4:26     ` JP Freeley
2006-07-22 14:08   ` [Bluez-devel] It's rfcomm connect problem Fabrizio Guglielmino
2006-07-24  8:38     ` Andreas Gaufer
2006-07-24 13:33       ` Fabrizio Guglielmino
2006-07-24 13:56         ` Andreas Gaufer
2006-07-24 16:35           ` Marcel Holtmann
2006-07-24 18:34             ` Andreas Gaufer
2006-07-24 20:30               ` Fabrizio Guglielmino
2006-07-24 21:12                 ` Marcel Holtmann
2006-07-27  9:04                   ` Fabrizio Guglielmino
2006-07-27  9:25                     ` [Bluez-devel] It's rfcomm connect problem [ERRATA] Fabrizio Guglielmino
2006-07-28 11:14                     ` [Bluez-devel] It's rfcomm connect problem Marcel Holtmann
2006-07-31 10:02                       ` Fabrizio Guglielmino [this message]
2006-07-31 14:14                         ` [Bluez-devel] About l2cap patch to handle multiple connections Marcel Holtmann
2006-08-02 11:24                           ` Fabrizio Guglielmino
2006-08-02 13:43                             ` 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=44CDD529.6030001@infitsrl.com \
    --to=guglielmino@infitsrl.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 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.