Hi Dimitris, Dimitris Lampridis writes: > OK, that's good news, but I have the same problem with asm/hardware.h > asm/mach-types.h and asm/arch/dma.h . This whole thing is very > arm-specific... So in my i386 platform, it doesn't compile. Anyway, I > guess I don't need things like mach-types, so we should #ifdef their use > maybe? And if you agree, what is the best #define statement that we > should use to check? > They should probably go in an architecture dependent header file so we won't have the main source file cluttered with #ifdef's. It might even be necessary to split out some functionality from the isp1362.c file. E.g. the 'platform_device' stuff will need to be replaced with 'pci_device' specific routines for PCI based systems.
> Perfectly understood, except the 'MASK'. I mean it even has the same > number (0x600) as 'RW'... And while RW is R+W masks together, why have > the same thing with another name? > REG_ACCESS_MASK can be used to isolate the access mode bits from the register specification just like REG_NO_MASK isolates the register number. Lothar Wassmann ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
