On Thursday 06 October 2005 07:21 am, Milan Obuch wrote: > While working on ACCESS.bus support for Geode based WRAP boards I run into > some linker issue. As Geode's controller is full hardware implementation, I > used pcf as a template, sort of. > > After I put my base module infrastructure together and began work with > actual hardware functions and iicbus interface, my module no longer > kldloaded. > > Then I checked pcf module and found the same behavior. If you have no > 'device iicbus' in kernel configuration, issuing 'kldload pcf' gives > link_elf: symbol iicbus_intr undefined > kldload: can't load pcf: No such file or directory. > > Adding 'device iibus' into kernel configuration and rebuilding kernel fixes > this, so it looks like symbol is just not exported. > > As I am using module for development and resulting code will be built in > kernel in application platform (most probably), it is not big issue to me. > I use found work-around. It would be just nice to get this fixed. > > Anyway, is anybody out there using pcf? There is some work done in this > area, but not yet linked into main tree. I have not pcf hardware, so I can > not test anything in this area, but it would be good to make the transition > from older i386/isa/pcf.c to new dev/pcf/... Sounds like it is missing a 'MODULE_DEPEND(iicbus, 1, 1, 1);' line. Can you try adding one and seeing if it fixes the kldload of pcf? -- John Baldwin <jhb_at_FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.orgReceived on Thu Oct 13 2005 - 18:14:54 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:45 UTC