Date: Mon, 21 May 2007 21:34:21 -0700 From: "Kip Macy" <kip.macy@gmail.com> To: Brad <brad@comstyle.com> Cc: freebsd-net <freebsd-net@freebsd.org>, Jack Vogel <jfvogel@gmail.com> Subject: Re: Is em endian-clean? Message-ID: <b1fa29170705212134k33164593p7d82cb857af8591f@mail.gmail.com> In-Reply-To: <20070522003246.0f5de4b2@booyah.home.comstyle.com> References: <b1fa29170705212059q5895428dk6c4946d4bf47192d@mail.gmail.com> <20070522003246.0f5de4b2@booyah.home.comstyle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Ours did too prior to the recent import :D On 5/21/07, Brad <brad@comstyle.com> wrote: > On Mon, 21 May 2007 20:59:15 -0700 > "Kip Macy" <kip.macy@gmail.com> wrote: > > > Hi Jack - > > I believe I've fixed the sun4v breakage caused by the interrupt filter > > changes but it appears that em still isn't working. Does Intel test at > > all on big endian hardware? If not, what do you do to avoid breaking > > e1000 on Linux? > > > > Thanks. > > > > -Kip > > I cannot comment about FreeBSD, but the em(4) driver in OpenBSD works > on macppc, sparc64, hppa and most likely sgi as well. >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b1fa29170705212134k33164593p7d82cb857af8591f>