Thanks Dave! I check this all.
> > But big problem is usb_new_device(), > > alias hcd_register_root() for old drivers. > > Use the updated calls, which know how to work with > the driver model code. You'll have to create > some kind of (platform?) device for the sl811 and > hook it in, for power management, sysfs linkage, > and other goodies. I have x86, and I will handle ARM to > > Driver hc_sl811* can not compile: Many compiler errors. > > Yes, I think I remember noticing nobody updated it during > the 2.5 development cycle. You don't need to convert > to use the "hcd" glue framework, though that would be > a win eventually. You can update SL-811 to 2.6 while > still using the old "struct usb_operations" interfaces, > like the current code does. Anybody shold mark it as "Not running Source". > > What is the best skeleton for a new host controller? > > For PCI, I think OHCI is simplest. > > And for non-PCI, the only working example in the 2.6 > kernel is the ohci-sa1111.c code ... perhaps the two > of those give you an answer! :) My decice use ISA-Bus (non-PCI, non-DMA). Have I right understand, than I lock into ohci-sa1111.c and create all this function calls of hardware for my controller? Henry ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
