Aurelien Jarno wrote:
I am not fully comfortable introducing a binary firmware based on a
patch posted on a website. I see two options:
- Get your patch merged into ZIPL, so that we can build the firmware
directly from the ZIPL sources
- Add the patch to the pc-bios/ directory
Looks like we'll
On Sat, Apr 10, 2010 at 11:22:37AM +0200, Alexander Graf wrote:
>
> On 10.04.2010, at 02:00, Aurelien Jarno wrote:
>
> > On Sat, Apr 10, 2010 at 01:29:55AM +0200, Alexander Graf wrote:
> >>
> >> On 09.04.2010, at 22:17, Aurelien Jarno wrote:
> >>
> >>> On Thu, Apr 01, 2010 at 06:42:41PM +0200,
On 10.04.2010, at 02:00, Aurelien Jarno wrote:
> On Sat, Apr 10, 2010 at 01:29:55AM +0200, Alexander Graf wrote:
>>
>> On 09.04.2010, at 22:17, Aurelien Jarno wrote:
>>
>>> On Thu, Apr 01, 2010 at 06:42:41PM +0200, Alexander Graf wrote:
This patch adds a firmware blob to the S390 target. T
On Sat, Apr 10, 2010 at 01:29:55AM +0200, Alexander Graf wrote:
>
> On 09.04.2010, at 22:17, Aurelien Jarno wrote:
>
> > On Thu, Apr 01, 2010 at 06:42:41PM +0200, Alexander Graf wrote:
> >> This patch adds a firmware blob to the S390 target. The blob is a simple
> >> implementation of a virtio cl
On 09.04.2010, at 22:17, Aurelien Jarno wrote:
> On Thu, Apr 01, 2010 at 06:42:41PM +0200, Alexander Graf wrote:
>> This patch adds a firmware blob to the S390 target. The blob is a simple
>> implementation of a virtio client that tries to read the second stage
>> bootloader from sectors describe
On Thu, Apr 01, 2010 at 06:42:41PM +0200, Alexander Graf wrote:
> This patch adds a firmware blob to the S390 target. The blob is a simple
> implementation of a virtio client that tries to read the second stage
> bootloader from sectors described as of offset 0x20 in the MBR.
>
> In combination wi
