Am Samstag 09 Februar 2008 schrieben Sie:nd Too bad that you cannot make them publish their infos. Interesting, this was where I posted, as well... And I won't, as I reverted to my stable kernel again and thus patching it=20 again (yes it was 2.6.24 with early-quirks.c from git and your patch on top= )=20 doesn't give more info then I already provided. Furthermore I also told you= =20 that because of missing nforce2 ID the practical test wasn't really=20 necessary. Just add this line to your patch: + QBRIDGE(PCI_VENDOR_ID_NVIDIA, PCI_DEVICE_ID_NVIDIA_NFORCE2,=20 nvidia_timer), So that the quirk gets applied for nForce2, then your patch is - while stil= l=20 wrong in my eyes - not a regression anymore (for me) and thus I would take= =20 back my NAK(, but still not ACK it). bye, =2D-=20 (=B0=3D =3D=B0) //\ Prakash Punnoor /\\ V_/ \_V
| Parag Warudkar | BUG: soft lockup - CPU#1 stuck for 15s! [swapper:0] |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Bart Van Assche | Integration of SCST in the mainstream Linux kernel |
| Greg Kroah-Hartman | [PATCH 001/196] Chinese: Add the known_regression URI to the HOWTO |
git: | |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Arjan van de Ven | Re: [GIT]: Networking |
| David Miller | Re: [BUG] New Kernel Bugs |
