Date: Sat, 27 Aug 2011 10:35:16 +0200 From: Eric Masson <emss@free.fr> To: Slawa Olhovchenkov <slw@zxy.spb.ru> Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, Doug Barton <dougb@FreeBSD.org>, src-committers@freebsd.org, John Baldwin <jhb@FreeBSD.org> Subject: Re: svn commit: r225201 - in head/sys: amd64/conf i386/conf Message-ID: <86obzbi75n.fsf@srvbsdfenssv.interne.associated-bears.org> In-Reply-To: <20110827081103.GB21676@zxy.spb.ru> (Slawa Olhovchenkov's message of "Sat, 27 Aug 2011 12:11:03 %2B0400") References: <201108262122.p7QLMZXW071323@svn.freebsd.org> <4E583B92.3060100@FreeBSD.org> <20110827081103.GB21676@zxy.spb.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
Slawa Olhovchenkov <slw@zxy.spb.ru> writes: Hello, > Yes, from FreeBSD 6.x puc.ko don't work. Only in-kernel version work. Nope puc.ko module can't attach drivers compiled in kernel, but if both puc & uart are loaded as modules, they work fine : emss@srvbsdfenssv:~> uname -mr 8.2-RELEASE-p2 amd64 emss@srvbsdfenssv:~> kldstat Id Refs Address Size Name 1 149 0xffffffff80100000 777090 kernel 2 2 0xffffffff80878000 8580 procfs.ko 3 3 0xffffffff80881000 94e0 pseudofs.ko 4 1 0xffffffff8088b000 bc28 geom_label.ko 5 2 0xffffffff80897000 4d110 pf.ko 6 1 0xffffffff808e5000 fef8 if_nfe.ko 7 2 0xffffffff808f5000 3dc80 miibus.ko 8 1 0xffffffff80933000 24d78 snd_hda.ko 9 2 0xffffffff80958000 757c8 sound.ko 10 1 0xffffffff809ce000 8ce8 umass.ko 11 7 0xffffffff809d7000 356f0 usb.ko 12 3 0xffffffff80a0d000 820c8 cam.ko 13 1 0xffffffff80a90000 f060 aio.ko 14 1 0xffffffff80aa0000 15e0 accf_http.ko 15 1 0xffffffff80aa2000 a6a8 puc.ko 16 1 0xffffffff80aad000 27d0 amdtemp.ko 17 1 0xffffffff80ab0000 10078 ahci.ko 18 1 0xffffffff80ac1000 18510 uart.ko 19 1 0xffffffff80ada000 8c70 ppc.ko 20 3 0xffffffff80ae3000 9948 ppbus.ko 21 1 0xffffffff80aed000 47e0 lpt.ko 22 1 0xffffffff80af2000 9ff8 ohci.ko 23 1 0xffffffff80afc000 d288 ehci.ko 24 1 0xffffffff80b0a000 38a8 uftdi.ko 25 2 0xffffffff80b0e000 5688 ucom.ko 26 1 0xffffffff80b14000 2450 pflog.ko 27 1 0xffffffff80b17000 4a30 cryptodev.ko 28 2 0xffffffff80b1c000 2fb70 crypto.ko 29 3 0xffffffff80b4c000 dc00 zlib.ko 30 1 0xffffffff80b5a000 4cc0 nfsmb.ko 31 3 0xffffffff80b5f000 24c0 smbus.ko 32 1 0xffffffff80b62000 2d28 smb.ko 33 1 0xffffffff80b65000 82e8 ng_ubt.ko 34 3 0xffffffff80b6e000 14de8 netgraph.ko 35 2 0xffffffff80b83000 12fc0 ng_hci.ko 36 2 0xffffffff80b96000 2da0 ng_bluetooth.ko 37 1 0xffffffff80c22000 3e80 linprocfs.ko 38 1 0xffffffff80c26000 1cf64 linux.ko emss@srvbsdfenssv:~> dmesg | grep puc puc0: <Oxford Semiconductor OX16PCI954 UARTs> port 0xd480-0xd49f,0xd400-0xd41f mem 0xfcffe000-0xfcffefff,0xfcffd000-0xfcffdfff irq 18 at device 7.0 on pci1 puc0: [FILTER] uart2: <16550 or compatible> on puc0 uart3: <16550 or compatible> on puc0 uart4: <16550 or compatible> on puc0 uart5: <16550 or compatible> on puc0 So including puc in GENERIC is the only solution as uart & ppc are already in. The other way could be to ship a stripped down GENERIC kernel and load modules manually or automagically (devd ?) Regards Éric Masson -- > Subject: pb fvwm95-2 comment l'installer le compiler??? > Merci d'avance je te conseille d'être un peu plus précis dans l'exposé de ton pb... -+- EJ in guide du linuxien pervers :"Les modéros sont sympas !" -+-
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86obzbi75n.fsf>