Re: 'miibus_if.h' file missing for 'dc' ethernet driver
In message [EMAIL PROTECTED], attila! writes: ../../pci/if_dc.c:151: miibus_if.h: No such file or directory mkdep: compile failed 'find' on entire sys subsystem fails to show it, and I pulled cvsups on 19th and 20th to see if it was in the stream --nope. pulled a 'glimpse' of 'current' list but found no reference. This file is generated on the fly in the compile directory I belive. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 'miibus_if.h' file missing for 'dc' ethernet driver
attila! wrote: ../../pci/if_dc.c:151: miibus_if.h: No such file or directory mkdep: compile failed 'find' on entire sys subsystem fails to show it, and I pulled cvsups on 19th and 20th to see if it was in the stream --nope. pulled a 'glimpse' of 'current' list but found no reference. I suspect that you are missing 'device miibus' in your kernel config file... Cheers, -Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 'miibus_if.h' file missing for 'dc' ethernet driver
solved. thanx! LINT added an explanation of the miibus driver requirement. I did the basic configuration from the 17 Apr LINT file and missed the change when I updated, even though I diff LINT when it updates. see diff below. As they say: RTFS...carefully. attila out! -- No, I don't suffer from insanity; I enjoy every minute of it! is LINT prior to 18 Apr is LINT after 18 Apr which tells you WHY you need 'miibus' 168d1823 devicemiibus # MII bus support 179,218c1834,2227 # MII bus support is required for some PCI 10/100 ethernet NICs, # namely those which use MII-compliant transceivers or implement # tranceiver control interfaces that operate like an MII. Adding # "device miibus0" to the kernel config pulls in support for # the generic miibus API and all of the PHY drivers, including a # generic one for PHYs that aren't specifically handled by an # individual driver. devicemiibus on Wed, 19 Apr 2000 23:18:08 -0700 (PDT), Jaye Mathisen: You need the device mii or miibus in your kernel config file, and I think it generates it. Look at a GENERIC near the dc driver in the later releases, and you'll see it added, or grep for mii in LINT/GENERIC. On Thu, 20 Apr 2000, attila! wrote: ../../pci/if_dc.c:151: miibus_if.h: No such file or directory mkdep: compile failed 'find' on entire sys subsystem fails to show it, and I pulled cvsups on 19th and 20th to see if it was in the stream --nope. pulled a 'glimpse' of 'current' list but found no reference. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 'miibus_if.h' file missing for 'dc' ethernet driver
-On [2420 08:49], attila! ([EMAIL PROTECTED]) wrote: ../../pci/if_dc.c:151: miibus_if.h: No such file or directory mkdep: compile failed 'find' on entire sys subsystem fails to show it, and I pulled cvsups on 19th and 20th to see if it was in the stream --nope. pulled a 'glimpse' of 'current' list but found no reference. You _did_ add device miibus to the kernel config file did you? -- Jeroen Ruigrok vd Werven/Asmodaiasmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Answering the questions that no one asks... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
