I already fixed that in my current version of virtualpok, but Janek's
patches were created against his version from April.
He already has the new version.
I maintain an own linkcmds in virtualpok, as I added a 0x1000 offset to
the start of the binary. It confused me to see some strange code in GD
>>> * Is the linkcmds change required for running pok-rtems?
>> For me, it was required. The old linkcmd script was causing undefined
>> TLS errors while building RTEMS.
> Please report this. This sounds like an independent issue which needs to
> be run down.
I believe this is a known issue. I thin
On 8/19/2014 4:34 PM, Janek van Oirschot wrote:
> On Mon, Aug 18, 2014 at 3:13 PM, Gedare Bloom wrote:
>> If you're using git for your development, you can use 'git
>> format-patch' to convert a set of commits into a set of patches. Some
>> properly formatted git patches can make it easier to rev
On Mon, Aug 18, 2014 at 3:13 PM, Gedare Bloom wrote:
> If you're using git for your development, you can use 'git
> format-patch' to convert a set of commits into a set of patches. Some
> properly formatted git patches can make it easier to review and merge
> your code. Some other notes follow.
Y
If you're using git for your development, you can use 'git
format-patch' to convert a set of commits into a set of patches. Some
properly formatted git patches can make it easier to review and merge
your code. Some other notes follow.
virtualpok_arinc653.patch:
* it seems the only part of this pat
A bit unconventional for a new patch but since my patches also include POK
changes this seemed like the best way to upload it. Patches and readme with
explanation on how to duplicate my environment and work are in the tarball.
I do assume that the virtualpok BSP and paravirt_cpu patches are already
