public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Daniel Hellstrom <daniel@gaisler.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] USB unaligned problem
Date: Mon, 01 Feb 2010 11:30:43 +0100	[thread overview]
Message-ID: <4B66AD53.1020103@gaisler.com> (raw)

Hi Remy,

I experience unaligned exceptions when using the USB stack in u-boot on 
SPARC/LEON. I believe that there are many places in the code that must 
be updated since many structures are declared with the GCC attribute 
PACKED and still use 16-bit or 32-bit fields. However, I have so far 
only needed to patch one C-line to make it work. I'm not sure why the 
packed attribute is used in so many structures, I guess it is bacause of 
the layout of the USB information headers read from USB devices.

Please see commit 5b6bc53e4c3eadd04f2ecb94bbb596dca306236a in u-boot 
sparc repoistory, usb branch:

http://git.denx.de/?p=u-boot/u-boot-sparc.git;a=commit;h=5b6bc53e4c3eadd04f2ecb94bbb596dca306236a

What do you think?

Best Regards,
Daniel Hellstrom

             reply	other threads:[~2010-02-01 10:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-01 10:30 Daniel Hellstrom [this message]
2010-02-01 18:52 ` [U-Boot] USB unaligned problem Remy Bohmer

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=4B66AD53.1020103@gaisler.com \
    --to=daniel@gaisler.com \
    --cc=u-boot@lists.denx.de \
    /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