On Mon, 2007-12-10 at 15:47 +0000, Ralf Baechle wrote:No, native mode is 5 not A in the low 4 bits of progif. You need to be a bit careful about those VIA, I remember having issues on Pegasos where we left it in legacy mode. It think the problem is that even when switched, the IRQ routing might be done based on some other setting in the chipset, possibly a strap. But that's nothing you can't deal with an appropriate quirk in the arch code. Also, double check the level/edge setting of the interrupts as it can be different between legacy and native (native is level low, legacy is rising edge). I'm surprised however that one would use such a legacy southbridge on a platform that can't issue low IO ports, that doesn't seem to make sense to me ... there's a whole lot of things on this such as the 8259 PIC etc.. that can only be addressed via low IOs, unless the ISA space can be somewhat remapped ? Ben. --
| Jeff Garzik | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Christoph Hellwig | Re: [malware-list] [RFC 0/5] [TALPA] Intro to a linux interface for on access scan... |
| Heiko Carstens | Re: -mm merge plans for 2.6.23 -- sys_fallocate |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
git: | |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Arjan van de Ven | Re: [GIT]: Networking |
| Jens Axboe | Re: [BUG] New Kernel Bugs |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Emmanuel Dreyfus | fixing send(2) semantics (kern/29750) |
| Christos Zoulas | Re: Melting down your network [Subject changed] |
| Juan RP | Changing the I/O scheduler on-the-fly |
| Emmanuel Dreyfus | Re: fixing send(2) semantics (kern/29750) |
