On Mon, Mar 19, 2007 at 05:53:10PM +0200, Danny Braniss wrote:
> I compiled the latest -current, with the latest nfe, and I got a slight
> regression :-)
> ...
> nfe0: port 0xdc00-0xdc07 mem
> 0xfe02c000-0xfe02cfff irq 21 at device 20.0 on pci0
> nfe0: Ethernet address: 50:71:a9:f3:18:00
I compiled the latest -current, with the latest nfe, and I got a slight
regression :-)
...
nfe0: port 0xdc00-0xdc07 mem
0xfe02c000-0xfe02cfff irq 21 at device 20.0 on pci0
nfe0: Ethernet address: 50:71:a9:f3:18:00
nfe0: MII without any phy!
kernel trap 12 with interrupts disabled
Fatal trap 12
On Fri, Mar 16, 2007 at 06:55:00PM +0200, Andriy Gapon wrote:
>
> I am wondering what is the purpose of the following pieces of code in
> if_nve.c:
>
> /* ... nve_attach ... */
> /* MAC is loaded backwards into h/w reg */
> sc->hwapi->pfnGetNodeAddress(sc->hwapi->pADCX, sc->origi
on 19/03/2007 12:24 Pyun YongHyeon said the following:
>
> Unlike other MCP hardwares, MCP61/MCP65/MCP67 stores ethernet address
> in-order. nve(4)/nfe(4) should not swap ethernet address on these
> hardwares. Peer Chen at NVIDIA and Shigeaki Tagashira sent me patches
> to the issue and I've updat
>
> I am wondering what is the purpose of the following pieces of code in
> if_nve.c:
>
> /* ... nve_attach ... */
> /* MAC is loaded backwards into h/w reg */
> sc->hwapi->pfnGetNodeAddress(sc->hwapi->pADCX, sc->original_mac_addr);
> for (i = 0; i < 6; i++) {
> ea
I am wondering what is the purpose of the following pieces of code in
if_nve.c:
/* ... nve_attach ... */
/* MAC is loaded backwards into h/w reg */
sc->hwapi->pfnGetNodeAddress(sc->hwapi->pADCX, sc->original_mac_addr);
for (i = 0; i < 6; i++) {
eaddr[i] = s
6 matches
Mail list logo