Closed schelleg closed 8 years ago
My suggestion is to add that script back into the scripts
folder. We can mention this in the Q&A section of our documents, so that different groups of users can choose to use it or not.
I wondered about having the xilinx_proxy.sh script in there - but do we want the world to know Xilinx internal proxy IP addresses? ... not sure if that is a security risk.
Remember too that anyone plugging PYNQ into a corporate network will have to manually add their own http_proxy variables - this is known to RPi communities.
On Wed, May 18, 2016 at 5:19 PM, Yun Rock Qu notifications@github.com wrote:
My suggestion is to add that script back into the scripts folder. We can mention this in the Q&A section of our documents, so that different groups of users can choose to use it or not.
— You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub https://github.com/Xilinx/Pynq/issues/89#issuecomment-220186375
Graham
I thinking adding instructions to the FAQ or other docs would be better than adding a script. We can send separate instructions to Xilinx users or they can use at home.
Moving to PYNQ board and external Xilinx user focus. I'll close now and we'll help Xilinx employees on case by case basis
Some of you have run into this, but in the milan release, I removed the xilinx proxy environment variables. Implications of this:
Any discussion on this? We have several options to support both user groups, but the non-default user group will have to change settings.