Brian, 1. Does it mean I now have to append _RP before my mod_open(), mod_close() and other functions from my driver which I use to populate qinit structure in the same manner as LiS 2.18 does it before connld_open?
Like if 2.18 does: static int _RP connld_open(queue_t *, dev_t*, int, int, cred_t *); should I also do : int _RP mymod_open(...); ? 2. LiS does a good job of finding CC compilation options based on info extracted from kernel and other sources. When I compile my module for LiS I apparently need to use exactly the same CC options that LiS has already found and used. Is there any elegant way to 'steal' this CC options from LiS so that I will not need to get into a trouble of finding them from the kernel and sources again? LiS could save them somewhere, so that I could take and use them? thanks for your comments, -- Eugene "Brian F. G. Bidulock" <[EMAIL PROTECTED]> wrote: >EugeneLisStreams, >Sometimes >#define _RP __attribute__((regparm(3))) >othertimes >#define _RP __________________________________________________________________ Switch to Netscape Internet Service. As low as $9.95 a month -- Sign up today at http://isp.netscape.com/register Netscape. Just the Net You Need. New! Netscape Toolbar for Internet Explorer Search from anywhere on the Web and block those annoying pop-ups. Download now at http://channels.netscape.com/ns/search/install.jsp _______________________________________________ Linux-streams mailing list [email protected] http://gsyc.escet.urjc.es/mailman/listinfo/linux-streams
