On Fri, Aug 7, 2015 at 11:22 PM, Joel Sherrill
wrote:
>
>
> On 8/7/2015 6:20 AM, Hesham ALMatary wrote:
>>
>> On Fri, Aug 7, 2015 at 12:07 PM, wrote:
>>>
>>> Zitat von Hesham ALMatary :
>>>
Hi,
>>>
>>>
>>>
FYI, there's some initial port that runs hello world here [1]. I'll
most li
On 7/08/2015 9:00 pm, e...@e-bbes.com wrote:
> Zitat von Hesham ALMatary :
>
> Yes, I run an update of Cygwin (but wasn't really old), and I started it
> again
> with --jobs=none.
>
> So far, the log file is twice the size of yesterdays, so it seems that it
> was a problem with the tools.
>
The
On 8/7/2015 6:20 AM, Hesham ALMatary wrote:
On Fri, Aug 7, 2015 at 12:07 PM, wrote:
Zitat von Hesham ALMatary :
Hi,
FYI, there's some initial port that runs hello world here [1]. I'll
most likely work on rebasing and improving it soon, and perhaps revive
the discussion of the upstreami
On Fri, Aug 7, 2015 at 12:07 PM, wrote:
> Zitat von Hesham ALMatary :
>
>> Hi,
>
>
>> FYI, there's some initial port that runs hello world here [1]. I'll
>> most likely work on rebasing and improving it soon, and perhaps revive
>> the discussion of the upstreaming process, if it's of interest.
>
Zitat von Hesham ALMatary :
Hi,
FYI, there's some initial port that runs hello world here [1]. I'll
most likely work on rebasing and improving it soon, and perhaps revive
the discussion of the upstreaming process, if it's of interest.
Any chance, you could check it in?
Zitat von Hesham ALMatary :
Hi,
I've built it early this morning, and it went smoothly, no errors. So,
I suspect it's something with your tools, and perhaps it's better to
update it and try again as Chris suggested.
Yes, I run an update of Cygwin (but wasn't really old), and I started it agai
Hi,
I've built it early this morning, and it went smoothly, no errors. So,
I suspect it's something with your tools, and perhaps it's better to
update it and try again as Chris suggested.
FYI, there's some initial port that runs hello world here [1]. I'll
most likely work on rebasing and improvin
On 7/08/2015 3:01 pm, emanuel stiebler wrote:
> should it still work, didn't see anything about it for a while on this
> list, tried yesterday, and the source-builder failed in newlib:
Can you please try '--jobs=none' on the RSB command line ?
I wonder if this is a GNU make and cgywin dll issue.
On Mon, Feb 2, 2015 at 9:18 PM, Chris Johns wrote:
> On 3/02/2015 1:36 am, Joel Sherrill wrote:
>>>
>>> Should I (or anyone of you) create a thread on Xilinx
>>> forums to discuss about that issue?
>>
>> Chris should answer this since he is leading the discussions with Xilinx
>> we have been havin
On 3/02/2015 1:36 am, Joel Sherrill wrote:
Should I (or anyone of you) create a thread on Xilinx
forums to discuss about that issue?
Chris should answer this since he is leading the discussions with Xilinx
we have been having.
Hesham, feel free to start a discussion.
Chris
___
On Mon, Feb 2, 2015 at 2:36 PM, Joel Sherrill wrote:
>
> On 2/2/2015 7:57 AM, Hesham Moustafa wrote:
>> OK for now I have a Hello World port working, using a very little code
>> for UART_RS232 IP (two functions send/receive and UART register
>> definitions) which I believe there is a similar code
On 2/2/2015 7:57 AM, Hesham Moustafa wrote:
> OK for now I have a Hello World port working, using a very little code
> for UART_RS232 IP (two functions send/receive and UART register
> definitions) which I believe there is a similar code for it on RTEMS
> somewhere.
If it is really an NS16550, t
OK for now I have a Hello World port working, using a very little code
for UART_RS232 IP (two functions send/receive and UART register
definitions) which I believe there is a similar code for it on RTEMS
somewhere. Should I (or anyone of you) create a thread on Xilinx
forums to discuss about that i
On 31/01/2015 8:32 am, Peter Dufault wrote:
The wording is very bizarre:
"Except as otherwise provided in a valid license issued to you by Xilinx, and to the maximum
extent permitted by applicable law: (1) THESE MATERIALS ARE MADE AVAILABLE "AS IS" AND
WITH ALL FAULTS, AND XILINX HEREBY DISCLA
The wording is very bizarre:
"Except as otherwise provided in a valid license issued to you by Xilinx, and
to the maximum extent permitted by applicable law: (1) THESE MATERIALS ARE MADE
AVAILABLE "AS IS" AND WITH ALL FAULTS, AND XILINX HEREBY DISCLAIMS ALL
WARRANTIES AND CONDITIONS, EXPRESS, I
On 29/01/2015 8:43 pm, Hesham Moustafa wrote:
I didn't find a separate license file but I found this license
paragraph on one of the header files:
The following license is not suitable for RTEMS and I question any
Xilinx code that may have been added to RTEMS as being suitable.
Specifically,
I didn't find a separate license file but I found this license
paragraph on one of the header files:
/**
*
* (c) Copyright 2002-2013 Xilinx, Inc. All rights reserved.
*
* This file contains confidential and proprietary inf
These may already be in the tree as part of the Zynq port if the serial port(s)
are the same.
Please post the full copyright text but check if the same code is already in
the tree in support of another of their ports.
And congratulations on getting it working this much quickly. :)
On January
See if there is a license in the distribution that contained the Xilinx files.
-Gedare
On Wed, Jan 28, 2015 at 1:05 PM, Hesham Moustafa
wrote:
> Hi,
>
> I am currently porting RTEMS to Microblaze based on Joel's work. Hello
> world hits Init and printf successfully, so I have to write a console
19 matches
Mail list logo
