Re: HEADS UP; new options for -current!
-On [2319 21:00], Poul-Henning Kamp ([EMAIL PROTECTED]) wrote: In message [EMAIL PROTECTED], Peter Wemm writes : If you are using old drivers that haven't been newbusified yet, you will need to add 'options COMPAT_OLDPCI' and/or 'options COMPAT_OLDISA' to your kernel configs and regenerate. Otherwise you will get compile failures. I think this is premature. I tried to newbusify if_mn.c, but after having added about 50 lines of code to replace the current about 10, I gave up. We need a highlevel wrapper for newbus before we should force people to upgrade the old-style drivers. I already addressed that in new-bus and there is some discussion and finding out the best way to do a higher level wrapping for a lot of newbus' stuff. So rest assured, work is underway. =) -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED] VIA NET.WORKS The Netherlands BSD: Technical excellence at its best http://www.bart.nl The mediocre teacher tells, the good teacher explains, the superior teacher demonstrates, the great teacher inspires... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP; new options for -current!
Jeroen Ruigrok van der Werven wrote: I already addressed that in new-bus and there is some discussion and finding out the best way to do a higher level wrapping for a lot of newbus' stuff. Is there? Where? I don't recall seeing that in any of the newbus mailing lists I (used to) subscribe to. -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone bind them. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
HEADS UP; new options for -current!
If you are using old drivers that haven't been newbusified yet, you will need to add 'options COMPAT_OLDPCI' and/or 'options COMPAT_OLDISA' to your kernel configs and regenerate. Otherwise you will get compile failures. This is for -current only. 4.x is not affected. Incidently, I was encouraged to break the shims rather than put an option around them, but that was too drastic for now. This won't be happening in 4.x so be sure to consider which codebase you want to be running. Remember, -current is going to get rather bumpy soon once merges start happening.. -Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP; new options for -current!
In message [EMAIL PROTECTED], Peter Wemm writes : If you are using old drivers that haven't been newbusified yet, you will need to add 'options COMPAT_OLDPCI' and/or 'options COMPAT_OLDISA' to your kernel configs and regenerate. Otherwise you will get compile failures. I think this is premature. I tried to newbusify if_mn.c, but after having added about 50 lines of code to replace the current about 10, I gave up. We need a highlevel wrapper for newbus before we should force people to upgrade the old-style drivers. -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
