On 26 March 2013 11:08, Arnd Bergmann wrote:
> On Tuesday 26 March 2013, Peter Maydell wrote:
>>
>> On 26 March 2013 10:54, Arnd Bergmann wrote:
>> > Yes, very good. We will probably introduce sparse irq support on
>> > versatile in the near future, and then the value we write into the
>> > PCI_
On 4 April 2013 11:58, Michael S. Tsirkin wrote:
> On Thu, Apr 04, 2013 at 12:05:51PM +0100, Peter Maydell wrote:
>> On 28 March 2013 10:28, Peter Maydell wrote:
>> > On 26 March 2013 21:12, Michael S. Tsirkin wrote:
>> >> On Tue, Mar 26, 2013 at 11:17:55AM +, Peter Maydell wrote:
>> >>> I'm
On Thu, Apr 04, 2013 at 12:05:51PM +0100, Peter Maydell wrote:
> On 28 March 2013 10:28, Peter Maydell wrote:
> > On 26 March 2013 21:12, Michael S. Tsirkin wrote:
> >> On Tue, Mar 26, 2013 at 11:17:55AM +, Peter Maydell wrote:
> >>> I'm happy to provide some other way for QEMU to detect a
>
On 28 March 2013 10:28, Peter Maydell wrote:
> On 26 March 2013 21:12, Michael S. Tsirkin wrote:
>> On Tue, Mar 26, 2013 at 11:17:55AM +, Peter Maydell wrote:
>>> I'm happy to provide some other way for QEMU to detect a
>>> new working kernel if you want to implement one in the
>>> kernel, if
On 26 March 2013 21:12, Michael S. Tsirkin wrote:
> On Tue, Mar 26, 2013 at 11:17:55AM +, Peter Maydell wrote:
>> On 26 March 2013 11:08, Arnd Bergmann wrote:
>> > On Tuesday 26 March 2013, Peter Maydell wrote:
>> >> On 26 March 2013 10:54, Arnd Bergmann wrote:
>> >> > Yes, very good. We wi
On Tue, Mar 26, 2013 at 11:17:55AM +, Peter Maydell wrote:
> On 26 March 2013 11:08, Arnd Bergmann wrote:
> > On Tuesday 26 March 2013, Peter Maydell wrote:
> >> On 26 March 2013 10:54, Arnd Bergmann wrote:
> >> > Yes, very good. We will probably introduce sparse irq support on
> >> > versat
On 26 March 2013 11:08, Arnd Bergmann wrote:
> On Tuesday 26 March 2013, Peter Maydell wrote:
>> On 26 March 2013 10:54, Arnd Bergmann wrote:
>> > Yes, very good. We will probably introduce sparse irq support on
>> > versatile in the near future, and then the value we write into the
>> > PCI_INT
On Tuesday 26 March 2013, Peter Maydell wrote:
>
> On 26 March 2013 10:54, Arnd Bergmann wrote:
> > Yes, very good. We will probably introduce sparse irq support on
> > versatile in the near future, and then the value we write into the
> > PCI_INTERRUPT_LINE field will become arbitrary from qemu
On 26 March 2013 10:54, Arnd Bergmann wrote:
> Yes, very good. We will probably introduce sparse irq support on
> versatile in the near future, and then the value we write into the
> PCI_INTERRUPT_LINE field will become arbitrary from qemu's point
> of view, but I will make sure that we fix the i
On Tuesday 26 March 2013, Peter Maydell wrote:
>
> Implement the correct IRQ mapping for the Versatile PCI controller; it
> differs between realview and versatile boards, but the previous QEMU
> implementation was correct only for the first PCI card on a versatile
> board, since we weren't swizzli
Implement the correct IRQ mapping for the Versatile PCI controller; it
differs between realview and versatile boards, but the previous QEMU
implementation was correct only for the first PCI card on a versatile
board, since we weren't swizzling IRQs based on the slot number.
Since this change would
11 matches
Mail list logo
