On Sun, 2004-05-09 at 01:46, Christoph Torens wrote:
> Hi,
> 
> First of all, I am impressed by the many mails that came over the list.
> Many thanks for your help. (And sorry for my late answer)
> 
> Ian Campbell wrote:
> > The VIPER kernel has the Roman Weissgaerber's 0.9.5 driver, I was never
> > able to get the BDL one to work quite right, and some of the patches
> > seemed more invasive than I was happy with.
> 
> Sorry, I didn't get it. What do you mean with "BDL"?
> The Boudarydevices patches?

Sorry, yes I mean the boundary devices patches.

> > I've been playing with the patches from
> > http://www.bennee.com/~alex/software/kernel/index.php as well, although
> > nothing has been released by Arcom using it at this time it's likely
> > this is what we will use for the next release.
> 
> That sounds interesting.
> I downloaded them. I tried to compile it (using the Arcom cross compiler)

I merged them into the kernel, rather than building standalone, but from
your log messages you are using 'sh4-linux-gcc' instead of
'arm-linux-gcc', your changes seem to make it use just 'cc' which is
also wrong (that will be your native host system compiler).

--no-implicit-fp is probably an sh4 option -- just remove it.

I also needed the attached patch.

Ian.

-- 
Ian Campbell, Senior Design Engineer
                                        Web: http://www.arcom.com
Arcom, Clifton Road,                    Direct: +44 (0)1223 403 465
Cambridge CB1 7EA, United Kingdom       Phone:  +44 (0)1223 411 200


_____________________________________________________________________
The message in this transmission is sent in confidence for the attention of the 
addressee only and should not be disclosed to any other party. Unauthorised recipients 
are requested to preserve this confidentiality. Please advise the sender if the 
addressee is not resident at the receiving end.  Email to and from Arcom is 
automatically monitored for operational and lawful business reasons.

This message has been virus scanned by MessageLabs.
--- linux-2.4.25-vrs-pxa.orig/drivers/usb/host/hc_isp116x.c     2004-04-21 
16:42:01.000000000 +0100
+++ linux-2.4.25-vrs-pxa/drivers/usb/host/hc_isp116x.c  2004-04-21 16:42:02.000000000 
+0100
@@ -132,9 +132,10 @@
 ** and will need to be changed for each baord this driver runs on
 ** depending on things like IRQ polarity
 **
-** Built in Resitors:    xxx1 xxxx xxxx xxxx
+** Built in Resitors:   xxx1 xxxx xxxx xxxx
 ** Clock can be stopped:xxxx 0xxx xxxx xxxx
 ** Use anaglog OC det:  xxxx x1xx xxxx xxxx
+** Reserved:            xxxx xx0x xxxx xxxx
 ** DACKmode normal:     xxxx xxx0 xxxx xxxx
 ** EOTInput polarity:   xxxx xxxx 1xxx xxxx
 ** DACKInput polarity:  xxxx xxxx x1xx xxxx
@@ -169,29 +170,21 @@
 
 static inline void ISP116x_OUTW (int val, unsigned long addr) 
 {
-    *(volatile u16 *)addr=val;
-    //    outw (val, addr);
-    
+#ifdef CONFIG_ARCH_VIPER
+       outw (val, addr);
+#else
+       *(volatile u16 *)addr=val;
+#endif    
 }
 
 static inline int ISP116x_INW (unsigned long addr)
 {
-    return *(volatile u16 *)addr;
-    //    return inw (addr);
-    
-}
-
-
-#ifdef ndelay
-#undef ndelay
+#ifdef CONFIG_ARCH_VIPER
+        return inw (addr);
+#else
+       return *(volatile u16 *)addr;
 #endif
-
-// #define ndelay(n) (__builtin_constant_p(n) ? ((n) > 20000 ? __bad_ndelay() : 
__const_udelay((n) * 5)) : __ndelay(n))
-
-// #define ndelay(n)  __const_udelay((n) * 5) 
-
-#define ndelay(n)  __const_udelay((n) * 50) 
-
+}
 
 /*
 ** These register READ/WRITE functions need to be protected by a

Reply via email to