From: Claudio Takahasi <cktakahasi@gmail.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] hcid D-Bus patch(Error Messages)
Date: Wed, 28 Sep 2005 09:19:28 -0300 [thread overview]
Message-ID: <e1effdeb05092805194782ba65@mail.gmail.com> (raw)
In-Reply-To: <1127896709.5321.7.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1727 bytes --]
Hi Marcel,
it's possible use uint32 without problems.
- 0x00000000 - 0x000000FF Bluetooth error codes (current situation)
- 0x00000100 - 0x0000FFFF Reserved for future Bluetooth error codes
extension
- 0x00010000 - 0x0001FFFF D-Bus errors
- 0x00020000 - 0x0003FFFF System errors (0x00020000 + system error value)
- 0x00040000 - 0xFFFFFFFF Reserved to future error classes
In order to make easier discover the error type, I defined the error values
range
considering bitwise operations.
Regards,
Claudio.
On 9/28/05, Marcel Holtmann <marcel@holtmann.org> wrote:
>
> Hi Claudio,
>
> > 2. Use error ranges
> > Define only one error message name(org.bluez.EFailed), signature:
> > sq
> > - 0x0000 - 0x00FF Bluetooth error codes
> > - 0x0100 - 0x01FF D-Bus errors
> > - 0x0200 - 0x02FF System errors (0x0200 + system error value)
> > - 0x0300 - 0xFFFF reserved to future error classes
>
> I like to go with this approach and a name like org.bluez.Error, because
> this makes it easy to map the Bluetooth errors. Question is if we should
> use uint16 or uint32. Maybe the Bluetooth specification extend their
> error codes to an uint16 instead of an uint8 and then I like to have a
> free space in this range. Do you think this is a problem?
>
> Regards
>
> Marcel
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Power Architecture Resource Center: Free content, downloads, discussions,
> and more. http://solutions.newsforge.com/ibmarch.tmpl
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>
[-- Attachment #2: Type: text/html, Size: 2393 bytes --]
next prev parent reply other threads:[~2005-09-28 12:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-26 14:27 [Bluez-devel] hcid D-Bus patch(Error Messages) Claudio Takahasi
2005-09-28 8:38 ` Marcel Holtmann
2005-09-28 12:19 ` Claudio Takahasi [this message]
2005-09-29 16:27 ` 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=e1effdeb05092805194782ba65@mail.gmail.com \
--to=cktakahasi@gmail.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.