On 13 May 2015 at 10:29, Leon Alrae wrote:
> On 13/05/2015 06:48, Liviu Ionescu wrote:
>> are these patches finally in? if so, what repo/branch should I use to get
>> them?
>
> Note that v3 was sent quite recently and there should be some time to
> give everyone a chance to comment.
It's still o
On 13/05/2015 06:48, Liviu Ionescu wrote:
> are these patches finally in? if so, what repo/branch should I use to get
> them?
Note that v3 was sent quite recently and there should be some time to
give everyone a chance to comment. I was planning to send it out later,
together with UHI via target-
> On 06 May 2015, at 19:12, Leon Alrae wrote:
>
> ... I'm going to follow up with UHI
> patch series only. I don't have anything set up to test other
> semihosting interfaces, thus I don't plan to do any changes in these
> areas in near future. Therefore feel free to send your ARM semihosting
>
On 06/05/2015 16:22, Liviu Ionescu wrote:
>
> apparently your patch does not fix the arm semihosting problems. do you plan
> a separate patch for this?
This patchset doesn't contain any target semihosting specific changes
(just a clean up and new arg option). I'm going to follow up with UHI
patc
apparently your patch does not fix the arm semihosting problems. do you plan a
separate patch for this?
> bool semihosting_enabled(void)
> {
> return semihosting.allowed;
> }
any particular reason for naming the structure member ".allowed" and the getter
function "_enabled()"?
regards,
Hi,
This patch series adds "arg=" sub-option to --semihosting-config group. It
allows building up a list of input arguments as it can appear multiple
times in the command line. This is a flexible solution for creating
argc/argv for the guest program (needed by UHI semihosting for example).
RFC pat