Re: newbie needs help with modules

[Michel <dae...@st...>]

Giorgio Terzi wrote:
> 
> fh...@at... wrote:
> 
> > I decided to try developing my driver projects as modules in order to save
> > reboot cycles.  When I do this, trying to follow the module programming
> > advice I got, I get unresolved symbols.  How do I get rid of these?  These
> > symbols appear to be routines burried in the kernel various places.
> >
> > The Hypercom4+ module:
> >
> > ser_hypercom4.o: unresolved symbol queue_task
> > ser_hypercom4.o: unresolved symbol mark_bh
> > ser_hypercom4.o: unresolved symbol __restore_flags
> > ser_hypercom4.o: unresolved symbol unregister_serial
> > ser_hypercom4.o: unresolved symbol register_serial
> >
> > Fred
> >
> 
> I can only answer for serial driver's code:
> With IOBlix driver i found a similar problem with register_serial()
> & unregister_serial() functions.
> I used m68k_register_serial() & m68k_unregister_serial() instead,
> interfacing myself with Roman Hodek's m68kserial driver and the problem
> was solved.

This may be a quick fix for that problem, however AFAIK the m68kserial isn't
accepted by Linus and isn't in the native tree nor our 2.4 tree, which should
really be our primary development target now. There's a new amiga serial
driver - amiserial.c - in 2.4 .


I'd like to have mainly only bug fixes (apart from the upgrade to 2.2.16, if
anyone really wants to do that...) in the 2.2 tree from now on.


Michel


-- 
Men are from Earth. Women are from Earth. Deal with it.
______________________________________________________________________________
Earthling Michel Dänzer (MrCooper)  \  CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \   member of XFree86, Team *AMIGA*, AUGS