This was cleaned up into commit https://github.com/ipxe/ipxe/commit/2d79b20f2
--
Reply to this email directly or view it on GitHub:
https://github.com/ipxe/ipxe/pull/52#issuecomment-1036448623
You are receiving this because you commented.
Message ID:
Closed #52.
--
Reply to this email directly or view it on GitHub:
https://github.com/ipxe/ipxe/pull/52#event-6052904769
You are receiving this because you commented.
Message ID: ___
ipxe-devel mailing list
ipxe-devel@lists.ipxe.org
Is this still an issue in current master?
--
Reply to this email directly or view it on GitHub:
https://github.com/ipxe/ipxe/pull/52#issuecomment-1036405097
You are receiving this because you commented.
Message ID: ___
ipxe-devel mailing list
@olivernie pushed 1 commit.
5425c7d59e58c74e7834cf83c1c16d9a2da8901d Merge branch 'master' into master
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
@robinsmidsrod I got another board which has two NICs. Net0 is using intel
82567lm, net1 is using intel 82576eb. My patch is on 82576eb. Following are the
results on loopback tests. Enabled debugging level 3 for intel and netdevice.
The failed case shows 1 packet transmitted but nothing
@olivernie Thanks for the test feedback. The loopback tests are most of the
time tested with two NICs in the same system, with one being the one under test
and the other one a known working NIC. This ensures that there is no packet
drop in the receive and transmit data paths and that VLAN
OK. Here are results of [ipxe.org/dev/driver](ipxe.org/dev/driver)
- Link detection--- Pass
- Basic DHCP --- Pass
- Close and reopen --- Pass
- Large file transfer correctness --- Pass
- Large file transfer speed
Ok. I will take a look at ipxe.org/dev/driver to see how to run those tests.
Update the result later.
---
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
It would be beneficial if you provide the results from the tests located at
ipxe.org/dev/driver both with and without the provided patch, so that it is
clear what this patch fixes.
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on
Yes. In my board, intel 82576EB is connected to BCM8359(copper on board). The
builtin PXE in NIC can DHCP and load the IPXE binary from server. But IPXE
can't even the ifstat shows link is up. This patch fix this bug. IPXE could
DHCP again and chainload the other image.
---
You are receiving
Does this fix an actual problem, or is it just for datasheet compliance? From
what I can remember, we try to avoid flags on new drivers unless absolutely
required (usually for strange hardware issues/bugs).
---
You are receiving this because you are subscribed to this thread.
Reply to this
Bit CTRL_ASDE is reserved and must be set to 0b according intel 82576EB
datasheet.
You can view, comment on, or merge this pull request online at:
https://github.com/ipxe/ipxe/pull/52
-- Commit Summary --
* Fixed bug in intel 10M/100M/1G NIC driver. bit CTRL_ASDE is reserved and
must be
12 matches
Mail list logo
