lkml.org 
[lkml]   [2003]   [Jul]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: 2.5.75-mm1 yenta-socket lsPCI IRQ reads incorrect
Date
On Tuesday 15 July 2003 17:34, Michael Frank wrote:
> I believe it is not here now, we need to look elsewhere, as interrupts
> stay dead also after reloading modules (see logs).
>
> Jul 15 17:06:43 mhfl2 kernel: Socket status: ffffffff

FFFFFFFF!!!!

This returns ffffffff too:
cb_writel(socket, CB_SOCKET_MASK, 0x0);
if ((temp = cb_readl(socket, CB_SOCKET_MASK)) != 0)
printk("Yenta: probe can't write socket mask %x\n",temp);

because the device is somewhat "passive" after a suspend....

Should we save all registers? - it has 128

It sits on the same bus with ide, e100 which work, so it won't
be pci related - OK?.

Another thing, even lspci returns crap after suspend because
data come from RAM rather than device(s).

I would like to do generic pci_save_state/pci_restore_state
centraly in the pci driver. It would reduce other driver side
work too.

What is the possible downside of this approach and your
opinion in general?


Regards
Michael


--
Powered by linux-2.5.75-mm1. Compiled with gcc-2.95-3 - mature and rock solid

My current linux related activities:
- 2.5 yenta_socket testing
- Test development and testing of swsusp for 2.4/2.5 and ACPI S3 of 2.5 kernel
- Everyday usage of 2.5 kernel

More info on 2.5 kernel: http://www.codemonkey.org.uk/post-halloween-2.5.txt
More info on swsusp: http://sourceforge.net/projects/swsusp/


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:46    [W:0.057 / U:0.024 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site