Date: Sun, 18 Sep 2011 04:06:43 +0700 From: Eugene Grosbein <egrosbein@rdtc.ru> To: pyunyh@gmail.com Cc: stable@freebsd.org Subject: Re: busdma MFC broke ipfw fwd for RELENG_6 Message-ID: <4E750BE3.7020607@rdtc.ru> In-Reply-To: <20110917202236.GB13993@michelle.cdnetworks.com> References: <201109151314.50549.jhb@freebsd.org> <4E7238C3.1060008@rdtc.ru> <20110915181524.GA6557@michelle.cdnetworks.com> <4E724BCD.4040607@rdtc.ru> <20110915191944.GB6557@michelle.cdnetworks.com> <4E72D465.8050900@rdtc.ru> <20110916191355.GA9916@michelle.cdnetworks.com> <4E74A8C6.2070608@rdtc.ru> <20110917200508.GA13993@michelle.cdnetworks.com> <4E74FF02.7070607@rdtc.ru> <20110917202236.GB13993@michelle.cdnetworks.com>
next in thread | previous in thread | raw e-mail | index | archive | help
18.09.2011 03:22, YongHyeon PYUN пишет: >>> Glad to hear that. Unfortunately I have no plan or time to merge >>> all changes made in re(4)/rl(4) to stable/6 so you may have to >>> stick to this unofficial driver. As you already know, I overhauled >>> these drivers long time ago and there were too many changes. >> >> Well, given that before busdma commit that hardware worked just fine with stock driver, >> it could be less overhead for me to rollback that one busdma small chunk :-) >> Who knows, which drivers got broken then in 2010 in 6.4-STABLE with busdma change besides re(4)... > > I agree but that MFC may have fixed bugs in other driver which > correctly used bus_dma(9) KPI. It is possible. With luck, this legacy 6.4-STABLE system runs rock-stable and have no other problems with drivers/ Thanks for your drivers backport, anyway, now this case is closed :-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E750BE3.7020607>