Hi, On Wed, 15 Sep 2004, Dimitris Lampridis wrote: > I obviously use the second case (UHCI-like) since my command and data > ports are accessed through IO ports... > So, to end this long description, if I don't have a "struct regs" that > is mapped to memory and accessed via read"x"/write"x", but rather strict > IO ports accesses via in"x"_p/out"x"_p (where "x" stands for b,l,w > etc.), > I don't have any memory mapped ohci_regs too. I'm using macros to access the real chip registers through readw/writew while having a kmalloc'd struct ohci_regs as shadow registers to emulate those bits that the chip doesn't support by itself.
> ------> how can I use the same method with you? <------ > > I mean, up until now, I have defined all the register addresses and > functions like [read/write]_reg[16/32](reg_address, [value]) to use > inw_p and outw_p to get or set the appropriate value, and this > differentiates a lot my work from OHCI, and is my main problem up until > now. Is there a way to map IO ports to memory and issue commands through > readw/writew fucntions??? > Switching from read*/write* to in*/out* is just a matter of redefining the basic access macros *_WRITE_ADDR, *_READ_DATA16 and *_READ_DATA32. Lothar Wassmann ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
