On Oct 14, 2010, at 10:22 PM, David MacMahon wrote:
> I can happily confirm that the current version of mlib_devel (ever since
> commit e7c407c) in the git repo can indeed successfully create bof files that
> work with the BEE2 using the Xilinx 10.1 tools.
Technically, it's since commit 87070e
Hi, Jack,
On Oct 14, 2010, at 10:02 PM, Jack Hickish wrote:
> I remember an issue with borph hanging on read/writes, which the mail archive
> suggests you may have solved. Could you just confirm -- does the current
> version of 10.1 in the git repo successfully create bof files that work with
Hi Dave,
I remember an issue with borph hanging on read/writes, which the mail
archive suggests you may have solved. Could you just confirm -- does the
current version of 10.1 in the git repo successfully create bof files that
work with the BEE2?
Cheers,
Jack
On 14 October 2010 12:09, David Ma
Hey Jonathan,
Here's an article with another price point for you:
http://www.hpcwire.com/offthewire/BLADE-Unveils-Single-Chip-40GbE-Switch-104948929.html?viewAll=y
"$350 per 10GbE port with 40GbE connectivity at just $1,400 per port."
Cheers,
Dave
On 10/12/2010 10:09 AM, Dan Werthimer wrote:
Dear Casper,
We recently upgraded to the newest version of tcpborphserver
(tcpborphserver-2.3304 2010-08-27) and have discovered that we can no
longer write to DRAM. Specifically, tcpborphserver crashes on the roach
when we try to use the Python KATCP command write('dram_memory', data).
We switc
Hi, Billy,
On Oct 13, 2010, at 6:23 PM, Barott, William Chauncey wrote:
> I'm running version 7 of the toolflow compiling for BEE2s.
In addition to the info others have provided about your subnet question, you
might want to seriously consider upgrading your toolflow to 10.1. The current
mlib_
6 matches
Mail list logo
