netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: netdev@vger.kernel.org
Subject: Re: sky2 problem on powerpc
Date: Wed, 06 Sep 2006 07:11:05 +1000	[thread overview]
Message-ID: <1157490665.22705.128.camel@localhost.localdomain> (raw)
In-Reply-To: <20060904211531.307bbd7f@localhost.localdomain>

On Mon, 2006-09-04 at 21:15 -0700, Stephen Hemminger wrote:
> On Tue, 05 Sep 2006 13:47:52 +1000
> Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
> 
> > 
> > > It may not need any swapping, it is hard to tell what the hardware
> > > will do without experimentation.
> > 
> > Yes... did you have a chance to test the vlan stuff on LE machines
> > (x86) ? did it work with the BE swapping you were doing ? I've
> > purposedly removed in my patches the hardware side swapping of the
> > descriptors, as I explained, thus making the hardware react the same on
> > ppc and x86. Thus we need the exact same swapping macros on both
> > platforms).
> 
> 
> Last time I checked it worked.  Private cable simulating VLAN
> from other Linux card.

Ok, so we should probably switch back the vlan bits to BE swapping
macros... 

However, we then have an inconsistency with that bit:

#ifdef SKY2_VLAN_TAG_USED
                case OP_RXVLAN:
                        sky2->rx_tag = length;
                        break;

                case OP_RXCHKSVLAN:
                        sky2->rx_tag = length;
                        /* fall through */
#endif

in sky2_status_intr()

Where we read the lenght field directly without swapping (on the non
patched driver, on the patched driver, lenght will have gone through an
LE swap). That is, if you take the standpoint of a LE machine, you will
read that value as a little endian value while elsewhere, we manipulate
sky2->rx_tag as a BE value... (this is even without my patch)

Ben.



  reply	other threads:[~2006-09-05 21:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-04  5:24 sky2 problem on powerpc Benjamin Herrenschmidt
2006-09-04  7:21 ` Benjamin Herrenschmidt
2006-09-04  7:42   ` Benjamin Herrenschmidt
2006-09-04 21:05     ` Segher Boessenkool
2006-09-04 21:33       ` Benjamin Herrenschmidt
2006-09-05  3:41     ` Stephen Hemminger
2006-09-05  3:47       ` Benjamin Herrenschmidt
2006-09-05  4:15         ` Stephen Hemminger
2006-09-05 21:11           ` Benjamin Herrenschmidt [this message]
2006-09-05 21:36             ` Stephen Hemminger
2006-09-05 22:00               ` Benjamin Herrenschmidt

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=1157490665.22705.128.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@osdl.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).