On 09/17/2010 11:45 PM, Cam Macdonell wrote:
> It seems most likely...< 2GB also means<= 1GB (which would fit in
> the hole). Although, I have to admit, I'm not sure how seabios handles
> the hole nowadays.
>
> What about 2GB with 32bit BAR?
The bios seems to ignore it and the guest can't
On Fri, Sep 17, 2010 at 3:15 PM, Chris Wright wrote:
> * Cam Macdonell (c...@cs.ualberta.ca) wrote:
>> On Fri, Sep 17, 2010 at 2:52 PM, Cam Macdonell wrote:
>> > On Fri, Sep 17, 2010 at 2:04 PM, Chris Wright wrote:
>> >> * Cam Macdonell (c...@cs.ualberta.ca) wrote:
>> >>> After fixing the resour
* Cam Macdonell (c...@cs.ualberta.ca) wrote:
> On Fri, Sep 17, 2010 at 2:52 PM, Cam Macdonell wrote:
> > On Fri, Sep 17, 2010 at 2:04 PM, Chris Wright wrote:
> >> * Cam Macdonell (c...@cs.ualberta.ca) wrote:
> >>> After fixing the resource_size_t return value with
> >>> pci_resource_alignment, I
On Fri, Sep 17, 2010 at 2:52 PM, Cam Macdonell wrote:
> On Fri, Sep 17, 2010 at 2:04 PM, Chris Wright wrote:
>> * Cam Macdonell (c...@cs.ualberta.ca) wrote:
>>> After fixing the resource_size_t return value with
>>> pci_resource_alignment, I see one other strange behaviour only when
>>> using 4GB
On Fri, Sep 17, 2010 at 2:04 PM, Chris Wright wrote:
> * Cam Macdonell (c...@cs.ualberta.ca) wrote:
>> After fixing the resource_size_t return value with
>> pci_resource_alignment, I see one other strange behaviour only when
>> using 4GB of RAM and a 2GB BAR. I haven't found any other combination
* Cam Macdonell (c...@cs.ualberta.ca) wrote:
> After fixing the resource_size_t return value with
> pci_resource_alignment, I see one other strange behaviour only when
> using 4GB of RAM and a 2GB BAR. I haven't found any other combination
> of RAM/BAR size that triggers this bug. I am using 2.6.
