LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Dale Farnsworth" <dale@farnsworth.org>
To: Valentine Barshak <vbarshak@ru.mvista.com>
Cc: david-b@pacbell.net, linuxppc-dev@ozlabs.org,
	linux-usb-devel@lists.sourceforge.net
Subject: Re: [linux-usb-devel] [PATCH] USB: Add frame_no big endian OHCI quirk
Date: Mon, 8 Oct 2007 11:52:25 -0700	[thread overview]
Message-ID: <20071008185225.GB2900@xyzzy.farnsworth.org> (raw)
In-Reply-To: <20071008184140.GA30470@ru.mvista.com>

On Mon, Oct 08, 2007 at 10:41:40PM +0400, Valentine Barshak wrote:
> Add OHCI big endian frame_no quirk.
> The frame_no value stored in the HCCA is a 16 bit field 
> at a specific offset, but since not all CPUs can do 16-bit
> memory accesses it's used as a 32 bit field.
> And that's why big-endian OHCI will shift 16 bits,
> unless the spec is not followed. Currently there's one MPC52xx
> platform that doesn't need the shift. This case is hanled
> using big endian frame_no quirk.
> 
> Signed-off-by: Valentine Barshak <vbarshak@ru.mvista.com>

Acked-by: Dale Farnsworth <dale@farnsworth.org>

  reply	other threads:[~2007-10-08 18:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-08 14:25 [PATCH] OHCI: add PowerPC 440EP/440EPx support Valentine Barshak
2007-10-08 15:01 ` [linux-usb-devel] " David Brownell
2007-10-08 16:06   ` Valentine Barshak
2007-10-08 16:19     ` David Brownell
2007-10-08 16:54       ` [PATCH] USB: Add frame_no big endian OHCI quirk Valentine Barshak
2007-10-08 16:58         ` [linux-usb-devel] " Valentine Barshak
2007-10-08 18:41         ` Valentine Barshak
2007-10-08 18:52           ` Dale Farnsworth [this message]
2007-10-08 17:39       ` [linux-usb-devel] [PATCH] OHCI: add PowerPC 440EP/440EPx support Kumar Gala
2007-10-08 17:42         ` Valentine Barshak
2007-10-08 19:45           ` David Brownell

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=20071008185225.GB2900@xyzzy.farnsworth.org \
    --to=dale@farnsworth.org \
    --cc=david-b@pacbell.net \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=vbarshak@ru.mvista.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