On 01/09/2016 15:17, Denis Dmitriev wrote:
>
> I think that I am missing some initialization or something like that.
> To work with the registers I create a memory region, and associate it
> with the read and write handlers (as an example I used lsi53c895a.c).
> Maybe work with memory in which m
2016-09-01 14:11 GMT+03:00 Paolo Bonzini :
>
>
>
> On 31/08/2016 15:48, Денис Дмитриев wrote:
> > uint64_t buslogicReadOutgoingMailbox(BuslogicState *s, BUSLOGICTASKSTATE
> > *TaskState)
> > {
> > uint64_tGCMailbox;
> > Mailbox24 Mbx24;
> > Mbx24.uCmdState = 0;
> > PCIDevice *
On 1 September 2016 at 13:59, Paolo Bonzini wrote:
> On 01/09/2016 13:19, Peter Maydell wrote:
>> On 1 September 2016 at 12:11, Paolo Bonzini wrote:
>>> That said, this looks very much like VirtualBox code. Do not use it if
>>> you want to contribute code to QEMU, because QEMU does not accept
>>
On 01/09/2016 13:19, Peter Maydell wrote:
> On 1 September 2016 at 12:11, Paolo Bonzini wrote:
>> That said, this looks very much like VirtualBox code. Do not use it if
>> you want to contribute code to QEMU, because QEMU does not accept
>> GPLv2-only code.
>
> I don't think this is the consen
On 1 September 2016 at 12:11, Paolo Bonzini wrote:
> That said, this looks very much like VirtualBox code. Do not use it if
> you want to contribute code to QEMU, because QEMU does not accept
> GPLv2-only code.
I don't think this is the consensus view. We'd prefer v2-or-later,
sure, but we haven
On 31/08/2016 15:48, Денис Дмитриев wrote:
> uint64_t buslogicReadOutgoingMailbox(BuslogicState *s, BUSLOGICTASKSTATE
> *TaskState)
> {
> uint64_tGCMailbox;
> Mailbox24 Mbx24;
> Mbx24.uCmdState = 0;
> PCIDevice *pci_dev = PCI_DEVICE(s);
> if (s->fMbxIs24Bit)
> {
>
Hi,
I'm trying to implement a buslogic scsi adapter(BT-958) for qemu. I
realized the driver interaction with the ports through which the driver can
write / read commands and parameters for the adapter. The driver was able
to make an adapter sample procedure. The problem is that I do not
understand
