On 24 March 2013 21:37, Michael S. Tsirkin wrote:
> On Sun, Mar 24, 2013 at 09:16:28PM +, Arnd Bergmann wrote:
>> I think it actually does on versatile and other platforms on which
>> the kernel probes the PCI bus itself, rather than relying on firmware
>> to have resources assigned in advance
On Sunday 24 March 2013, Michael S. Tsirkin wrote:
> For future kernels, let's build in some hook that let
> qemu detect a non broken guest. How about writing
> some magic value into revision ID or some other
> readonly field?
Yes, makes sense.
On Sunday 24 March 2013, Peter Maydell wrote:
> OK, I'll give that a go tomorrow.
>
> While you're here, do you know what the point of the PCI_SELFID
> register is? The h/w docs are clear that the OS has to write
> the slot number of the board itself in to this register, but
> again I don't see wh
On Sun, Mar 24, 2013 at 09:16:28PM +, Arnd Bergmann wrote:
> On Sunday 24 March 2013, Peter Maydell wrote:
> > Yeah, ideally being able to detect the buggy kernel would be good;
> > I can't see anything at the controller level that would do though,
> > and I don't really know enough about PCI t
On Sun, Mar 24, 2013 at 08:53:33PM +, Peter Maydell wrote:
> On 24 March 2013 19:17, Michael S. Tsirkin wrote:
> > On Sun, Mar 24, 2013 at 04:58:37PM +0100, Aurelien Jarno wrote:
> >> On Sun, Mar 24, 2013 at 11:32:30AM +, Peter Maydell wrote:
> >> > I've provided a property for enabling th
On 24 March 2013 21:16, Arnd Bergmann wrote:
> On Sunday 24 March 2013, Peter Maydell wrote:
>> Yeah, ideally being able to detect the buggy kernel would be good;
>> I can't see anything at the controller level that would do though,
>> and I don't really know enough about PCI to know about generic
On Sunday 24 March 2013, Peter Maydell wrote:
> Yeah, ideally being able to detect the buggy kernel would be good;
> I can't see anything at the controller level that would do though,
> and I don't really know enough about PCI to know about generic
> PCI stuff that would work. (Why would the OS nee
On 24 March 2013 19:17, Michael S. Tsirkin wrote:
> On Sun, Mar 24, 2013 at 04:58:37PM +0100, Aurelien Jarno wrote:
>> On Sun, Mar 24, 2013 at 11:32:30AM +, Peter Maydell wrote:
>> > I've provided a property for enabling the old broken IRQ mapping;
>> > this can be enabled with the command lin
On Sun, Mar 24, 2013 at 04:49:37PM +, Peter Maydell wrote:
> On 24 March 2013 15:58, Aurelien Jarno wrote:
> > On Sun, Mar 24, 2013 at 11:32:30AM +, Peter Maydell wrote:
> >> This patch series fixes a number of serious bugs in our emulation of
> >> the PCI controller found on VersatilePB a
On Sun, Mar 24, 2013 at 04:58:37PM +0100, Aurelien Jarno wrote:
> On Sun, Mar 24, 2013 at 11:32:30AM +, Peter Maydell wrote:
> > This patch series fixes a number of serious bugs in our emulation of
> > the PCI controller found on VersatilePB and the early Realview boards:
> > * our interrupt m
On 24 March 2013 15:58, Aurelien Jarno wrote:
> On Sun, Mar 24, 2013 at 11:32:30AM +, Peter Maydell wrote:
>> This patch series fixes a number of serious bugs in our emulation of
>> the PCI controller found on VersatilePB and the early Realview boards:
>> Patchset tested on both versatilepb a
On Sun, Mar 24, 2013 at 11:32:30AM +, Peter Maydell wrote:
> This patch series fixes a number of serious bugs in our emulation of
> the PCI controller found on VersatilePB and the early Realview boards:
> * our interrupt mapping was totally wrong
> * we weren't implementing the PCI memory win
This patch series fixes a number of serious bugs in our emulation of
the PCI controller found on VersatilePB and the early Realview boards:
* our interrupt mapping was totally wrong
* we weren't implementing the PCI memory windows
* the I/O window wasn't mapped on VersatilePB
* realview mapped
13 matches
Mail list logo
