Date: Fri, 7 Apr 2017 15:15:43 +0200 From: =?UTF-8?B?xYF1a2FzeiBXw7NqY2lr?= <lukasz.wojcik@zoho.com> To: freebsd-net@freebsd.org Subject: Re: Impending NATM removal Message-ID: <e1e91d07-b7c6-1f88-16ff-2fd12feb42b6@zoho.com> In-Reply-To: <efa21bbe-1a87-6cf4-13e7-604df3da1d21@zoho.com> References: <20170406235747.GA8756@spindle.one-eyed-alien.net> <efa21bbe-1a87-6cf4-13e7-604df3da1d21@zoho.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Oh, and mbpool DMA syncing does not work at all and -- at least in patm driver -- causes various issues. This of course can be easily worked around if you choose to let ATM ecosystem stay. If my client agrees, I could also share a patch for patm to make it work with newer ProSUM hardware. -ŁW On 07-Apr-17 15:08, Łukasz Wójcik wrote: > Hi Brooks, > > > AFAIK Prosum still manufactures PROATM155M card that utilizes patm > driver (which is by the way a little bit outdated and does > > not support newer variants of ProSUM cards). I also have clients that > still use ATM and prosum cards and FreeBSD. My guess is that > > they're not the only ones. Just my 5cents. The other thing is that > ATM/NATM infrastructure in FreeBSD seems to never have been > > finished. > > > Thanks > > -ŁW > > > On 07-Apr-17 01:57, Brooks Davis wrote: >> As previously threatened, I plan to remove NATM support next week. This >> includes the drivers en(4), fatm(4), hatm(4), and patm(4). None of >> these devices have been manufactured in the last 20 years so it is time >> to move on. >> >> The planned commit can be seen at https://reviews.freebsd.org/D9883 >> >> -- Brooks > > > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e1e91d07-b7c6-1f88-16ff-2fd12feb42b6>