From: Paul Brook <paul@codesourcery.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: Revert bogus usb-ohci change
Date: Sun, 4 Apr 2010 22:28:47 +0100 [thread overview]
Message-ID: <201004042228.47496.paul@codesourcery.com> (raw)
In-Reply-To: <y2if43fc5581004041402uc291ef72ha0f205c8575c7cec@mail.gmail.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.
The difference is that your patch makes this visible to the user.
Internal warts are only annoying to developers. User visible warts annoy
and/or confuse everyone. Improving compile time at the expense of end user
happiness is something I consider to be a bad idea.
Compare this with e.g. pflash_cfi01 where you're trading compile time for code
size (~100 extra lines). I'm not entirely convinced this is worth it, but am
not going to object too strongly. I do however think that your naming
convention is wrong. Instead of be/le it should be native/cross endian.
It just happens that all the current cross cases are for LE devices on a BE
target.
Paul
prev parent reply other threads:[~2010-04-04 21:28 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 ` [Qemu-devel] " Blue Swirl
2010-04-04 21:28 ` Paul Brook [this message]
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=201004042228.47496.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=blauwirbel@gmail.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).