From: Laurent Pinchart <laurentp@cse-semaphore.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: netdev@vger.kernel.org, Ben Dooks <ben-linux@fluff.org>
Subject: Re: [PATCH 1/2] [DM9000] Added support for big-endian hosts
Date: Mon, 27 Aug 2007 09:51:34 +0200 [thread overview]
Message-ID: <200708270951.35269.laurentp@cse-semaphore.com> (raw)
In-Reply-To: <46CFB0BE.4030301@garzik.org>
On Saturday 25 August 2007 06:31, Jeff Garzik wrote:
> Laurent Pinchart wrote:
> > This patch splits the receive status in 8bit wide fields and convert the
> > packet length from little endian to CPU byte order.
> >
> > Signed-off-by: Laurent Pinchart <laurentp@cse-semaphore.com>
> > ---
> > drivers/net/dm9000.c | 13 +++++++------
> > 1 files changed, 7 insertions(+), 6 deletions(-)
> >
> > diff --git a/drivers/net/dm9000.c b/drivers/net/dm9000.c
> > index c3de81b..a424810 100644
> > --- a/drivers/net/dm9000.c
> > +++ b/drivers/net/dm9000.c
> > @@ -894,7 +894,8 @@ dm9000_timer(unsigned long data)
> > }
> >
> > struct dm9000_rxhdr {
> > - u16 RxStatus;
> > + u8 RxPktReady;
> > + u8 RxStatus;
> > u16 RxLen;
> > } __attribute__((__packed__));
>
> why does this not need endian conversions as well?
>
> Jeff
The rx header is a 4-byte structure layed out as above (packet ready, status
and length). The first two fields are 8-bit wide so don't need endian
conversion. The length field is a 16-bit big endian value which is converted
to CPU order in dm9000_rx().
Before this patch, the driver accessed the status and packet ready fields as a
16-bit value, which was obviously endianess-dependant.
Best regards,
--
Laurent Pinchart
CSE Semaphore Belgium
Chaussée de Bruxelles, 732A
B-1410 Waterloo
Belgium
T +32 (2) 387 42 59
F +32 (2) 387 42 75
prev parent reply other threads:[~2007-08-27 7:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-16 8:15 [PATCH 1/2] [DM9000] Added support for big-endian hosts Laurent Pinchart
2007-08-16 17:00 ` Ben Dooks
2007-08-25 4:31 ` Jeff Garzik
2007-08-27 7:51 ` Laurent Pinchart [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=200708270951.35269.laurentp@cse-semaphore.com \
--to=laurentp@cse-semaphore.com \
--cc=ben-linux@fluff.org \
--cc=jeff@garzik.org \
--cc=netdev@vger.kernel.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).