[07:43] [09:35] Hello all I have a quick question probably like most. Does anyone know how to get Quick Synergy to work? [09:36] I have attempted to set it up several times now and have not luck [09:44] Hello all [11:00] Can anyone suggest me a goos ARM board with usb host? cheap pls.. :) [11:01] vanexx: beagleboard is probably the nicest you can get for now [11:02] it's v7 and has advanced modern hardware [11:03] yeah but is there any seller here in europe? [11:03] i know it is 149 $ [11:03] but shpping cost is 80 [11:04] hmm hey what about this.. http://plugcomputer.org/ it is cool [11:05] You can group orders; don't think there's a reseller in Europe [11:05] vanexx: The sheevaplug is cute and nice and cheap, but keep in mind it's ARMv5 and has no VFP [11:05] You can run Jaunty or Debian on it, but soon you wont be able to run karmic [12:42] I am crosscompiling UVCVIDEO to an arm board with linux 2.6.14, uvcvideo needs to be compiled with version > 2.6.14. [12:42] So its ok, I crosscompile it with 2.6.28 in my PC with no problems, the problem is: when I try to insmod the compiled uvcvideo.ko into the ARM kernel i got errors of the type [12:42] "undefined symbol X", thats normal because those symbols (symbols from v4l2 etc) are not in 2.6.14 os version, so is there way for compiling [12:42] uvcvideo specifyng that all refrences must be static instead of dynamic? [12:45] vanexx: you need to compile the module with the kernel you really use. [12:46] if uvcvideo needs a kernel > 2.6.14, then it needs that version to run too. [12:47] but.. i cant change the os in the ARM board [12:47] it is 2.6.14 and cannont be changed.. [12:48] I do believe it is possible without compiling with the version I really use.. it is only a matter of compiling statically [12:48] no, it's not. [12:48] I mean gaspa, the only diff between 2.6.14 and 2.6.15 for example are new functions and symbols [12:48] why can't the kernel be changed? it's on a ROM? [12:48] "only" ? [12:49] :P [12:49] so if u export those symbols to ur static compilantion... [12:49] well no really only but, yes for that matter [12:49] you will at least need the headers for that kernel [12:49] gaspa no its on a flasy and yes it can be changed but i have no support from the vendor to do it [12:49] (the *configured* headers, which means you need the source) [12:50] ogra yes... thats true [12:50] ogra: "(01:42:26 PM) vanexx: I am crosscompiling UVCVIDEO to an arm board with linux 2.6.14, uvcvideo needs to be compiled with version > 2.6.14." [12:50] yep, i saw that [12:50] thats what i want: use the kernel headers but when compiling the resulting module must have all their references static [12:50] backport it then :) [12:51] or forwardport the missing functions [12:51] i think backporting is what you need to do. [12:52] how can I do it? [12:52] with a lot of coding :) [12:52] change the code of uvcvideo to match the interface of 2.6.14... [12:52] and there is no guarantee it will work [12:53] (which you will only find out in the end) === ogra_ is now known as ogra [13:46] and what if I dont change the OS in the ARM but in /lib i put libraries from the 2.6.28 for ex? [13:47] using busyboc for ex [13:47] busybox [14:14] vanexx: no, userspace library doesn't matter at all. uvcvideo is a kernel module, and so, must be compiled against the "same" kernel that will run it. [16:52] * bizkut i am back