From: Michael Buesch <mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
To: Jiri Pirko <jpirko-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Petko Manolov
<petkan-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] pegasus usb-net: Fix endianness bugs
Date: Thu, 18 Jun 2009 20:02:42 +0200 [thread overview]
Message-ID: <200906182002.42629.mb@bu3sch.de> (raw)
In-Reply-To: <20090618174621.GA3416-YzwxZg+R7evSU73v1vjTzyO4YDw3rz4rAInAS/Ez/D0@public.gmane.org>
On Thursday 18 June 2009 19:46:22 Jiri Pirko wrote:
> >--- linux-2.6.30.orig/drivers/net/usb/pegasus.c
> >+++ linux-2.6.30/drivers/net/usb/pegasus.c
> >@@ -297,7 +297,7 @@ static int update_eth_regs_async(pegasus
> >
> > pegasus->dr.bRequestType = PEGASUS_REQT_WRITE;
> > pegasus->dr.bRequest = PEGASUS_REQ_SET_REGS;
> >- pegasus->dr.wValue = 0;
> >+ pegasus->dr.wValue = cpu_to_le16(0);
> Is this necessary? I mean zero is still zero :-)
Well, yes. However wValue is a little endian variable and 0 is CPU endian.
The fact that 0 is represented with the same bits in LE and BE doesn't really
matter. It documents the fact that we really require this to be a LE value.
GCC will recognize it and optimize it away, so it's not a runtime issue.
And wValue = cpu_to_le16(0) is used in the rest of the driver, too. This is the
only place that doesn't use it. So let's fix it. If only for consistency.
> >+ u8 interval;
> >
> >- read_eprom_word(pegasus, 4, (__u16 *) data);
> >+ read_eprom_word(pegasus, 4, &data);
> >+ interval = data >> 8;
> > if (pegasus->usb->speed != USB_SPEED_HIGH) {
> >- if (data[1] < 0x80) {
> >+ if (interval < 0x80) {
> > if (netif_msg_timer(pegasus))
> > dev_info(&pegasus->intf->dev, "intr interval "
> > "changed from %ums to %ums\n",
> >- data[1], 0x80);
> >- data[1] = 0x80;
> >+ interval, 0x80);
> >+ interval = 0x80;
> >+ data = (data & 0x00FF) | ((u16)interval << 8);
> ^^^^^ you do not need this
> typecast
Hm, well. The cast is there because "interval" is an 8bit variable.
I think the behavior of C is machine dependent in such a situation.
But as Linux doesn't run on anything with less than 32bit registers, it probably
doesn't matter.
--
Greetings, Michael.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-06-18 18:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-18 17:03 [PATCH] pegasus usb-net: Fix endianness bugs Michael Buesch
[not found] ` <200906181903.47541.mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
2009-06-18 17:46 ` Jiri Pirko
[not found] ` <20090618174621.GA3416-YzwxZg+R7evSU73v1vjTzyO4YDw3rz4rAInAS/Ez/D0@public.gmane.org>
2009-06-18 18:02 ` Michael Buesch [this message]
2009-06-19 7:25 ` David Miller
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=200906182002.42629.mb@bu3sch.de \
--to=mb-fseuscv1ubazqb+pc5nmwq@public.gmane.org \
--cc=jpirko-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=petkan-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.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).