Date: Thu, 16 Mar 2006 16:57:00 +0300 From: Artem 'ZaZooBred' Ignatiev <zazubrik@mail.ru> To: freebsd-hackers@freebsd.org Subject: Re: newbus questions Message-ID: <1142517420.36931.58.camel@timon> In-Reply-To: <1142510785.36931.43.camel@timon> References: <1142506792.36931.25.camel@timon> <200603161235.24124.hackers@dino.sk> <1142510785.36931.43.camel@timon>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 16/03/2006 at 15:06 +0300, Artem 'ZaZooBred' Ignatiev wrote: .... > Yes, I've got some clearance in how that <something>_if.m files are > written, but bktr driver is too complex for me to understand how the > things are done right now. I'll look at it again, though, maybe I could > understand the logic of how such things are done, when I could clearly > separate generic logic from implementation of particular hardware > driver. > Looks like I'm totally newbie there. I've created small saa_if.m file, with CODE section, declaring two small debug functions, and two METHODS, DEFAULTing to that functions. Now I want to update Makefile so that typing ``make depend'' will produce .c and .h from the .m file. Looks like /sys/conf/kmod.mk lists all .m files by name, and deals with them on one-by-one basis, so I must manually insert all that awk -f ... invocations for these targets, am I right? Or had I overlooked feature of automated codegeneration just in Makefile? P.S. I suppose, that it's worth to create some useful doc with skeleton bus driver, one dummy method, and child driver overriding that method. (As to me, the latest task is the easiest, at least I know how to do this, e.g., PCI device overriding probe method). P.P.S Hey, that's my birthday! So I would like a toast to all BSD developers, core team and hackers
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1142517420.36931.58.camel>