search for: 369009

Displaying 3 results from an estimated 3 matches for "369009".

Did you mean: 369001
2011 Apr 20
0
CESA-2011:0394 Important CentOS 5 x86_64 conga Update
CentOS Errata and Security Advisory 2011:0394 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2011-0394.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) x86_64: 6876b352f595b24bb20dfd4c86325dea luci-0.12.2-24.el5.centos.1.x86_64.rpm 9b1ff70b3cb5e14b92db6205e37ec95f ricci-0.12.2-24.el5.centos.1.x86_64.rpm
2014 Mar 23
0
[PATCH] drm/nouveau: allow nv04/nv50/nvc0+ parts of the driver to be separated
...of hardware. This could further be split off as necessary. Nothing: 416118 bytes text data bss dec hex filename 198669 9525 80 208274 32d92 drivers/gpu/drm/nouveau/nouveau.ko NV04: 710270 bytes text data bss dec hex filename 333755 35094 160 369009 5a171 drivers/gpu/drm/nouveau/nouveau.ko NV50: 722079 bytes text data bss dec hex filename 346476 34727 480 381683 5d2f3 drivers/gpu/drm/nouveau/nouveau.ko NVC0: 878726 bytes text data bss dec hex filename 360593 140327 80 501000 7a508 dri...
2014 Feb 15
3
[RFC PATCH] drm/nouveau: split off nvc0 compilation
So... I was wondering what the impact of splitting up the card compilation by e.g. generation would be. Depending on the split things would get fairly intertwined, so I thought I'd start small. This just splits NVC0 from everything else. I figure that for the people this matters the most to, NVC0 is the least relevant card -- people with sub-1GB of RAM, older hardware. With my config options