qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Blue Swirl <blauwirbel@gmail.com>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: Revert bogus usb-ohci change
Date: Mon, 5 Apr 2010 00:02:33 +0300	[thread overview]
Message-ID: <y2if43fc5581004041402uc291ef72ha0f205c8575c7cec@mail.gmail.com> (raw)
In-Reply-To: <201004042130.23957.paul@codesourcery.com>

On 4/4/10, Paul Brook <paul@codesourcery.com> wrote:
> Commit f1698408 "Compile usb-ohci only once" introduces a "be" property to the
>  pci-ohci device. The PCI bus is always little-endian, so this is completely
>  bogus. A hypothetical big-endian device would actually introduce another
>  byteswap.

Then why there are again byte swaps with big endian target, aren't
they bogus too? Because we don't have the byte swapping bus yet.
Current system is bogus in this respect, so I claim that in general,
the level of bogosity was not changed.

>  As discussed previously, if you really want to avoid compiling the device
>  multiple times then this needs to be fixed elsewhere. Adding user visible
>  properties to devices is definitely not the right solution.
>
>  I have reverted this change. If there are other devices that have been hacked
>  in the same way then please revert those too.

I agree that the user visible property solution was wrong, sorry.

I had a patch "Compile rtl8139 and e1000 only once", which had "be"
property too but I didn't commit it because the property passing
didn't feel right and I didn't have a plan how to pass that from
higher levels.

Other patches didn't use the property method.

  reply	other threads:[~2010-04-04 21:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-04 20:30 [Qemu-devel] Revert bogus usb-ohci change Paul Brook
2010-04-04 21:02 ` Blue Swirl [this message]
2010-04-04 21:28   ` [Qemu-devel] " Paul Brook

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=y2if43fc5581004041402uc291ef72ha0f205c8575c7cec@mail.gmail.com \
    --to=blauwirbel@gmail.com \
    --cc=paul@codesourcery.com \
    --cc=qemu-devel@nongnu.org \
    /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;
as well as URLs for NNTP newsgroup(s).