> > I merged them into the kernel, rather than building standalone, but from > > Hm, but compiling this standalone gives a module file, doesn it?
I should think so, but as I said, I've only used the driver by merging with the kernel, and not by building it standalone... Your build procedure looks reasonable, although I would have edited the makefile to use arm-linux-gcc directly. > I think that works fine. I cross-compiled bluez-pand this way. > (Litle off-topic but I wasn't able to do this 'export' by a script. > How can I do this? Just making a file executable with the above line > does not work, and also some other variants I tried) If you do the export in a script then it is only valid for that process and it's children, when the script returns the variable will go 'out of scope'. You probably need to source the script from your current shell with 'source SCRIPT'. Even better would be to add the export to your shells initialisation script (perhaps ~/.bash_profile) > But now I get the following error on boot: You need to pass in the correct module parameters for I/O addresses. hc_data_port=0xf4000000 hc_cmd_port=0xf4000002 irq=25 (or the addresses might be reversed, I can't quite remember and don't have a VIPER to hand to try). There is also hc_wu_port in the source, but it doesn't seem to be used. The wu port isn't connected on the VIPER, you could try hc_wu_port=0xf4000004, since it needs to be set to something I think and the default of 0x240 is invalid on a VIPER, or you could try hacking the source to remove references to hc_wu_port -- it doesn't seem to be used. BTW -- I think you have now got about as far as I did with this driver before I got distracted -- I hope to have time to look at it again this week. 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. ------------------------------------------------------- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel