Hi all, We've got a board with the Intel 3100 chipset. It shows a PCI id of 2670, which matches PCI_DEVICE_ID_INTEL_ESB2_0 and so the iTCO_wdt.c driver happily initializes. However, the documentation for the TCO wdt for this chipset doesn't match the implementation in the driver, so things get messed up. I'm not sure why the PCI IDs match, but maybe there is something else that the iTCO_wdt driver should key off of to make sure it doesn't try to run invalid code? On another note, it appears that Intel has driver code (written for 2.6.18, under dual BSD/GPLv2) for the wdt for this chipset available at: http://downloadcenter.intel.com/Detail_Desc.aspx?ProductID=2568&DwnldID=13653&lang=eng Are there any plans to incorporate this into mainline? Thanks, Chris --
| Heiko Carstens | Re: -mm merge plans for 2.6.23 -- sys_fallocate |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Vladislav Bolkhovitin | Re: Integration of SCST in the mainstream Linux kernel |
| Ingo Molnar | Re: suspend2 merge (was Re: [Suspend2-devel] Re: CFS and suspend2: hang in atomic ... |
git: | |
| Sander | 'struct task_struct' has no member named 'mems_allowed' (was: Re: 2.6.20-rc4-mm1) |
| David Miller | [GIT]: Networking |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Natalie Protasevich | [BUG] New Kernel Bugs |
| Gerrit Renker | [PATCH 15/37] dccp: Set per-connection CCIDs via socket options |
| Hans Reiser | Re: silent semantic changes with reiser4 |
| Nick Piggin | [ANNOUNCE] new new aops patchset |
| Christoph Hellwig | Re: [patch 01/15] security: pass path to inode_create |
| johnrobertbanks | Re: Reiser4. BEST FILESYSTEM EVER. |
