On Wed, Feb 14, 2007 at 03:05:24PM +, Jan Beulich wrote:
> The change to force legacy mode IDE channels' resources to fixed
> non-zero values confuses (at least some versions of) X, because the
> values reported by the kernel and those readable from PCI config space
> aren't consistent anymore.
> The masking is done primarily to (a) calculate the correct length (from a
> BAR's
> perspective), as I don't want to write the BAR if its length doesn't match the
> expectation, and (b) to properly report the new value in the printk.
Ok I guess you have to do something like that since you can't
>>> Alan <[EMAIL PROTECTED]> 14.02.07 16:40 >>>
>On Wed, 14 Feb 2007 15:05:24 +
>"Jan Beulich" <[EMAIL PROTECTED]> wrote:
>
>> The change to force legacy mode IDE channels' resources to fixed
>> non-zero values confuses (at least some versions of) X, because the
>> values reported by the kernel
On Wed, 14 Feb 2007 15:05:24 +
"Jan Beulich" <[EMAIL PROTECTED]> wrote:
> The change to force legacy mode IDE channels' resources to fixed
> non-zero values confuses (at least some versions of) X, because the
> values reported by the kernel and those readable from PCI config space
> aren't con
The change to force legacy mode IDE channels' resources to fixed
non-zero values confuses (at least some versions of) X, because the
values reported by the kernel and those readable from PCI config space
aren't consistent anymore. Therefore, this patch arranges for the
respective BARs to also get u
5 matches
Mail list logo