Linux bluetooth development
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Max Krasnyansky <maxk@qualcomm.com>
Cc: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] [PATCH] Fix abuse of kernel headers.
Date: Sat, 26 Apr 2003 00:28:17 +0100	[thread overview]
Message-ID: <1051313297.2850.14.camel@imladris.demon.co.uk> (raw)
In-Reply-To: <5.1.0.14.2.20030425153625.081db0f0@unixmail.qualcomm.com>

On Fri, 2003-04-25 at 23:49, Max Krasnyansky wrote:
> >Take a look at the PPC version.

> Looks ok to me ;-). But I do remember some problem on some arch.
> Which was the reason why I implemented sdp_get_unaligned() instead
> of using <asm/unaligned.h>

It's wrapped in '#ifdef __KERNEL__' on the build box I used. 

> >I looked at that but AFAIK the C standard doesn't actually guarantee the
> > packed structure method will work 

> I don't think packet structures are in the standard. But compiler has to 
> guarantee that. Otherwise we'd have big problems (all hci structures
> are packed).

The people I consulted weren't convinced that the compiler must generate
code which handles the _structure_ being misaligned. Expecting it to
emitting code to correctly read an int which is three bytes from the
beginning of the struct is OK; expecting it to emit code which can
handle misalignment when the member being accessed is at a normal offset
from the start of the structure isn't necessarily safe.
 
> >and since we were always byteswapping
> No we don't. ntohs does nothing on big endian machines.

Sorry, I should have said 'since we were always byteswapping on i386
anyway'. 

Do it that way on ARM and you end up individually loading bytes and
shifting, then you swap them all round afterwards... :)

-- 
dwmw2




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2003-04-25 23:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-25 13:25 [Bluez-devel] [PATCH] Fix abuse of kernel headers David Woodhouse
2003-04-25 17:43 ` Max Krasnyansky
2003-04-25 21:16   ` David Woodhouse
2003-04-25 22:49     ` Max Krasnyansky
2003-04-25 23:28       ` David Woodhouse [this message]
2003-04-28 21:49         ` Max Krasnyansky
2003-04-29 10:15           ` David Woodhouse

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=1051313297.2850.14.camel@imladris.demon.co.uk \
    --to=dwmw2@infradead.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=maxk@qualcomm.com \
    /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