From: Johann D. <jo...@do...> - 2002-04-11 08:24:01
|
Rodrigo Damazio wrote: > Johann Deneux wrote: > >> Rodrigo Damazio wrote: >> >>> [...] btw, I'm attaching a few minor but necessary fixes to >>> linux-console 2.5.7 code...also on line 749 of hid-core.c, you forgot >>> to change the parameters to hiddev_hid_event...I'm not exactly sure >>> how it expects the uref struct to be populated, so I'm leaving that >>> one to you... >>> >> >> Neither do I. I will in turn leave this one to James. > > > Seems like he corrected it already =c) > Well, I actually fixed it after sending the mail (which never reached the list anyway, because of a mistyped address). The point is that it seems we are having several versions of the hid code. The version in Greg KH tree contained the right code. I hope Dave Jones, Linus, Greg and us are not going to end up with different versions. I fear the same problem applies to the rest of the code in our CVS. >> >>> ------------------------------------------------------------------------ >>> >>> diff -ru ruby/linux/drivers/char/consolemap.c >>> linux/drivers/char/consolemap.c >>> --- ruby/linux/drivers/char/consolemap.c Wed Mar 7 01:42:27 2001 >>> +++ linux/drivers/char/consolemap.c Mon Apr 8 18:17:22 2002 >>> @@ -397,7 +397,7 @@ >>> >>> extern u8 dfont_unicount[]; /* Defined in consolemap_deftbl.c */ >>> extern u16 dfont_unitable[]; >>> -extern u16 dfont_num; >>> +u16 dfont_num; >> >> >> >> This one shouldn't be necessary. dfont_num is indeed defined in >> consolemap_deftbl.c (a file generated by conmakehash). > > > I see...but for some reason it would compile, but at link time > it'd complain about not finding that symbol... > Are we using the same kernel version ? I do have link-time errors too, but not the same ones. In my case, handle_scancode isn't defined in any object linked to bzImage. I was using Linus' 2.5.7 with files from the linuxconsole CVS in this attempt. -- Johann Deneux |