Simon,
Just checked what u propsed, and it works.
So, i'm pretty sure, that the problem is with the ASL code. I thought
of an implementaion change of the ASL code, which will make it work:
we will change it from:
...
if ( slt == 0x1 )
else if (slt == 0x2)
...
else if (slt == 0x20)
.,..
to the following (just as an example):
if ( slt < 0x10 )
{
if (slt == 0x1)
...
} else {
if ( slt == 0x11)
...
}
What do u think about this?
On Fri, Oct 16, 2009 at 9:43 AM, Simon Horman <horms@xxxxxxxxxxxx> wrote:
> On Thu, Oct 15, 2009 at 04:02:59PM +0200, Tom Rotenberg wrote:
>> Well, i don't have a patch for it, as i'm not that skilled with
>> writing ASL code for the DSDT.
>> When i tried to change the levle interrupt to edge, it didn't work,
>> although i though it should work, so it might be a bug i wrote.
>>
>> Bottom line, if you are skilled enough to write a "smarter" device
>> search code for the DSDT - you should try it. I think that will solve
>> it. If you don't think you'll be able to pull it off, i can try to
>> prepare a patch, but it's not my sepciality... :)
>>
>> What do u think we should do to solve it?
>
> I did think of a check that might help.
>
> It is to simply move slot 8 (which is the lowest numbered slot
> that fails for me) up to be the first if clause. That should
> exercise your timing theory without having to get too involved
> in how to write better ASL (which frankly seems a bit painful to me).
>
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|