https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225325
aaron.s...@baesystems.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #189913|0 |1
is obsolete| |
--- Comment #3 from aaron.s...@baesystems.com ---
Created attachment 189996
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=189996&action=edit
/var/log/messages re1 output
After submitting the bug, I did some digging and saw how common this chip is,
so I would agree that simply forcing all of them to use IO mapped registers is
not the right solution. The attached is the relevant output of
/var/log/messages. (Note that this is from a 10.1 Live CD).
I clearly need to do some more testing with this. I'll try this card in a
different machine, and I'd also like to compile with RE_DIAG to see if this is
simply a known problem with this device, but that will take me a bit. I'm not
sure if the 10.1 live cd build is compiled with this or not...
As for the meaning of "doesn't work," I'm able to set the address and bring the
device up with ifconfig, which reports the device is up and active. However,
any attempts to ping another host on the network results in 'sendto: Host is
down.' Wireshark shows no packets coming from the 1869 re device.
Other network devices on this machine work as expected, so I know it's not a
network issue. Setting hw.re.prefer_iomap=1 also works. The device works on
Linux in this machine, though I haven't taken a close look at their driver yet,
or figured out if they're using Memory or IO mapped registers.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
