On 04/03/19 11:19, Peter Maydell wrote:
> On Fri, 15 Feb 2019 at 09:38, Paolo Bonzini wrote:
>>
>> On 14/02/19 23:04, Sven Schnelle wrote:
>>> @@ -2202,6 +2224,7 @@ static const VMStateDescription vmstate_lsi_scsi = {
>>> VMSTATE_UINT8(stime0, LSIState),
>>> VMSTATE_UINT8(respid0
On Fri, 15 Feb 2019 at 09:38, Paolo Bonzini wrote:
>
> On 14/02/19 23:04, Sven Schnelle wrote:
> > @@ -2202,6 +2224,7 @@ static const VMStateDescription vmstate_lsi_scsi = {
> > VMSTATE_UINT8(stime0, LSIState),
> > VMSTATE_UINT8(respid0, LSIState),
> > VMSTATE_UINT8(resp
On Fri, Feb 15, 2019 at 10:36:53AM +0100, Paolo Bonzini wrote:
> > HP-UX checks this register after sending data to the target. If there's no
> > valid
> > information present, it assumes the client disconnected because the kernel
> > sent
> > to much data. Implement at least some of the SBCL fun
On 14/02/19 23:04, Sven Schnelle wrote:
> HP-UX checks this register after sending data to the target. If there's no
> valid
> information present, it assumes the client disconnected because the kernel
> sent
> to much data. Implement at least some of the SBCL functionality that is
> possible
>
HP-UX checks this register after sending data to the target. If there's no valid
information present, it assumes the client disconnected because the kernel sent
to much data. Implement at least some of the SBCL functionality that is possible
without having a real SCSI bus.
Signed-off-by: Sven Schn
