mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: David Miller <davem@davemloft.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: brcm80211 build busted on big-endian
Date: Wed, 22 Jun 2011 08:40:22 -0700	[thread overview]
Message-ID: <20110622154022.GB19027@kroah.com> (raw)
In-Reply-To: <20110621.193641.1605224831578508501.davem@davemloft.net>

On Tue, Jun 21, 2011 at 07:36:41PM -0700, David Miller wrote:
> 
> It tries to do "xor" operations on pointers because of how the
> R_REG() and W_REG() macros are defined.
> 
> ====================
> #define R_REG(r) (\
>         SELECT_BUS_READ( \
>                 ({ \
>                         __typeof(*(r)) __osl_v; \
> 				       		switch (sizeof(*(r))) { \
>                         case sizeof(u8): \
>                                 __osl_v = \
>                                 readb((volatile u8*)((r)^3)); \
>                                 break; \
>                         case sizeof(u16): \
>                                 __osl_v = \
>                                 readw((volatile u16*)((r)^2)); \
>                                 break; \
>                         case sizeof(u32): \
>                                 __osl_v = readl((volatile u32*)(r)); \
>                                 break; \
>                         } \
>                         __osl_v; \
>                 }), \
>                 OSL_READ_REG(r)) \
> )
> ====================
> 
> This driver is a crap fest of volatile pointers and not-compile-tested
> code.

For big endian, I agree, which is why I thought I fixed this up so it
wouldn't build on other arches than MIPS for the moment.

Is this blowing up in -next or in Linus's tree right now?

thanks,

greg k-h

  reply	other threads:[~2011-06-22 15:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-22  2:36 David Miller
2011-06-22 15:40 ` Greg KH [this message]
2011-06-22 20:23   ` David Miller
2011-06-23  1:29     ` Stephen Rothwell
2011-06-27 21:36       ` Greg KH

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=20110622154022.GB19027@kroah.com \
    --to=greg@kroah.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®