newer version of HTC Dream support
in [Kernel]
|
Prev: writeback: switch to per-bdi threads for flushing data
Next: [patch 38/48] kthreads: fix kthread_create() vs kthread_stop() race
From: Randy Dunlap on 4 Sep 2009 12:10 On Tue, 1 Sep 2009 15:21:59 +0200 Pavel Machek wrote: > Hi! > > > With 2.6.31 being closer... is there a git tree or set of patches to > > make it boot on HTC Dream? > > > > Quite a lot of hw should be supported in linux-next, and it would be > > nice to get arch-specific code working with linux-next and eventually > > merged... > > Any news here? If you need some more kernel hackers I guess I'm > looking for a job :-). well, mmotm and linux-next dream builds fail like this: CC drivers/staging/dream/gpio_axis.o drivers/staging/dream/gpio_axis.c:18:30: error: linux/gpio_event.h: No such file or directory drivers/staging/dream/gpio_axis.c: In function 'gpio_event_update_axis': drivers/staging/dream/gpio_axis.c:68: error: dereferencing pointer to incomplete type drivers/staging/dream/gpio_axis.c:69: error: dereferencing pointer to incomplete type drivers/staging/dream/gpio_axis.c:70: error: dereferencing pointer to incomplete type drivers/staging/dream/gpio_axis.c:71: error: dereferencing pointer to incomplete type drivers/staging/dream/gpio_axis.c:71: error: 'GPIOEAF_PRINT_RAW' undeclared (first use in this function) drivers/staging/dream/gpio_axis.c:71: error: (Each undeclared identifier is reported only once drivers/staging/dream/gpio_axis.c:71: error: for each function it appears in.) drivers/staging/dream/gpio_axis.c:71: error: dereferencing pointer to incomplete type drivers/staging/dream/gpio_axis.c:71: error: dereferencing pointer to incomplete type drivers/staging/dream/gpio_axis.c:72: error: dereferencing pointer to incomplete type drivers/staging/dream/gpio_axis.c:72: error: dereferencing pointer to incomplete type drivers/staging/dream/gpio_axis.c:75: error: dereferencing pointer to incomplete type drivers/staging/dream/gpio_axis.c:75: error: 'EV_REL' undeclared (first use in this function) drivers/staging/dream/gpio_axis.c:75: error: dereferencing pointer to incomplete type drivers/staging/dream/gpio_axis.c:75: error: dereferencing pointer to incomplete type drivers/staging/dream/gpio_axis.c:76: error: dereferencing pointer to incomplete type drivers/staging/dream/gpio_axis.c:77: error: dereferencing pointer to incomplete type drivers/staging/dream/gpio_axis.c:78: error: dereferencing pointer to incomplete type drivers/staging/dream/gpio_axis.c:78: error: dereferencing pointer to incomplete type drivers/staging/dream/gpio_axis.c:78: error: dereferencing pointer to incomplete type drivers/staging/dream/gpio_axis.c:79: error: dereferencing pointer to incomplete type drivers/staging/dream/gpio_axis.c:80: error: dereferencing pointer to incomplete type drivers/staging/dream/gpio_axis.c:80: error: dereferencing pointer to incomplete type drivers/staging/dream/gpio_axis.c:80: error: dereferencing pointer to incomplete type drivers/staging/dream/gpio_axis.c:81: error: dereferencing pointer to incomplete type drivers/staging/dream/gpio_axis.c:81: error: 'GPIOEAF_PRINT_EVENT' undeclared (first use in this function) drivers/staging/dream/gpio_axis.c:81: error: dereferencing pointer to incomplete type drivers/staging/dream/gpio_axis.c:81: error: dereferencing pointer to incomplete type drivers/staging/dream/gpio_axis.c:82: error: dereferencing pointer to incomplete type drivers/staging/dream/gpio_axis.c:82: error: dereferencing pointer to incomplete type drivers/staging/dream/gpio_axis.c:87: error: dereferencing pointer to incomplete type drivers/staging/dream/gpio_axis.c:87: error: dereferencing pointer to incomplete type drivers/staging/dream/gpio_axis.c:87: error: dereferencing pointer to incomplete type drivers/staging/dream/gpio_axis.c:88: error: dereferencing pointer to incomplete type drivers/staging/dream/gpio_axis.c:88: error: dereferencing pointer to incomplete type drivers/staging/dream/gpio_axis.c:90: error: implicit declaration of function 'input_report_rel' drivers/staging/dream/gpio_axis.c:90: error: dereferencing pointer to incomplete type drivers/staging/dream/gpio_axis.c:92: error: dereferencing pointer to incomplete type drivers/staging/dream/gpio_axis.c:92: error: dereferencing pointer to incomplete type drivers/staging/dream/gpio_axis.c:92: error: dereferencing pointer to incomplete type drivers/staging/dream/gpio_axis.c:93: error: dereferencing pointer to incomplete type drivers/staging/dream/gpio_axis.c:93: error: dereferencing pointer to incomplete type drivers/staging/dream/gpio_axis.c:95: error: implicit declaration of function 'input_event' drivers/staging/dream/gpio_axis.c:95: error: dereferencing pointer to incomplete type drivers/staging/dream/gpio_axis.c:95: error: dereferencing pointer to incomplete type drivers/staging/dream/gpio_axis.c:97: error: implicit declaration of function 'input_sync' drivers/staging/dream/gpio_axis.c: At top level: drivers/staging/dream/gpio_axis.c:110: warning: 'struct gpio_event_info' declared inside parameter list drivers/staging/dream/gpio_axis.c:110: warning: its scope is only this definition or declaration, which is probably not what you want drivers/staging/dream/gpio_axis.c: In function 'gpio_event_axis_func': drivers/staging/dream/gpio_axis.c:118: error: dereferencing pointer to incomplete type drivers/staging/dream/gpio_axis.c:118: warning: type defaults to 'int' in declaration of '__mptr' drivers/staging/dream/gpio_axis.c:118: warning: initialization from incompatible pointer type drivers/staging/dream/gpio_axis.c:118: error: invalid use of undefined type 'struct gpio_event_axis_info' drivers/staging/dream/gpio_axis.c:119: error: 'GPIO_EVENT_FUNC_SUSPEND' undeclared (first use in this function) drivers/staging/dream/gpio_axis.c:120: error: dereferencing pointer to incomplete type drivers/staging/dream/gpio_axis.c:121: error: dereferencing pointer to incomplete type drivers/staging/dream/gpio_axis.c:124: error: 'GPIO_EVENT_FUNC_RESUME' undeclared (first use in this function) drivers/staging/dream/gpio_axis.c:125: error: dereferencing pointer to incomplete type drivers/staging/dream/gpio_axis.c:126: error: dereferencing pointer to incomplete type drivers/staging/dream/gpio_axis.c:130: error: 'GPIO_EVENT_FUNC_INIT' undeclared (first use in this function) drivers/staging/dream/gpio_axis.c:139: error: implicit declaration of function 'input_set_capability' drivers/staging/dream/gpio_axis.c:139: error: dereferencing pointer to incomplete type drivers/staging/dream/gpio_axis.c:139: error: dereferencing pointer to incomplete type drivers/staging/dream/gpio_axis.c:140: error: dereferencing pointer to incomplete type drivers/staging/dream/gpio_axis.c:140: error: 'EV_ABS' undeclared (first use in this function) drivers/staging/dream/gpio_axis.c:140: error: dereferencing pointer to incomplete type drivers/staging/dream/gpio_axis.c:140: error: dereferencing pointer to incomplete type drivers/staging/dream/gpio_axis.c:141: error: implicit declaration of function 'input_set_abs_params' drivers/staging/dream/gpio_axis.c:141: error: dereferencing pointer to incomplete type drivers/staging/dream/gpio_axis.c:142: error: dereferencing pointer to incomplete type drivers/staging/dream/gpio_axis.c:144: error: dereferencing pointer to incomplete type drivers/staging/dream/gpio_axis.c:145: error: dereferencing pointer to incomplete type drivers/staging/dream/gpio_axis.c:148: error: dereferencing pointer to incomplete type drivers/staging/dream/gpio_axis.c:151: error: dereferencing pointer to incomplete type drivers/staging/dream/gpio_axis.c:167: error: dereferencing pointer to incomplete type drivers/staging/dream/gpio_axis.c:168: error: dereferencing pointer to incomplete type drivers/staging/dream/gpio_axis.c:172: error: dereferencing pointer to incomplete type make[4]: *** [drivers/staging/dream/gpio_axis.o] Error 1 make[3]: *** [drivers/staging/dream] Error 2 config attached. --- ~Randy LPC 2009, Sept. 23-25, Portland, Oregon http://linuxplumbersconf.org/2009/
From: Pavel Machek on 11 Sep 2009 03:20 Hi! > > > With 2.6.31 being closer... is there a git tree or set of patches to > > > make it boot on HTC Dream? > > > > > > Quite a lot of hw should be supported in linux-next, and it would be > > > nice to get arch-specific code working with linux-next and eventually > > > merged... > > > > Any news here? If you need some more kernel hackers I guess I'm > > looking for a job :-). > > well, mmotm and linux-next dream builds fail like this: Ok, is the goal here to get it to compile, or get it to boot? I have recent tree that compiles, somewhere, but getting it to boot is 'slightly more interesting'. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Randy Dunlap on 11 Sep 2009 11:00 On Fri, 11 Sep 2009 09:16:16 +0200 Pavel Machek wrote: > Hi! > > > > > With 2.6.31 being closer... is there a git tree or set of patches to > > > > make it boot on HTC Dream? > > > > > > > > Quite a lot of hw should be supported in linux-next, and it would be > > > > nice to get arch-specific code working with linux-next and eventually > > > > merged... > > > > > > Any news here? If you need some more kernel hackers I guess I'm > > > looking for a job :-). > > > > well, mmotm and linux-next dream builds fail like this: > > Ok, is the goal here to get it to compile, or get it to boot? Can you do b. (boot) without a. (compile)? > I have recent tree that compiles, somewhere, but getting it to boot is > 'slightly more interesting'. Sure, booting is more interesting. Especially if one has the device. --- ~Randy LPC 2009, Sept. 23-25, Portland, Oregon http://linuxplumbersconf.org/2009/ -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Pavel Machek on 11 Sep 2009 12:20 Hi! > > > > > With 2.6.31 being closer... is there a git tree or set of patches to > > > > > make it boot on HTC Dream? > > > > > > > > > > Quite a lot of hw should be supported in linux-next, and it would be > > > > > nice to get arch-specific code working with linux-next and eventually > > > > > merged... > > > > > > > > Any news here? If you need some more kernel hackers I guess I'm > > > > looking for a job :-). > > > > > > well, mmotm and linux-next dream builds fail like this: > > > > Ok, is the goal here to get it to compile, or get it to boot? > > Can you do b. (boot) without a. (compile)? Well, hardly, but I can do a) without b), and it is very much easier. So... which is it? > > I have recent tree that compiles, somewhere, but getting it to boot is > > 'slightly more interesting'. > > Sure, booting is more interesting. Especially if one has the device. Do you have one? Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Randy Dunlap on 11 Sep 2009 12:30
On Fri, 11 Sep 2009 18:13:35 +0200 Pavel Machek wrote: > Hi! > > > > > > > With 2.6.31 being closer... is there a git tree or set of patches to > > > > > > make it boot on HTC Dream? > > > > > > > > > > > > Quite a lot of hw should be supported in linux-next, and it would be > > > > > > nice to get arch-specific code working with linux-next and eventually > > > > > > merged... > > > > > > > > > > Any news here? If you need some more kernel hackers I guess I'm > > > > > looking for a job :-). > > > > > > > > well, mmotm and linux-next dream builds fail like this: > > > > > > Ok, is the goal here to get it to compile, or get it to boot? > > > > Can you do b. (boot) without a. (compile)? > > Well, hardly, but I can do a) without b), and it is very much > easier. So... which is it? I'm only targeting compile/build. > > > I have recent tree that compiles, somewhere, but getting it to boot is > > > 'slightly more interesting'. > > > > Sure, booting is more interesting. Especially if one has the device. > > Do you have one? Nope. Hence compile/build. --- ~Randy LPC 2009, Sept. 23-25, Portland, Oregon http://linuxplumbersconf.org/2009/ -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |