From: Matthew Wilcox <matthew@wil.cx>
To: Ryan Bradetich <rbradetich@uswest.net>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] sym53c8xx driver with 64-bit kernel on C200.
Date: Sun, 4 Mar 2001 04:18:33 +0000 [thread overview]
Message-ID: <20010304041833.B1865@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <3AA1BA3F.A7C79E31@uswest.net>; from rbradetich@uswest.net on Sat, Mar 03, 2001 at 08:45:03PM -0700
On Sat, Mar 03, 2001 at 08:45:03PM -0700, Ryan Bradetich wrote:
> When I run OUTL(nc_dsp,pc) through the preprocessor the statement gets
> expanded into this:
>
> _gsc_writel(((__builtin_constant_p((__u32)((((pc))))) ? ({ __u32 __x =
> (((((pc))))); ((__u32)( (((__u32)(__x) & (__u32)0x000000ffUL) << 24) |
> (((__u32)(__x) & (__u32)0x0000ff00UL) << 8) | (((__u32)(__x) &
> (__u32)0x00ff0000UL) >> 8) | (((__u32)(__x) & (__u32)0xff000000UL) >>
> 24) )); }) : __fswab32(((((pc))))))),(void *)((char *)np->reg +
> (((size_t) &((struct ncr_reg *)0)->nc_dsp))));
I guess you'd like this decoded? Let's see. `pc' is clearly not a constant,
so __builtin_constant_p returns false, so we can simplify this down to:
_gsc_writel(__fswab32(pc) ,
(void *)((char *)np->reg + (((size_t) &((struct ncr_reg *)0)->nc_dsp))));
which leads me to ask `what value does `pc' have?'
I suspect you want to put debugging code in _gsc_writel to tell you where
you're trying to perform IO to.
My suspicion is that you're writing to the 32 bit IO space in 64-bit mode,
which is juts not going to work.
--
Revolutions do not require corporate support.
next prev parent reply other threads:[~2001-03-04 4:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-04 3:45 [parisc-linux] sym53c8xx driver with 64-bit kernel on C200 Ryan Bradetich
2001-03-04 4:18 ` Matthew Wilcox [this message]
2001-03-04 6:50 ` Ryan Bradetich
2001-03-04 16:57 ` Ryan Bradetich
2001-03-05 20:34 ` Richard Hirst
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=20010304041833.B1865@parcelfarce.linux.theplanet.co.uk \
--to=matthew@wil.cx \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=rbradetich@uswest.net \
/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