From: Jeff Baitis <baitisj@evolution.com>
To: Dan Malek <dan@embeddededge.com>
Cc: ppopov@mvista.com, linux-mips@linux-mips.org
Subject: Re: fixup_bigphys_addr and DBAu1500 dev board
Date: Fri, 21 Feb 2003 19:50:31 -0800 [thread overview]
Message-ID: <20030221195031.I20129@luca.pas.lab> (raw)
In-Reply-To: <3E568ECC.2090601@embeddededge.com>; from dan@embeddededge.com on Fri, Feb 21, 2003 at 03:40:44PM -0500
Dan & Pete:
Thank you very much for your help!
I've patched things up, and my kernel runs, but the yenta_socket kernel module
still locks the system. Time to break out GDB and take a look at everything!
Please let me know if ya'll have some suggestions. :*)
After the 36-bit PCI patch, I had to alter include/asm-mips/io.h in order to
get drivers/net/wireless to compile. Preprocessor expansion of outw_p in the
hermes.h -> hermes_enable_interrupt and hermes_set_irqmask inline functions
caused some issues; I hope this patch is of some use!
Regards,
Jeff
diff -u -r1.29.2.19 include/asm-mips/io.h
--- include/asm-mips/io.h 28 Nov 2002 23:04:11 -0000 1.29.2.19
+++ include/asm-mips/io.h 22 Feb 2003 03:44:27 -0000
@@ -329,12 +329,25 @@
SLOW_DOWN_IO; \
} while(0)
-#define outw_p(val,port) \
-do { \
- *(volatile u16 *)(mips_io_port_base + __swizzle_addr_w(port)) = \
- __ioswab16(val); \
- SLOW_DOWN_IO; \
-} while(0)
+/* baitisj */
+static inline u16 outw_p(u16 val, unsigned long port)
+{
+ register u16 retval;
+ do {
+ retval = *(volatile u16 *)(mips_io_port_base + __swizzle_addr_w(port)) =
+ __ioswab16(val);
+ SLOW_DOWN_IO;
+ } while(0);
+ return retval;
+}
+/*
+ * #define outw_p(val,port) \
+ * do { \
+ * *(volatile u16 *)(mips_io_port_base + __swizzle_addr_w(port)) = \
+ * __ioswab16(val); \
+ * SLOW_DOWN_IO; \
+ * } while(0)
+ */
#define outl_p(val,port) \
do { \
On Fri, Feb 21, 2003 at 03:40:44PM -0500, Dan Malek wrote:
> Jeff Baitis wrote:
>
> > I'd love to know where this mystery fixup_bigphys_addr comes from!?
>
> You need the 36-bit patch from Pete that is not yet part of the
> linux-mips tree.
>
> You can find it on linux-mips.org in /pub/linux/mips/people/ppopov.
>
> Have fun!
>
>
> -- Dan
>
>
>
--
Jeffrey Baitis - Associate Software Engineer
Evolution Robotics, Inc.
130 West Union Street
Pasadena CA 91103
tel: 626.535.2776 | fax: 626.535.2777 | baitisj@evolution.com
next prev parent reply other threads:[~2003-02-22 3:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-20 6:05 Ramdisk image on flash Krishnakumar. R
2003-02-20 18:27 ` Pete Popov
2003-02-20 19:30 ` Tibor Polgar
2003-02-20 19:41 ` Mark Salter
2003-02-20 20:01 ` Tibor Polgar
2003-02-20 20:16 ` Mark Salter
2003-02-20 20:35 ` Dan Malek
2003-02-20 20:44 ` Jun Sun
2003-02-20 20:57 ` Pete Popov
2003-02-20 21:24 ` Dan Malek
2003-02-20 20:37 ` Jun Sun
2003-02-20 21:08 ` Guido Guenther
2003-02-20 21:12 ` Alan Cox
2003-02-20 19:41 ` Pete Popov
2003-02-20 19:42 ` Brian Murphy
2003-02-20 20:59 ` Guido Guenther
2003-02-20 21:27 ` Dan Malek
2003-02-21 2:24 ` Atsushi Nemoto
2003-02-21 20:25 ` fixup_bigphys_addr and DBAu1500 dev board Jeff Baitis
2003-02-21 20:40 ` Dan Malek
2003-02-21 22:10 ` Pete Popov
2003-02-22 3:50 ` Jeff Baitis [this message]
2003-02-23 9:19 ` Geert Uytterhoeven
2003-02-24 17:46 ` Pete Popov
2003-02-25 21:54 ` Jeff Baitis
2003-02-25 22:05 ` Pete Popov
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=20030221195031.I20129@luca.pas.lab \
--to=baitisj@evolution.com \
--cc=dan@embeddededge.com \
--cc=linux-mips@linux-mips.org \
--cc=ppopov@mvista.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.