11:10 <mtrbot-ml> [mattermost] <sb10q> @astro is zc706/build.rs still used?

11:10 <mtrbot-ml> [mattermost] <sb10q> thanks for fixing the build

11:20 <mtrbot-ml> [mattermost] <sb10q> @astro you have not tried running code from the DDR yet, correct?

11:20 <mtrbot-ml> [mattermost] <sb10q> only OCM?

13:29 <mtrbot-ml> [mattermost] <sb10q> @astro why does println! sends two carriage-return to the UART instead of one?

13:29 <mtrbot-ml> [mattermost] <sb10q> @astro why does println! send two carriage-returns to the UART instead of one?

13:43 <mtrbot-ml> [mattermost] <sb10q> @astro what is the purpose of the call to libboard_zynq::stdio::drop_uart on zc706 in experiments/main.rs?

14:06 <mtrbot-ml> [mattermost] <sb10q> @astro you probably guessed it, but we need to use sockets and the mailbox at the same time

14:06 <mtrbot-ml> [mattermost] <sb10q> so Sockets::run() as main loop seems inappropriate

14:21 <mtrbot-ml> [mattermost] <sb10q> "eth: got Link { speed: S1000, duplex: Half }" << why does it say "duplex: Half"?

23:05 <mtrbot-ml> [mattermost] <astro> the uart driver is lazy-initialized on the 1st println!() but must be re-initialized after clock setup

23:07 <mtrbot-ml> [mattermost] <astro> right. we could load it into DDR which has been setup by ps7_init.tcl. if we manage to configure it ourselves (not yet there) we would need to break the firmware into two stages.

23:09 <mtrbot-ml> [mattermost] <astro> build.rs moves the linker script into the build directory.

23:11 <mtrbot-ml> [mattermost] <astro> the PHY has always reporting half duplex for me. but it has been a while and I will look into that again.

23:13 <mtrbot-ml> [mattermost] <astro> I agree that this is an ugly part of the interface. perhaps that should just be another never terminating future to poll() on...