> I'm just suggesting here that it would be nice if the authors of > this code would make it _equally functional_ to what was removed. > It's not nice to remove functionality unconditionally and then > provide no replacement at all... That work is underway, and something to understand about -current is that it doesn't have to actually work at all times during the interim periods between releases. Now, should 4.0 be on the horizon and the situation still be one where "equivalent functionality" has not been provided by the newpcm driver, we'll revert back to the original luigi driver and continue the experiment in the new post-branch (5.0) current. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
- Wierd su problem still ther... Adam Strohl
- Re: Wierd su problem still ... Benjamin Lewis
- Re: Wierd su problem still ... Adam Strohl
- Re: Loss of Functionality w... Alex Perel
- Re: Loss of Functionality w... Alok K. Dhir
- Re: Loss of Functionality w... Donald J . Maddox
- Re: Loss of Functionality w... Doug Rabson
- Re: Loss of Functionality w... Amancio Hasty
- Re: Loss of Functionality w... Doug Rabson
- Re: Loss of Functionality w... Donald J . Maddox
- Re: Loss of Functionality with newpnp Jordan K. Hubbard
- Re: Loss of Functionality with newpnp Rodney W. Grimes
- Re: Loss of Functionality with newpn... Jordan K. Hubbard
- Re: Loss of Functionality with ... Rodney W. Grimes
- Re: Loss of Functionality with newpn... Daniel C. Sobral
- Re: Loss of Functionality with newpn... Warner Losh
- Re: Loss of Functionality with ... Daniel C. Sobral
- Re: Loss of Functionality w... Mike Smith
- Re: Loss of Functionality w... Michael Reifenberger
- Re: Loss of Functionality with ... Warner Losh
- Re: Loss of Functionality with newpnp D. Rock